Resources · n8n integration

E-goi n8n integrationAutomate E-goi with n8n.

Your E-goi lists should fill themselves while you work on something else. The E-goi n8n integration exposes 1 resource, contacts, and 4 operations on it, from a node that already sits in your n8n instance. There is no E-goi trigger, so another step starts the run.

Try the E-goi integration on n8nSee the 4 operations

Verified Trustpilot reviews · AI, automation & growth agency

Why automate

What does the E-goi n8n integration give you?

It is the built-in E-goi node plus one credential, the stored login n8n keeps for an account, holding your API key. The node works on a single resource, contacts, with 4 operations: create a member, get a member, get many members, update a member. Each one runs against a list you choose in the node, and whatever comes back becomes ordinary workflow data for the next step.

Start with the case most teams build first. A sign-up form drops a row somewhere, often in Google Sheets, and a scheduled workflow walks the new rows and calls Create a member for each one. The address goes in Email, the destination goes in List Name or ID, and Tag Names or IDs attaches the tag that says where the person came from. Nobody exports a CSV on Monday morning.

The second case is hygiene. When someone cancels, churns or asks to be left alone, the source of truth is usually your CRM or your billing tool, not your email lists. Update a member writes the new Status on the E-goi side, and a short message in Slack tells the team the change went through. Two systems, one version of the truth.

The third case runs the other way. Get many members with Return All on reads a whole list, and the workflow turns it into a weekly count posted to Telegram or written back into a sheet. It is a small habit that makes list growth visible without anyone opening a dashboard.

Anything that falls outside those 4 operations is a job for the HTTP Request node. It calls any endpoint of the E-goi API and reuses the same credential through predefined authentication, so you are not juggling a second copy of your API key. Build the workflow with the E-goi node where it fits, and drop to HTTP Request for the rest.

Two things to plan around. E-goi has no trigger node in n8n, so every workflow starts elsewhere: a Schedule Trigger on a fixed interval, the n8n Webhook node called by another service, or the trigger of a tool you already automate. And the node returns the contact ID alone unless Resolve Data is on, which changes what the next step can read. Our n8n review covers how that plays out across tools, and the n8n training walks through building the first one.

Connect

How do you connect E-goi to n8n?

  1. 01

    Generate the API key in E-goi

    You need an E-goi account first. The node authenticates with a single method, an API key, and E-goi documents where to generate and view that key in its own help desk. Copy it once and keep it somewhere safe, because it is the only secret n8n will ask for. No OAuth screen, no scope list, no callback URL to register on either side.

  2. 02

    Store it as an n8n credential

    In n8n, open the Credentials menu and create an E-goi credential, then paste the key into the API Key field. A credential is created once and reused by every workflow in the instance, so a key rotation is a single edit rather than a change repeated node by node. The same screens exist on n8n Cloud and on a self-hosted install, with no difference in behavior.

  3. 03

    Point the node at a list

    Add the E-goi node, pick your credential from its dropdown, then choose the resource Contact and the operation you want. The List Name or ID field offers your lists once the credential works, which is the fastest proof that the key is valid. Run Get many members with a small Limit and read the output before you connect anything after it.

Actions

What can the E-goi node do?

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

Resources × operations matrix
ResourceCreateGetGet ManyUpdate
Contact✓✓✓✓

Contact

4 operations
01

Create a member

contact.create

What you see in n8n

Notes & use cases

Registers a new subscriber in one E-goi list. The response carries the contact ID and nothing else, unless you ask for more.

Key parameters

  • Email: the subscriber address, in the name@email.com shape.
  • List Name or ID: where the member lands, from the dropdown or as a list ID in an expression.
  • Additional Fields: 7 optional fields, including First Name, Cellphone, Birth Date and Tag Names or IDs.
  • Resolve Data: on, the contact data comes back instead of the ID alone.
Use cases
a sign-up arrives, the workflow creates the member and attaches the tag matching the offer, so the segment is already correct before the first send goes out.
02

Get a member

contact.get

What you see in n8n

Notes & use cases

Pulls one subscriber into the workflow so the next step works on real values instead of assumptions.

