Resources · n8n integration

Autobound n8n integrationAutomate Autobound with n8n.

Can a workflow write a first-touch email that really talks about the prospect? The Autobound n8n integration exposes 4 operations across 2 resources: emails, LinkedIn messages, cold call scripts and ranked insights, split across the Content and Insight resources.

Community node This node is not shipped with n8n: it is a community package (n8n-nodes-autobound) you install from Settings › Community nodes on a self-hosted instance. npm

Try the Autobound integration on n8nSee the 4 operations

Verified Trustpilot reviews · AI, automation & growth agency

Why automate

What does the Autobound n8n integration give you?

Autobound generates personalized sales content and returns insights about a contact or a company. Inside n8n, that work becomes a node you drop between two other nodes: a list of prospects goes in, generated copy or ranked insights come out, and the next node sends or stores the result. The node covers 4 operations spread over 2 resources, Content and Insight, and its maximum node version is 3.1.

Because the package is not shipped with n8n, you install it yourself. That single step aside, the node behaves like any other: one credential, a dropdown of operations, and expressions such as {{ $json.email }} to pull a value from the item coming in. Its technical name in the canvas search is n8n-nodes-autobound.autobound, and any field marked required stops the run when you leave it empty.

Outbound from a spreadsheet. A Google Sheets node reads a list of prospects, Generate an email turns each row into copy written for that person, and Gmail sends it. Nobody rewrites the same opener 30 times.

A LinkedIn touch your reps approve first. Generate a linkedin message produces the draft, and Slack posts it in the channel where the rep reads it before hitting send. Same input, different channel, no second tool.

Research before a call. Get insights returns what Autobound found on the contact or the company, and an If node splits the flow: enough signal, the workflow drafts a cold call script; nothing solid, the contact waits for the next pass.

Four operations is a small surface. Anything the Autobound API offers beyond them stays reachable through the HTTP Request node, which calls any endpoint while reusing the same credential through predefined authentication. Two other limits are worth knowing before you build: there is no Autobound trigger in n8n, so a workflow always starts somewhere else, and Number of Variations tops out at 3 and does not work with an email sequence. If you are still comparing platforms, the n8n review covers the ground.

Connect

How do you install and connect Autobound in n8n?

  1. 01

    Install the community package

    On a self-hosted n8n, open Settings then Community nodes and install the npm package n8n-nodes-autobound, version 2.3.3. Once the install finishes, the node appears in the canvas search under its technical name n8n-nodes-autobound.autobound. On n8n Cloud the list is restricted to verified community nodes, so plan for a self-hosted instance, whether you run it through Docker or npm.

  2. 02

    Create the Autobound credential once

    Head to the Credentials menu and create the Autobound credential there rather than inside a workflow. A credential built that way is stored once and offered to every workflow on the instance, so a key rotation is one edit instead of a hunt through the canvas. Nothing about this step is specific to Autobound: n8n handles all credentials the same way.

  3. 03

    Pick the resource and run one item

    Add the node, select the saved credential in its dropdown, then choose the resource, Content for generated copy or Insight for research. Run the workflow on a single prospect before you point it at a full list. A field marked required stops the node when it is empty, so a missing Insight Subtypes value fails loudly instead of returning something half built.

Actions

What can the Autobound node do?

The Autobound node exposes 4 operations across 2 resources. For each one: the node as you configure it in n8n, the required fields, and our field notes.

Resources × operations matrix
ResourceGenerate Cold Call ScriptGenerate EmailGenerate LinkedIn MessageGet Insights
Content✓✓✓
Insight✓

Content

3 operations
01

Generate an email

content.generateEmail

What you see in n8n

Notes & use cases

The operation writes an email aimed at one prospect and returns the text, ready for a sending node.

Key parameters

  • Contact Email: the prospect address, often {{ $json.contactEmail }}, or Contact LinkedIn URL.
  • User Email: the seller the copy is written for, or User LinkedIn URL.
  • Content Type: email, sequence where each email costs 2 credits, or custom, which requires Custom Content Type.
  • Writing Style: seven angles, from basho for very short notes to data_driven for metrics and ROI. On custom, Custom Writing Style becomes required.
  • Email Sequence Length: emails in the sequence, 3 by default, read only when Content Type is sequence.
Use cases
a first touch per row of a prospect list, or a sequence prepared before a campaign.
02

Generate a linkedin message

content.generateLinkedIn

What you see in n8n

Notes & use cases

