DocumentationUsing Connections in Workflows

Using Connections in Workflows

3 minLast updated: 2026-03-31

API Call Steps with Connections

When adding an API Call action to a workflow step, you can select a Connection from a dropdown instead of manually entering URL and credentials. The workflow engine auto-fills:

  • Base URL: From the connection's configured URL
  • Headers: Merged from connection defaults + step-specific headers
  • Authentication: Automatically applied based on the connection's auth type

Configuration

In the workflow step editor, select your connection and specify only the path and body:

{
  "action": "api_call",
  "connection_id": 5,
  "path": "/inventory/check",
  "method": "POST",
  "body": {
    "product_id": "{{trigger.product_id}}",
    "quantity": "{{trigger.quantity}}"
  }
}

The base URL, auth headers, and default headers are inherited from the Connection, you only specify what's unique to this step.

Benefits

  • No credential duplication: API keys and tokens are stored once in the Connection, not in every workflow step
  • Easy rotation: Update the token in one place when credentials change, all workflow steps using that Connection are updated automatically
  • Visual Workflow Builder: The /dashboard/workflow-builder shows a dropdown of available Connections when configuring API Call blocks

Was this article helpful?