Workflow node reference
App Action
Perform action in a connected app. Exact configuration, outputs, execution behavior, errors, limits, and examples for the App Action workflow node.
What this guide covers
- Category: Integrations.
- Use it to run one supported action from an active connected Stripe, Notion, Slack, Google Sheets, Google Calendar, Gmail, or Google Drive account.
- 3 configuration fields and 3 documented outputs.
- Only cataloged actions are supported.
What this node does
Perform action in a connected app
Use it to run one supported action from an active connected Stripe, Notion, Slack, Google Sheets, Google Calendar, Gmail, or Google Drive account.
When not to use it
Do not use it for an unsupported provider or action; use HTTP Request or a reviewed Function.
Prerequisites
- Supported app
- Active connected account
- Provider permission to the selected resource
- Required action inputs
Supported app. Active connected account. Provider permission to the selected resource. Required action inputs
Inputs and configuration fields
| Field | Key | Control / type | Requirement | Default | Accepted values and behavior |
|---|---|---|---|---|---|
App | app | select | Required when shown | No default | Select from your connected apps. Value accepted by the displayed control |
Action | action | select | Required when shown | No default | What to do in this app. Value accepted by the displayed control |
Action Configuration | action_config | json | Optional | No default | Configure the action parameters. Value accepted by the displayed control |
Configure the node
- Drag App Action from Integrations in the node palette.
- Select the node to open its configuration drawer.
- Complete every required field and any conditional field revealed by your choices.
- Insert variables only from the current trigger or an earlier node on the same path.
- Connect every required output handle to the intended next step.
- Save and run Workflow Test with representative data before activation.
Outputs
Later nodes can use these values only after this node has run successfully on the same execution path.
| Variable | Type | Meaning |
|---|---|---|
{{nodes.app_action.success}} | boolean | Whether action succeeded |
{{nodes.app_action.result}} | object | Action result data |
{{nodes.app_action.error}} | string | Error message if failed |
Execution behavior
- Loads the canonical action schema for the selected app.
- Resolves mapped inputs and calls through the selected connection.
- Makes outputs available to later nodes; exact fields depend on the action.
Do not assume a failed node is automatically retried. Review the execution result and the relevant service documentation before repeating an operation that could create a duplicate side effect.
Example use case
Append qualified lead details to Google Sheets and notify a Slack channel.
New Conversation → Extract Info → App Action (Sheets) → App Action (Slack) → End FlowCommon errors
| Symptom | Resolution |
|---|---|
Connection is missing or expired | Open Integrations and connect/reconnect. |
Resource not found | Grant the connected account access and use the exact provider identifier. |
Action input is invalid | Match the fields shown after selecting the action. |
Limitations
Only cataloged actions are supported.
Provider permissions and rate limits still apply.
Only cataloged actions are supported. Provider permissions and rate limits still apply.