TurboFlow Triggers and Actions

Build workflows with triggers, actions, and logic nodes

TurboFlow workflows start with a trigger, move through one or more actions, and branch with logic nodes. This reference documents every available node type, the exact configuration fields each node accepts, and the output each node exposes to downstream nodes.

How node outputs flow through a workflow

Each node adds its result to the workflow context under that node's ID. Downstream nodes can reference those values with expressions, which lets you pass trigger payloads into actions, reuse action results, and branch on logic outcomes.

Expression syntax

Expressions use double curly braces around a path. The path usually starts with a node ID, followed by the output field you want to read.

Common expression examples

Trigger nodes

Triggers start a workflow. Every flow uses a trigger as its entry point, and some triggers also verify incoming events from external integrations.

webhook_trigger

webhook_trigger is the universal entry point for every flow. It supports direct external webhooks and optional voice tool exposure for AI assistants.

What this trigger does

• External webhook receiver — any external system can send a POST request to the flow's trigger URL.
• Voice tool — when voice_tool.exposed is enabled, the same trigger is registered as a callable tool for voice assistants.

Configuration fields

ParameterDef fields

Use one ParameterDef object for each tool parameter.

Output fields

Downstream nodes can read incoming trigger data from trigger.body.

Example voice tool configuration

{
  "voice_tool": {
    "exposed": true,
    "tool_name": "book_calendly_meeting",
    "tool_description": "Books a meeting for the caller and returns the booking result",
    "parameters": [
      {
        "name": "full_name",
        "type": "string",
        "description": "Caller full name",
        "source": "ai",
        "required": true
      },
      {
        "name": "email",
        "type": "string",
        "description": "Best email address for the meeting invite",
        "source": "ai",
        "required": true
      },
      {
        "name": "meeting_type",
        "type": "string",
        "description": "Meeting type to book",
        "source": "static",
        "static_value": "demo_call"
      }
    ]
  }
}

Integration triggers

Integration triggers start a workflow from verified events sent by external systems.

Supported integration triggers

Meta trigger configuration

Use these fields when configuring the Meta lead trigger.

Action nodes

Actions perform work after a trigger fires. They can call external APIs, create or update CRM data, start outbound calls, or shape the workflow's final response.

http_request

http_request sends an HTTP request to any reachable URL and exposes the full response to downstream nodes.

Configuration fields

Output fields

Example configuration

{
  "url": "https://api.acmecrm.com/v1/leads",
  "method": "POST",
  "headers": {
    "Authorization": "Bearer dkai_example_9xmk7q2r",
    "Content-Type": "application/json"
  },
  "body": {
    "email": "{{trigger.body.email}}",
    "name": "{{trigger.body.full_name}}"
  },
  "timeout_seconds": 30
}

talkturo_upsert_contact

talkturo_upsert_contact creates or updates a CRM contact. Matching happens by phone first, then by email.

Configuration fields

Output fields

Example configuration

{
  "first_name": "{{trigger.body.first_name}}",
  "last_name": "{{trigger.body.last_name}}",
  "phone": "{{trigger.body.phone}}",
  "email": "{{trigger.body.email}}",
  "source": "web_form",
  "tags": [
    "demo-request",
    "priority-lead"
  ]
}

talkturo_call_contact

talkturo_call_contact places an outbound AI call through a campaign.

Configuration fields

Output fields

Example configuration

{
  "contact_id": "{{talkturo_upsert_contact.contact_id}}",
  "campaign_id": "cmp_7af42c1d9e",
  "timing_mode": "schedule",
  "scheduled_at": "{{trigger.body.follow_up_time}}"
}

format_output

format_output shapes the JSON object returned by the workflow to the voice assistant.

Configuration fields

Output fields

Example configuration

{
  "mode": "fields",
  "fields": [
    {
      "key": "contact_id",
      "value": "{{talkturo_upsert_contact.contact_id}}"
    },
    {
      "key": "created",
      "value": "{{talkturo_upsert_contact.created}}"
    },
    {
      "key": "message",
      "value": "Contact saved and ready for follow-up"
    }
  ]
}

{
  "mode": "json",
  "template": {
    "contact": {
      "id": "{{talkturo_upsert_contact.contact_id}}",
      "created": "{{talkturo_upsert_contact.created}}"
    },
    "source": "{{trigger.body.source}}"
  }
}

Logic nodes

Logic nodes control which path the workflow follows next.

condition

condition evaluates two operands and sends the workflow down the true or false handle.

Configuration fields

Operators

Output fields

Example configuration

{
  "left": "{{http_request.status}}",
  "operator": "gte",
  "right": 200
}

Node reference by purpose

Use this table to choose the right node quickly.

Related pages