Skip to main content
Actions are the steps that do work after a workflow starts. They can transform values, call another service, make a decision, create a file, send a response, or control which path runs next. This reference documents every action currently available in the editor. Use the navigation to browse by package, or search for the action by the name shown in the node picker.

​
Read an action page

Every page starts with the action’s purpose, then documents the fields and behavior that exist in the current implementation:
  • Inputs are values the action reads. A field can be configured directly, connected from an earlier output, or both, depending on the node.
  • Outputs are values later actions can use. Some outputs appear only when a related option is enabled.
  • Third-party account identifies the connected service account used for an external request.
  • Examples show a representative configuration when the action benefits from one.
  • Troubleshooting calls out common failures and implementation-specific constraints.
Many nodes change their visible inputs or outputs when a configuration value changes. Review downstream connections after changing an option that controls the node’s shape.

​
Static and connected values

Configuration fields are normally fixed for the workflow, while connectable inputs can receive a different value on every run. Some fields support either mode. Use a fixed value for behavior that should remain constant, and connect an earlier output when the value belongs to the data being processed.

​
Accounts and external services

Integration actions require a matching third-party account. The page for each action describes the account type and the request it makes, but access still depends on the permissions, API limits, and data available to that account.
When a service action fails, first verify the selected account, then inspect required inputs and service-specific limits documented on that action’s page.

​
Actions and triggers

An action runs because the workflow reached it. A trigger starts a workflow in response to an event or schedule. See the Triggers reference for every available starting event.