Skip to main content

Build your first Workflow

Step-by-step guide to building your first Workflow in Flowla - from picking a trigger to adding actions and going live.

Delia Barbat avatar
Written by Delia Barbat
Updated this week

What you’ll do

In this guide, you’ll walk through how to build your very first Workflow in Flowla.

No coding, no guesswork.

You’ll define:

  • A trigger: when something happens (like a form is submitted or a Room is viewed)

  • One or more actions: what Flowla should do next (like send an email, notify your team, or create a Room)

This is the foundation of automation in Flowla, and it only takes a few minutes.


Step 1: Add a Trigger

In the Workflow Builder, click “Select a trigger.”

Pick the signal that should start this Workflow. That could be:

  • A Room being viewed

  • A form being submitted

  • A CRM stage changing

  • A webhook firing from another tool

You can narrow it down using scopes, so the Workflow only runs under specific conditions (like for a certain template or Room

Step 2: Add an Action

Once the trigger is set, click the plus icon to add an action.

Flowla can:

  • Send an email

  • Create a new Room from a template

  • Summarize text with AI

  • Push or pull data from your CRM

  • And more

Actions can include conditions (when to run) if you want to limit the workflow.

Bonus: Add AI Agent

Use Flowla’s AI Agents to personalize follow-ups, summarize form responses, or write content based on Room activity.

Just select an AI-powered action, like Email Composer or Summarizer, and add your instructions.

Step 3: Save, Test, and Activate

Give your Workflow a name, save it, and test it in one of your Rooms.

You’ll see the automation kick in the moment the trigger condition is met.

💡 Important: Integrate First

If your Workflow uses:

  • CRM-based triggers or actions (HubSpot or Salesforce)

  • Email-based actions (like sending a Room via Gmail or Outlook)

Make sure those integrations are connected first.
Go to Settings → Integrations to set them up.

Did this answer your question?