Same prospect, other channel: the operation returns a LinkedIn message rather than an email, so nothing in the workflow changes except the node that delivers it.

Key parameters

  • LinkedIn Message Type: the kind of message to produce, chosen from the dropdown.
  • Tone: six values, casual, consultative, direct, formal, friendly or professional.
  • Word Count: an approximate length. Leave it empty and the system decides.
  • Number of Variations: distinct versions returned, 1 by default and 3 at most.
Use cases
a connection note written from the prospect profile, or two variations pushed to a rep who chooses before sending.
03

Generate a cold call script

content.generateColdCall

What you see in n8n

Notes & use cases

Here the output is spoken, not written: a script a rep reads before dialling, built from the same contact and seller identifiers as the other Content operations.

Key parameters

  • Call Duration Target: the length the script is written for, picked from the dropdown.
  • Additional Context: anything the generator could not know, written as instructions, up to 10,000 characters.
  • Value Proposition: your pitch, which overwrites the default Autobound would use.
  • Sales Asset: extra material such as whitepaper text or a scraped page, also capped at 10,000 characters.
Use cases
a morning batch of scripts for the accounts a rep will call, or one script regenerated after a discovery call changed the pitch.

Insight

1 operation
04

Get insights

insights.getInsights

What you see in n8n

Notes & use cases

No copy comes out of this one. It returns what Autobound knows about a contact or a company, ranked by contextual relevance, which makes it the research step before any generation.

Key parameters

  • Insight Subtypes: required, and multiple values are allowed. Autobound resolves each one and ranks them.
  • Return Top 20 Insights: switch it on and the top 20 come back ranked automatically. Off, you have to select subtypes yourself.
  • Contact Email: needed unless you supply Contact LinkedIn URL or Contact Company URL, the company domain.
Use cases
a briefing built before a meeting, or a scoring step that decides which accounts deserve a generated email at all.
Need help

Need help automating Autobound with n8n?

A person reads every message.

FAQ

Autobound and n8n, the questions that come up

01Is the Autobound n8n integration free?
On the n8n side, yes. Autobound is a community node, which means it does not ship with n8n: you install the npm package n8n-nodes-autobound, version 2.3.3, from Settings then Community nodes on a self-hosted instance. n8n costs nothing extra for that, whether you run it through Docker or npm. The catch is not price, it is availability: n8n Cloud only accepts verified community nodes, so a Cloud workspace may not let you install this one at all. What Autobound itself costs on your plan is a separate question, and this page does not cover it.
02What credentials do you need to connect Autobound to n8n?
One Autobound credential, created once. In n8n a credential lives in the Credentials menu rather than inside a workflow, and every workflow on the instance can then reuse it: the Autobound node offers it in its own dropdown once it exists. That matters more than it sounds, because a key you rotate is edited in one place instead of in each node that calls the API. The node itself has no authentication selector, so there is no method to choose before you start, only a credential to point at.
03What are the limits of the Autobound node in n8n?
Four operations over 2 resources, and that is the whole surface. Content generates emails, LinkedIn messages and cold call scripts, Insight returns research. Anything else in the Autobound API is out of reach from this node, but not out of reach from n8n: the HTTP Request node calls any endpoint and reuses the same credential through predefined authentication. Inside the operations themselves, two caps are worth remembering: Number of Variations stops at 3 and does not combine with an email sequence, and free text fields such as Additional Context have a character cap the node shows in its description.
04Does Autobound trigger an n8n workflow in real time?
No, because there is no Autobound trigger node in n8n. A workflow that uses Autobound always starts somewhere else, and you have three usual ways to do it. A Schedule Trigger fires at a fixed interval, which fits a daily batch of prospects. An n8n Webhook gives you a URL a third party service can call, so your CRM or your form provider starts the run. Or you reuse another tool trigger, a new row, a new deal, a new signup, and chain Autobound behind it. The generation step stays the same in all three cases.
05n8n or Make for Autobound?
It depends on where you want the workflow to live. Make is hosted by Make, with no self-hosting option, and it bills per operation, which is easy to forecast when volume is stable. n8n runs on n8n Cloud or on your own server through Docker or npm, so the data and the logs stay where you put them, and the cost model follows that choice rather than your operation count. For Autobound specifically the deciding factor is hosting: this is a community node installed from Settings, and that install needs an instance you control. Both platforms build workflows visually, so the visual logic is rarely what separates them.
Same platform

Other docs you might need on this stack.

Browse all integrations