Actions are what a workflow does once its trigger fired and its conditions passed. A workflow can have several actions. Add them with Add Action in the workflow form.
Available action types
| Action type | Label in UI | What it does |
|---|---|---|
send_email | Send Email | Sends an email using the organization's SMTP settings |
create_pdf | Create PDF | Generates a PDF from an HTML template (requires a filename) |
webhook | Call Webhook | Makes a signed HTTP request to an external service, with retries |
notify | Send In-App Notification | Shows a notification in the bell for one user or every member of the organization |
create_ticket | Create Ticket | Creates a support ticket, optionally linked to a customer and assigned to a user |
update_record | Update Triggering Record | Sets a field on the record that fired the trigger. Class triggers only |
Configuration fields
- Send Email: To Email (required), then either a template (Use Template) or Subject and Body; optional CC Email and BCC Email.
- Create PDF: a template and Output Filename (required).
- Call Webhook: Webhook URL, HTTP Method, JSON Body and Timeout (ms).
- Send In-App Notification: Send To (One User or Everyone In The Organization), a User when sending to one user, Notification Title, Notification Message, optional Link and Notification Type (Info, Warning, Success, Error).
- Create Ticket: Ticket Title (required), Ticket Description, Priority (Low, Medium, High, Critical), Customer ID, Assignee.
- Update Triggering Record: Field To Update and New Value (leave empty to clear the field).
Steps
- Select the trigger first.
- Click Add Action and choose the Action Type.
- Fill in the configuration; required fields are validated on save.
- Repeat for more actions and save.
Tips
- Text fields accept
{{...}}placeholders that are replaced with values from the triggering record. After you choose a trigger, the panel beside the form lists the available data fields and you can drag them into a field. - Use Send In-App Notification to test a workflow safely.
- If one action fails and others succeed, the run is logged as Partial Failure (see
automation/troubleshooting). - Update Triggering Record only works with class (custom entity) triggers.