Integrationsn8n

React to replies in n8n, and push leads back into GetSales.

Install the GetSales node, add your API key and pick the events. A reply, a hand-off or a website visit starts your n8n workflow, and the node's actions add people to a table or a GetSales workflow.

  • ConnectSettings, API keys
  • DirectionBoth ways
  • Credits0 per event
GetSales to n8n

What moves between GetSales and n8n: an event such as a reply, a hand-off or a website visit starts an n8n workflow through the GetSales Trigger node, and the GetSales node adds a person to a table, adds people to a GetSales workflow or finds a person.

  1. A reply, a hand-off, a visit to GetSales Trigger node

    GetSales to n8n, as an event

  2. A person in a table to Add a person to a table

    n8n to GetSales, skipped if GetSales has them

  3. People in a workflow to Add people to a workflow

    n8n to GetSales, the workflow's steps take over

  4. A person found to Find a person

    n8n reads it from GetSales

What it does

What starts an n8n workflow,
and what the node does

A trigger node for any GetSales event, with the common ones named, and a node with four actions.

Trigger node: GetSales to n8n

  • Any of these events

    Pick the GetSales events you want in one trigger. Activate the n8n workflow and it subscribes, deactivate it and the subscription goes.

  • Reply received

    A lead answered on LinkedIn or by email.

  • Task created

    A task for someone on your team, the AI SDR's hand-offs included.

  • Four more

    Conversation state changed, Lead finished or left a workflow, Website visit identified, Import or search finished.

Actions: n8n to GetSales

  • Add a person to a table

    From a form, a CRM or a database. A person GetSales already has is skipped, not changed.

  • Add people to a workflow

    Pick the GetSales workflow and they enter its steps. Anyone already in it is left alone, and your stoplist still holds.

  • Find a person

    Look a person up in your tables and use their fields in the next nodes.

  • Get a message

    The text of a reply and its conversation, for the next nodes. The reply trigger carries the message's id, not its text.

Not in this version

  • Sending messages

    n8n cannot send a LinkedIn message or an email. Add people to a GetSales workflow and its steps send.

  • Building workflows or tables

    n8n cannot create or edit a GetSales workflow, a table or a column. Build them in GetSales.

  • Connection accepted

    No trigger fires when someone accepts a connection request.

  • Updating people

    n8n cannot change the fields of a person already in GetSales.

When it runs

Activate it once,
it keeps running

The GetSales nodes run like any other node in an n8n workflow.

  1. On an event

    The trigger fires when GetSales records the event: a reply lands in Unibox, a task opens, a person leaves a GetSales workflow.

  2. Between your nodes

    The actions run after any node: a form, a CRM, a database, your own code.

  3. Then in GetSales

    A person added to a table meets its Auto-run columns, and people added to a GetSales workflow start its steps. Nobody has to press run.

What it costs

Nothing
per event

Events, reads and writes move your own data, so GetSales charges no credits for them. What an action starts in GetSales is billed as it is in the app.

What a credit costs
An event sent to n8n
0
A person added, found or added to a workflow
0
A column that runs on the new row
Its own rate
AI steps and the AI SDR's work in the workflow
As in the app

Set it up

Connected
in five steps

  1. Create a key

    In GetSales, open Settings, API keys and click Create key. Pick the Automation platform preset, name it n8n and copy the secret: it is shown once.

  2. Install the node

    On a self-hosted n8n, an owner or admin opens Settings, Community nodes, clicks Install and enters the package name, @getsales/n8n-nodes-getsales. On n8n Cloud, it is added from the nodes panel once n8n lists it there.

  3. Add the credential

    Create a GetSales credential in n8n with the key.

  4. Pick the events

    Add the GetSales Trigger node and, under Trigger on, choose a named trigger such as Reply received, or Any of these events to pick your own.

  5. Activate

    Add the actions you need, test the n8n workflow once, then activate it. The trigger subscribes when you do.

You need a GetSales user who can manage API keys and, on a self-hosted n8n, an owner or admin to install the node. A key works for one workspace.

Questions

n8n,
your questions

Anything else, ask our AI sales agent.

Talk to AI Sales

How does the GetSales node for n8n work?

Install the GetSales node in n8n and add a credential with an API key from GetSales. The GetSales Trigger node starts an n8n workflow on the events you pick, and the GetSales node adds a person to a table, adds people to a GetSales workflow, finds a person or reads a reply's message.

Which events can start an n8n workflow?

Any of these events takes any event GetSales sends to webhooks, picked from a list. The named triggers cover the common ones: Reply received, Task created (it carries the AI SDR's hand-offs), Conversation state changed, Lead finished or left a workflow, Website visit identified, and Import or search finished.

Does it work on self-hosted n8n?

Yes. An owner or admin installs it from Settings, Community nodes, by its package name, @getsales/n8n-nodes-getsales, and it runs on your own instance.

Does it work on n8n Cloud?

Not yet. n8n Cloud runs only the community nodes n8n has approved, and the GetSales node is not one of them yet. Self-hosted n8n works, and any n8n, Cloud included, can call the GetSales API from an HTTP Request node with the same key.

Can n8n add people to a GetSales workflow?

Yes. Add a person to a table or find one, then use Add people to a workflow with the GetSales workflow picked. They enter its steps as people added by hand do, and a person on your stoplist does not enter. Anyone the workflow holds already is left as they are, so a run repeated with the same people starts nobody twice.

Can I send LinkedIn messages or emails from n8n?

Not in this version. Sending stays in GetSales: add the person to a GetSales workflow and its steps send from your sender profiles, paced within each account's limits.

What happens when a person is already in GetSales?

Add a person to a table skips them and returns the person GetSales has, so the next node can still add them to a workflow. Their fields are not changed: updating people is not in this version.

Does the n8n integration cost credits?

Events, reads and writes cost no credits. What an action starts is billed as it is in the app: a column with Auto-run on the new row at its own rate, and the AI work of a workflow step or the AI SDR. What a credit costs is on the pricing page.

Your flows, connected

Every reply, in your own flows.

Install the node once. GetSales events run your n8n workflows, and n8n keeps your tables and GetSales workflows filled.

Replies in GetSales. Your logic in your own nodes.