What is an action in automation?
An action is a task an automated workflow carries out after it starts, such as sending an email, creating a record, or updating a row in a spreadsheet.
If a trigger decides when an automation runs, actions decide what it does. An action is a single step in which the automation does something in an app: sends a message, creates a calendar event, adds a contact, uploads a file, or updates a record. A workflow can have one action or a long chain of them, each running in order.
For example, when a customer books a demo through a scheduling page, the actions might be to create a contact in the CRM, add the meeting to the salesperson's calendar, send the customer a confirmation email with a short preparation checklist, and post a note in the sales channel. Each action can reuse details from the trigger or from earlier steps, such as the customer's name and email address.
Actions can also change information rather than send it anywhere, for example by reformatting a date, splitting a full name into first and last names, or asking an AI model to summarize a block of text. Conditions and filters can decide whether an action runs at all, so different cases take different paths through the same workflow.
An action can only do what the connected app allows through its integration. If an app does not offer a particular action, it may still be possible through its API, the channel programs use to talk to each other, but that usually takes more technical setup. Actions that change or delete data are worth testing carefully, because a mistake repeats every time the workflow runs.
An example
After a form is submitted, the workflow's actions add the person to a mailing list and send the team a chat message.