Skip to main content
Actions are what your workflow actually does — the steps Flowla takes once a trigger fires.

​
Room actions

​
Communication actions

​
Contact & company actions

​
Task actions

​
CRM actions — HubSpot

​
CRM actions — Salesforce

​
CRM actions — Attio

​
AI actions

​
Advanced actions

​
Configuring actions

Using dynamic values You can pull in real data from earlier in the workflow — like the contact’s name, the room link, or the deal name — so each action is personalized automatically. Examples:
  • {{trigger.deal_name}} — the name of the deal that triggered the workflow
  • {{contact.email}} — the contact’s email address
  • {{room.link}} — the shareable link to the room
Use dynamic values wherever possible — hardcoding a contact name or email address makes the workflow brittle and less useful across your team.
Sending to the Smart Queue for review Toggle on “Add to queue for review” on any action to hold it for your approval before it runs. This is especially useful for AI-generated emails or updates you want to check before they go out.

​
Best practices

  1. Order actions logically — Run them in the sequence they should happen
  2. Use dynamic values — Personalise each action with real data from the trigger
  3. Plan for errors — Think about what should happen if an action doesn’t work
  4. Test one step at a time — Add actions gradually and verify each one before adding the next