Key parameters

  • By: search on id or on email, which decides which of the next two fields you fill.
  • Contact ID or Email: the value that identifies the subscriber.
  • List Name or ID: the list being searched.
  • Simplify: on, n8n hands back a trimmed response rather than the raw data.
Use cases
before any send, check whether the address is already in the list, then route the run so a known contact gets an update and an unknown one gets created.
03

Get many members

contact.getAll

What you see in n8n

Notes & use cases

Reads the members of a list in bulk, for the times the workflow needs the audience rather than one person.

Key parameters

  • Return All: on, n8n walks the API pages until the whole list is back; off, Limit caps the result.
  • Limit: the ceiling that applies while Return All stays off.
  • List Name or ID: the list being read.
  • Simplify: keeps the output readable when a few values per member are enough.
Use cases
a weekly export into a spreadsheet for the marketing review. Build with Return All off, switch it on at the end, or every test run drags the full list through the workflow.
04

Update a member

contact.update

What you see in n8n

Notes & use cases

Changes values on a subscriber who is already in the list, touching only the fields you add.

Key parameters

  • Contact ID: the subscriber to modify, usually carried in from an earlier step.
  • Update Fields: 8 fields, among them Email, Last Name, Extra Fields and Status, whose values are unconfirmed, active, inactive and removed.
  • Resolve Data: returns the contact data rather than the identifier.
Use cases
an opt-out recorded elsewhere sets Status to removed in E-goi. Holding only an email? Run Get a member first, then feed its result here.
Need help

Need help automating E-goi with n8n?

A person reads every message.

FAQ

E-goi and n8n: common questions

01Is the E-goi n8n integration free?
Yes, on the n8n side. The E-goi node ships with n8n, so there is nothing to install and nothing extra to pay for using it. That holds on n8n Cloud, the hosted offer run by n8n, and on your own instance installed with Docker or npm under the Community Edition and its Sustainable Use license. A workflow behaves the same way in both places, so you can assemble it on Cloud and move it to a server later without rewriting anything. What your E-goi account itself costs is a separate matter and depends on your plan there, which this page does not cover. On the n8n side, all you need is a credential holding your API key.
02What credentials does the E-goi node need?
One API key. E-goi supports a single authentication method for this node, and the credential holds a single field, API Key. You create an E-goi account, generate the key following E-goi's own help desk instructions, then paste it into a credential in the n8n Credentials menu. From there, every E-goi node in every workflow offers that credential in its dropdown, so you configure it once rather than per node. There is no scope to pick and no consent screen to approve, which also means the key carries whatever access your E-goi account has. Treat it accordingly and rotate it in the one place it lives.
03What are the limits of the E-goi node?
The catalogue is what you see: 4 operations on 1 resource, contacts. Anything beyond those 4 operations goes through the HTTP Request node, which calls any endpoint of the E-goi API and reuses the same credential through predefined authentication, so you keep one secret and one place to rotate it. The other practical limit is volume. Get many members returns up to the value in Limit unless Return All is on, in which case n8n chains the API pages until the whole list is back. On a large list that means many items flowing into every node downstream, so filter early rather than late.
04Can an n8n workflow react to E-goi in real time?
Not from E-goi itself, because this tool has no trigger node in n8n. A trigger is the step that starts a workflow, and here it has to come from somewhere else. Three options cover most builds. A Schedule Trigger runs the workflow on a fixed interval, which fits list reads and nightly syncs. The n8n Webhook node gives you a URL that another service calls, a webhook, so a form or an app can start the run the moment something happens on its side. Or the trigger of another tool you already automate starts the workflow, and the E-goi node runs as one step inside it.
05n8n or Make for E-goi?
It depends on four things, and price is only one of them. Make is a hosted automation platform with no self-hosting option, billed per operation, so cost tracks volume and your data always transits through their infrastructure. n8n runs either way: on n8n Cloud if you want none of the maintenance, or on your own server with Docker or npm if you need the data and the logs to stay with you. The visual logic differs too, and that is a matter of taste more than capability. For an E-goi workflow that reads a full list on a schedule, the per-operation model is the variable worth checking first.
Same platform

Other docs you might need on this stack.

Browse all integrations