Automation actions
Actions define what an automation does after the trigger runs. Each action does one specific thing, and you can chain multiple actions together in sequence, so a single automation carries out several steps one after the other from a single event that started the automation.
Entity actions
Entity actions create, update, archive, duplicate, move, copy, or delete records across your workspace. A create action generates a new task, invoice, proposal, contract, form, contact, or recurring invoice with fields mapped from the trigger data. An update action changes a field value on an existing record, like setting a task status to "Complete" or assigning a project to a team member. An archive action moves a record to archived status. A duplicate action creates a copy of the triggering record. A move action relocates a task to a different board or group, and a copy action copies it to a new location. A delete action removes a record. Field mapping lets trigger data flow into action fields, so a form submission's name field populates the new contact's name automatically.
Communication actions
The "Email" action delivers an email using a customisable template where variables like client name, project title, and invoice amount pull from the trigger data, so each email is personalised to the event that started the automation. The "Notification" action pushes an in-app notification to specific team members or roles. The "Comment" action adds a comment to a task, which keeps a visible trail on the record itself.
Flow control and integration actions
A delay action pauses the chain for a set period (minutes, hours, or days) before the next action runs, or waits until a condition is met. An "API Call" action sends an HTTP request to an external URL, passing data from the trigger and previous actions, so automations can push updates to tools and services outside your workspace. The API call supports GET, POST, PUT, PATCH, and DELETE methods, with configurable headers, URL parameters, and body data. A "Zapier" action connects to a Zapier webhook URL, which opens up thousands of third-party integrations from within an automation chain.
Chaining actions together
Actions run in sequence from top to bottom. Because actions chain, a single automation can create a contact, send a welcome email, and assign a follow-up task, all from one trigger event, all in one connected flow.
