What Do Actions Do in a Workflow?
What Do Actions Do in a Workflow?
Triggers are always followed by Actions. Each action performs a task—like creating, updating, or finding data.
Actions do the real work (the follow-ups, the notifications, the updates, the content unlocks) that keep your processes moving without manual effort.
Actions are added one-by-one to your workflow
Actions are added one-by-one to your workflow
Each action performs a single task, and you can chain multiple actions together to create powerful, automated flows.
Examples:
Send Room → Share a personalized Room with a new lead
Send Email → Follow up with a summary and next steps
Post to Slack → Notify your team when a decision-maker engages
Update CRM property → Keep your pipeline up to date
Use AI Agent → Auto-generate a proposal, email, or summary
What makes up an action?
What makes up an action?
Every action has two parts:
Element | Description |
Inputs | The information it uses to run (like email address, Room ID, or message) |
Conditions | Optional filters that determine if this action should run |
Some actions also produce outputs, which can be passed into later steps, like extracting a Room ID and using it in the next action.
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
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.
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.