Action Node

Perform external actions like sending emails, Slack messages, API calls, and creating tickets.

Overview

The Action Node executes external operations during workflow execution. It connects your chatbot to the outside world—sending notifications, updating systems, and triggering processes based on conversation outcomes.

Supported Actions

Send Email
Send emails to users or team members

Configure email delivery with your preferred provider and customize templates with dynamic variables from the conversation.

Supported Providers

SMTPSendGridMailgunAWS SES

Configuration Options

  • Recipient email (static or from form data)
  • Subject line with dynamic variables
  • Email body/template with dynamic variables
  • Retry on failure
  • Continue on error (don't block workflow)
Send Slack Message
Post messages to Slack channels or direct messages

Integrate with Slack to notify your team about important conversation events, new leads, or support requests.

Configuration Options

  • Channel or DM selection
  • Message body with dynamic variables
  • Retry on failure
  • Continue on error
Use Case: Notify your sales team in #leads channel when a high-value prospect fills out a contact form.
API Call
Make HTTP requests to external APIs

Invoke any REST API to integrate with CRMs, databases, webhooks, or custom backend services.

Supported Methods

GETPOSTPUTPATCHDELETE

Authentication Methods

  • Basic Auth: Username and password
  • Bearer Token: JWT or API tokens
  • API Key: Header or query parameter
  • OAuth 2.0: Full OAuth flow support

Request Configuration

  • URL endpoint
  • Headers
  • Request body with dynamic variables
  • Retry on failure
  • Continue on error
Create Zendesk Ticket
Automatically create support tickets in Zendesk

Create tickets directly from conversations when issues need human follow-up or escalation.

Ticket Configuration

  • Subject: Ticket title with dynamic variables
  • Description: Detailed content with conversation context
  • Priority: Low, Normal, High, Urgent
  • Type: Question, Incident, Problem, Task
  • Tags: Custom tags for categorization
  • Custom Fields: Map to your Zendesk custom fields

Error Handling

  • Retry on failure
  • Continue on error

Using Dynamic Variables

All action types support dynamic variables that pull data from the conversation:

  • Form field values
  • Previous node responses
  • Agent node outputs
  • User information

Example: Email with Form Data

Subject: New inquiry from {{form.name}}

Hi Team,

We received a new inquiry:

Name: {{form.name}}
Email: {{form.email}}
Company: {{form.company}}
Message: {{form.message}}

Intent: {{agent.classified_intent}}

Please follow up within 24 hours.

Error Handling

All actions support robust error handling options:

Retry on Failure

Automatically retry the action if it fails. Useful for transient network issues or temporary service unavailability.

Continue on Error

If the action fails, continue with the workflow instead of stopping. The conversation proceeds normally.

Best Practices

  • 1

    Enable "Continue on Error" for non-critical actions

    Don't let a failed notification break the user experience.

  • 2

    Test integrations thoroughly

    Verify API credentials and test with sample data before going live.

  • 3

    Use meaningful ticket subjects

    Include key information in Zendesk ticket subjects for easy triage.

Next Steps

End Node

Complete your workflow and attach widgets

Email Provider Setup

Configure SMTP, SendGrid, Mailgun, or AWS SES