📘 TL;DR
A trigger is the event that starts your workflow.
It might be someone viewing a room, submitting a form, or a CRM deal moving to a new stage. You can also define scopes so a trigger only runs under specific conditions, like “only when a deal moves to Contract Sent.”
Once a trigger happens, Flowla runs the workflow you’ve defined.
What Is a Trigger?
Think of a trigger as your workflow's starting signal.
It tells Flowla: “Something important just happened. Now do what we planned.”
That could be:
A room is viewed for the first time
A prospect fills out a form
A deal in your CRM moves from Proposal to Closed Won
A contact hasn’t opened their room in 3 days
You decide what counts as meaningful activity. Flowla listens and reacts.
Types of Triggers You Can Use
Inside the Workflow Builder, you’ll see triggers grouped by source. Here are the main categories and how they’re typically used:
🟦 Room Activity
Trigger | Use Case |
Room viewed | Notify the rep or trigger a follow-up |
Room not viewed (after X days) | Send a reminder or nudge the buyer |
Room viewed for the first time | Great for a personalized first-touch |
Room status changed | Useful for updating CRM or notifying CS |
Section completed | Unlock the next step or send confirmation |
Action marked complete | Trigger a handoff or internal alert |
Action not completed (after X days) | Send a reminder or escalate internally |
📄 Forms
Trigger | Use Case |
Form submitted | Push data to your CRM, trigger onboarding steps, or notify CS |
📊 CRM (HubSpot & Salesforce)
Trigger | Use Case |
Deal/Opportunity stage changes | Create a room, send proposal, unlock onboarding |
Property updated | Use field changes to trigger personalized next steps |
New object created | Automatically spin up a room for new deals or contacts |
🌐 Webhooks & External Apps
Trigger | Use Case |
Webhook received | Use events from tools like notetakers or custom apps to kick off workflows (e.g. “Call ended” → summarize & send recap) |
What are scopes?
Sometimes you don’t want your workflow to trigger every time something changes, just when something specific happens.
That’s where scopes come in.
A scope helps you define exactly when a trigger should fire. Think of it like a filter, but smarter.
For example:
🔸 Trigger: Deal status changed
🔹 Scope: Only if the new stage is Contract Sent
So instead of running every time the deal stage changes, it only runs at the right moment.