Skip to main content
A trigger is the starting signal for your workflow — the moment Flowla knows it’s time to act.

​
What is a trigger?

Think of a trigger as Flowla’s way of listening. You tell it what to watch for, and the moment it happens, your workflow kicks off automatically. That could be something like:
  • A prospect opens your room for the first time
  • A customer submits a form
  • A deal moves to a new stage in your CRM (your customer relationship tool, like HubSpot or Salesforce)
  • A contact hasn’t opened their room in 3 days
You decide what counts as the right moment. Flowla does the rest.

​
Types of triggers

​
Room activity

​
Forms

​
Actions (tasks inside rooms)

​
CRM — HubSpot

​
CRM — Salesforce

​
CRM — Attio

​
Call transcripts

​
Email

​
Webhooks & external apps

​
What are scopes?

Sometimes you don’t want a workflow to fire every time a trigger happens — only when something specific is true. That’s what scopes are for. A scope acts as a filter, so your workflow only runs at exactly the right moment.

​
Example

  • Trigger: Deal stage changed
  • Scope: Only when the new stage is Contract Sent
Without a scope, the workflow fires every time the deal stage changes. With a scope, it only fires when the deal reaches that one specific stage.
After setting up a new trigger, check your workflow logs to confirm it fires exactly when expected — it’s the quickest way to catch a misconfigured scope before it causes issues.

​
Best practices

  1. Start specific — Begin with narrow conditions and expand later if needed
  2. Check for duplicates — Make sure you don’t have two workflows with the same trigger
  3. Test before going live — Create a test record to confirm the trigger fires correctly
  4. Use scopes — Filter down to exactly the scenario you care about
  5. Review regularly — Check your workflow logs to make sure triggers are firing as expected