Skip to main content
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.

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

Room Activity

TriggerDescription
Room viewedFires when any viewer opens the room
Room viewed first timeFires only on the first view of the viewer
Room not viewedFires when a room hasn’t been viewed within a time period
Room status changedFires when room status is updated
Room met criteriaFires when room matches specific conditions

Forms

TriggerDescription
Form submittedFires when a form is completed

Flowla actions

TriggerDescription
Action status changedFires when an action is marked done, in progress, or cancelled
Action not completedFires when an action remains incomplete past due date
Stage completedFires when all actions in a section are done

CRM - HubSpot

TriggerDescription
Deal stage changedFires when opportunity moves to a different stage
Contact lead status changedFires when lead status is updated
Object createdFires when a new deal, contact, or company is created
Property changedFires when any HubSpot property is updated
Ticket status changedFires when ticket status changes
Task completedFires when a HubSpot task is marked complete

CRM - Salesforce

TriggerDescription
Opportunity stage changedFires when opportunity moves to a different stage
Object createdFires when a new record is created
Property changedFires when any Salesforce field is updated

Call Transcripts

TriggerDescription
Fireflies transcription completedFires when Fireflies.ai processes a call
Gong transcription completedFires when Gong processes a call

Email

TriggerDescription
Gmail thread email receivedFires when a new email arrives in a tracked thread

Webhooks & External Apps

TriggerDescription
Custom webhookFires via API or webhook for custom integrations

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. 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.

Best practices

  1. Start specific - Begin with narrow conditions, expand later
  2. Avoid duplicates - Check for existing workflows with similar triggers
  3. Test thoroughly - Create test records to verify trigger behavior
  4. Use scopes - Filter to relevant scenarios
  5. Monitor performance - Review workflow logs to ensure triggers fire correctly