Action

Perform actions in connected applications like creating tasks, sending messages, or updating records.

Overview

The Action node executes operations in your connected integrations - send Slack messages, create CRM records, add rows to spreadsheets, update project tasks, and more.

Best for: Creating/updating records, sending messages, triggering actions in connected apps, and integrating with external services.

Configuration

1. Select Integration: Choose from connected apps (Slack, Google Sheets, Notion, etc.)
2. Choose Action: Select a specific action (Send message, Create record, etc.). The available fields depend on your selection.
3. Select Connection: If you have multiple connections, choose which one to use
4. Map Fields: Provide data from previous nodes using variables. Hover a field label to view its description when guidance is available.
5. Configure Settings: Action-specific options

Field Configuration Modes

Each field in an action can be configured independently with one of these modes:

Mode	Description	When to Use
Manual	Enter a static value or use variables from previous nodes	When you know exactly what value to use
Auto	AI automatically determines the best value based on context	When the value depends on workflow context
Prompt AI	Provide instructions for AI to generate the value	When you need custom AI logic for this field
None	Skip an optional field entirely	When the action does not need that input

Recipient fields such as To, Cc, and Bcc are never filled by AI by default. If you switch them to Auto or Prompt AI, the editor shows a warning, because earlier steps can contain untrusted text from form submissions or meeting invites. At runtime, AI-generated addresses are validated against recipient data from previous nodes; if an address cannot be verified, the step fails instead of sending.

Manual Mode Example:

{{trigger.output.customer_email}}

Prompt AI Mode Example:

Based on the sentiment analysis result {{agent.output.structured.sentiment}},
write an appropriate subject line for the follow-up email.

Connection Selection

If you have multiple connections to the same integration (e.g., multiple Slack workspaces or Gmail accounts), select which connection this action should use. This is configured at the action level.

If the selected connection is expired or missing scopes required by this action, the connection selector shows a warning with a link to reauthorize.

Requires Confirmation

When enabled, the workflow will pause before executing this action and request user confirmation. This is useful for:

• Actions with significant external impact (sending emails, creating records)
• Review steps before data is pushed to external systems
• Compliance workflows requiring human approval

Default: Disabled (action executes automatically)

Error Handling

Configure how errors are handled:

Strategy	Behavior
Stop (default)	Workflow stops immediately on error
Callback	Route to an error handling branch
Continue	Continue with error data available

Common Actions

Slack

• Send message to channel
• Send direct message
• Create channel
• Add reaction

Google Sheets

• Add row
• Update row
• Delete row
• Update cell

Gmail

• Send email
• Create draft
• Add label

Notion

• Create page
• Update database record

CRM (Salesforce, HubSpot)

• Create/update contact
• Create/update deal
• Add activity log

Example

Slack: Send Message
Channel: #support
Message: New ticket #{{trigger.output.ticket_id}}
Priority: {{agent.output.structured.priority}}
Assigned to: {{condition.output.assignee}}

Next Steps

Integration Trigger

Trigger workflows from integration events

Getting Started

Build your first workflow