For the complete documentation index, see llms.txt. This page is also available as Markdown.

Add and configure actions

In this section you will learn about the steps

An action performs a task such as reading data, updating a record, or navigating to an app page. A workflow step contains an action or a rule.

Add an action

  1. Click + at the position where the step should run.

  2. Choose the action.

  3. For a data action, choose the resource, collection, and operation.

  4. Configure required fields, filters, and record identifiers.

  5. Bind dynamic fields to workflow inputs or earlier step outputs.

  6. Test the step and inspect the result before adding a dependent step.

Example: update a ticket

Choose the Tickets collection and its update operation. Bind the record ID to ticket_id and set status to an allowed value in that source.

Do not use a row's position as its record identifier. Confirm the operation targets the intended ID, particularly after sorting or filtering a list.

Choose the right action

See the action reference. In-app actions, such as page navigation, belong to an interactive app context; do not assume they are meaningful in a background automation.

If a step fails, inspect its input and error before running it again. A test of a write action can change data. See Test steps and complete workflows.

Last updated

Was this helpful?