Use n8n's HTTP Request nodes to call Autobound's API and build any outbound workflow you can imagine.

How n8n Connects to Autobound (API + Webhooks)

There is no dedicated Autobound node in n8n's node library. Instead, the integration uses n8n's built-in HTTP Request node to call Autobound's REST API -- the same API infrastructure that powers integrations with Clay, custom scripts, and any other tool that speaks HTTP. This approach gives you more flexibility than a pre-built node would, because you have full control over request parameters, headers, and response handling.

The core workflow pattern is straightforward:

Trigger: Any n8n trigger node starts the workflow. This could be a Webhook node receiving data from your CRM, a Schedule node running every hour, a Google Sheets trigger watching for new rows, or a Salesforce trigger firing on record updates. n8n supports over 1,000 integrations, so virtually any event in your GTM stack can kick off the workflow.

Enrich and Send: An HTTP Request node sends prospect data to Autobound's API endpoint (POST /api/workflows/campaigns/{campaignId}/execute/). The request body includes the prospect's email or LinkedIn URL as the required identifier, plus optional fields like name, company name, and domain for richer personalization. Autobound processes the request using 400+ real-time buyer signals and returns AI-generated content.

Handle the Response: Autobound can return content synchronously in the API response or asynchronously via webhook. For webhook-based flows, configure a separate Webhook node in n8n to receive the finished content when Autobound completes generation. This is especially useful for bulk workflows where processing takes longer.

Route and Act: Once you have the generated content, n8n's branching logic lets you do anything with it. Push it to your CRM via API, send it through an email tool, post it to Slack for review, append it to a spreadsheet, or feed it into another workflow. The output is standard JSON, so it works with any downstream node.

Why API-Powered Integration Beats a Pre-Built Node

Pre-built nodes are convenient for simple use cases, but they lock you into the node author's assumptions about how the integration should work. With Autobound's API approach, you get access to the full range of Autobound functionality -- campaign execution, content generation, signal retrieval, and webhook exports -- without waiting for a node maintainer to add features.

You also get version control. When Autobound adds new API parameters or capabilities, you can adopt them immediately by updating your HTTP Request node configuration. There is no dependency on a third-party node package release cycle.

For teams already comfortable with n8n's HTTP Request node (which is one of the most commonly used nodes on the platform), the setup is familiar. You configure the URL, method, headers, and body just like any other API call.

Common Workflow Patterns

CRM-Triggered Outreach: A Salesforce or HubSpot trigger fires when a new lead is created or a deal stage changes. The workflow sends the contact to Autobound's API, receives personalized content, and pushes it back to the CRM as a custom field or directly into a sequence tool like Outreach or Salesloft.

Spreadsheet-Based Campaigns: A Google Sheets trigger watches for new rows added by your marketing or SDR team. Each new row triggers an API call to Autobound, and the generated content is written back to adjacent columns for review before sending.

Scheduled Batch Processing: A Schedule node runs nightly, pulling a list of prospects from your database or CRM, sending each one to Autobound's API, and storing the results for next-day outreach.

Webhook-to-Webhook Pipeline: An external system (like a form submission tool or lead scoring platform) fires a webhook to n8n. The workflow enriches the lead with Autobound content and forwards the complete package to your sales engagement platform via another API call.

Human-in-the-Loop Review: After Autobound generates content, the workflow posts it to a Slack channel or Google Sheet. A team member reviews and approves the content, and a second workflow (triggered by a Slack reaction or sheet checkbox) sends the approved messages through your outreach tool.