Add And Configure Actions
Add the work a workflow should perform after it starts.
Actions are the steps that run after a trigger or another node.
Actions do the real work in a workflow: create records, update fields, send messages, wait, branch, loop, or call an integration. A workflow can have one action or many, but each action should have a clear reason to exist.
Add An Action
- Select the place where the next step should be added.
- Open the node palette.
- Search for an action.
- Select the action.
- Open the configuration panel.
- Complete all required fields.
- Save the workflow.
The builder only shows actions that are compatible with the records available at that point in the workflow.
Name actions clearly when the builder supports labels. A workflow with several
similar steps is much easier to debug when each action explains its purpose,
such as Create onboarding task or Notify finance owner.
Choose The Right Action
Start with the business outcome, then choose the smallest action that achieves it. If a teammate still needs to make a decision, create a task or notification instead of automatically sending an email, invoice, document, or provider update.
Use create actions when the workflow should start new work. Use update actions when the workflow should keep an existing record current. Use notification actions when a human needs context before acting.
Configure Action Fields
Action fields can use fixed values or variables from earlier workflow records. Use variables when the action should copy data from the trigger or another step.
For each action, review:
- Required fields.
- Record or resource selected from earlier steps.
- Static values that should be the same every time.
- Variables that should change per run.
- Owner, assignee, status, priority, or due date behavior.
- Whether the action sends a customer-facing message.
For finance, HRM, and customer-facing actions, confirm the action should run automatically every time the trigger matches. If a human should approve the decision first, add a task or notification action instead of automating the final customer-facing step.
Order Actions Carefully
Put actions in the order the business process actually needs. For example, create the task before adding a task comment, create the invoice before sending an invoice email, and wait for a condition before sending a reminder.
If a later action depends on a field from an earlier action, test the workflow and confirm that value appears in the run detail.
Use delays and conditions to protect actions that should not run immediately. For example, send a reminder only after waiting and checking that the invoice is still unpaid.
Customer-Facing Actions
Before adding an action that sends something to a customer, test the exact message, recipient, link, and timing with an internal record. Customer-facing workflow actions should have clear ownership because they can send many messages without a teammate pressing send each time.
If the action depends on a payment, signature, booking, or approval status, add a condition immediately before the send step so the workflow checks the current state before contacting the customer.
Troubleshoot Action Warnings
Configuration warnings usually mean the action is missing a required field, a selected resource is no longer available, or a variable points to a step that no longer exists. Fix warnings before publishing, because a workflow with invalid actions may fail after the trigger fires.
If an action fails during a run, open the run detail before editing the workflow. The run detail shows which input value, record, provider, or configuration caused the failure.
Test New Actions
Before publishing, simulate the workflow with a safe record. Confirm the action creates, updates, sends, waits, or branches exactly as intended. Then review the first live run after publishing.