📘 TL;DR
An action is the task Flowla performs when a workflow is triggered.
It could be creating a room, sending an email, unlocking a section, notifying your team, updating your CRM, or even generating personalized content using AI. Actions can be combined, sequenced, and conditionally controlled.
What Is an Action?
If a trigger is when the workflow starts, an action is what it actually does.
Actions are the building blocks of automation. Each one performs a specific task:
For your buyers (e.g. send a room or follow-up email)
For your team (e.g. notify CS or post to Slack)
For your systems (e.g. update CRM, send data to an API)
You can use one action, or chain multiple actions together to handle complex workflows with ease.
Action Types in Flowla
Here are the most common actions, grouped by purpose:
Action | Use Case |
AI Agents | Generate a summary, proposal, business case |
Send email, batch-send follow-ups | |
CRM (Salesforce, HubSpot) | Change property, update stage, sync contacts |
Room Actions | Notify team when a room is viewed or form submitted |
Forms & Actions | Create action, change status, assign task |
Misc | Webhooks, conditional paths, API calls |
Why Actions Matter
Actions are the backbone of any scalable process. They:
Keep your CRM and room aligned
Ensure buyers get timely follow-ups
Alert your team to take the next step
Turn signals into movement
Instead of relying on memory or chasing tasks manually, your workflows act on your behalf.
What Makes Up an Action?
Every action in Flowla includes:
Element | What it Does |
Inputs | The information it uses to run (like email address, room ID, or message) |
Conditions | Optional filters that determine if this action should run |
Outputs (only some actions) | Data created by the action, like a room link or contact ID, which can be used in the next step |
Inputs: where actions get their data
Inputs: where actions get their data
Every action needs information to do its job. This is called an input.
Input fields define what the action will do and with which data. They are used to set up the action.
Type | What it means | Example |
Static | Use the same selected value every time the workflow runs | Send this email to [email protected] |
Dynamic | Flowla pulls the value from a previous step | Send this email to the contact who submitted the form |
If you’ve used a trigger like “Form submitted”, the form data becomes available to use in the next actions: like the name, email, or company field that was filled in.
Dynamic inputs help you build flexible workflows that adapt to each customer or deal, without having to hard-code anything.
Conditions: when to run (or skip) an action
Conditions: when to run (or skip) an action
You can add conditions to any action to control whether it runs.
Think of conditions like “only do this if...” logic.
For example:
✅ Only send the follow-up email if the Room was viewed
✅ Only update the CRM if the contact has a valid email
✅ Only notify Slack if the viewer is a decision-maker
Outputs: what you get for the next step
Outputs: what you get for the next step
Some actions also produce outputs. This is data you can reuse later.
For example:
Find Room by Deal ID → gets you the Room link
Send Email → uses that Room link in the message body
Flowla makes it easy to pass values between steps, so everything stays connected.