Resources · n8n integration

Humantic AI n8n integrationAutomate Humantic AI with n8n.

Buyer research should not sit outside the workflow. The Humantic AI n8n integration gives you one resource, Profile, and 3 operations on it: create an analysis, read it back, update it. There is no Humantic AI trigger, so the run starts elsewhere in n8n. Built for sales and recruiting teams.

Try the Humantic AI integration on n8nSee the 3 operations

Verified Trustpilot reviews · AI, automation & growth agency

Why automate

What does the Humantic AI n8n integration actually cover?

The Humantic AI n8n integration is a node that ships with n8n and talks to the Humantic AI API on your behalf. It handles a single resource, Profile, through 3 operations: create a profile, get a profile, update a profile. Authentication goes through a credential, meaning a set of saved connection details, that holds an API key and is picked from a dropdown once it exists.

The most common setup is the one that runs before a sales call. A meeting gets booked, the row lands in Google Sheets, and a Schedule Trigger walks the new rows each morning. profile.create registers the prospect from their LinkedIn profile URL, and further down the workflow profile.get reads the result back with the Persona option set to sales. The rep finds it waiting in Slack.

Recruiting runs the same loop against a different persona. Each candidate row carries a LinkedIn URL, so the create step needs nothing else, and the read asks for hiring. Persona accepts several values separated by a comma, which matters when the same person is being looked at for two reasons at once.

Resumes make the third pattern, and it works differently. An attachment arriving through Gmail is passed to profile.create with Send Resume switched on and Input Binary Field naming the binary property that carries the PDF or DOCX. Because a resume is being sent, User ID has to be a unique string you decide on, not a URL, and that same string is what profile.get expects later.

Outside those 3 operations, the HTTP Request node calls any other Humantic AI endpoint and reuses the same credential through predefined authentication, so the key still lives in one place. One thing to plan for: Humantic AI has no trigger node in n8n. A workflow that involves it starts from a Schedule Trigger at a fixed interval, from an n8n Webhook (a URL a third-party service calls), or from another tool's trigger.

If the platform choice is still open, the n8n review goes through how it holds up on this kind of enrichment job, and n8n training is there when the team would rather build these flows in-house.

Connect

How do you connect Humantic AI to n8n?

  1. 01

    Open the Humantic AI account first

    The credential has nothing to fill in until a Humantic AI account exists, so that comes first. The key itself is issued from the Humantic AI API page, which is also where an API key can be tried as a free trial. That trial key is enough to wire a first workflow end to end and see what create and get return before anyone commits to a wider rollout.

  2. 02

    Save the key as a credential in n8n

    In n8n, open the Credentials menu and add a Humantic AI entry. A credential is a saved set of connection details, and this one asks for a single value: API Key. Paste the key from the Humantic AI API page and save. From that point the credential is available to every workflow on the instance, so the key never has to be copied around again.

  3. 03

    Drop the node in and pick an operation

    Add the Humantic AI node to a workflow and select the credential in its dropdown. Resource is Profile, and the operation is one of the 3 on offer. Each of them asks for User ID, which is required: leave it empty and the node stops the execution instead of running. Most of the time it gets filled by an expression such as {{ $json.field }}, which reads a field off the item coming in.

Actions

What can the Humantic AI node do?

The Humantic AI node exposes 3 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
ResourceCreateGetUpdate
Profile✓✓✓

Profile

3 operations
01

Create a profile

profile.create

What you see in n8n

Notes & use cases

Registers a person with Humantic AI and starts the analysis under the identifier you hand over. Everything afterwards hangs on it.

Key parameters

  • User ID: the LinkedIn profile URL or the email ID the Humantic profile is created from, usually {{ $json.field }} taken from the node before. When a resume is being sent, this has to be a unique string instead.
  • Send Resume: whether a resume is sent, for a resume based analysis.
  • Input Binary Field: the name of the input binary field holding the resume, in PDF or DOCX format.
Use cases
a prospect added to a list in the morning gets a profile in the same pass, so the analysis exists before a rep opens the record.
02

Get a profile

profile.get

What you see in n8n

Notes & use cases

Reads back the profile stored under an identifier and hands it to the rest of the workflow as regular JSON, ready for {{ $json.field }} in the next node.

Key parameters

  • User ID: the same value given when the analysis was created, so a LinkedIn URL, an email ID, or the unique string used for a resume based analysis.
  • Persona: sits under Options and fetches the profile for a particular persona type, sales or hiring. Several persona values are supported when a comma separates them.
Use cases
minutes before a discovery call, the workflow pulls the profile for the persona that rep works under and posts it in the channel they already live in.
03

Update a profile

profile.update

What you see in n8n

Notes & use cases

Sends extra material about someone whose analysis already exists in Humantic AI, using the identifier it was filed under.

Key parameters

  • User ID: the value provided when the analysis was created. This operation is currently only supported for profiles created using a LinkedIn URL.
  • Text: additional text written by the user.
  • Send Resume: whether a resume of the user is sent.
  • Input Binary Field: the name of the input binary field containing the resume, in PDF or DOCX format.
Use cases
once a call is over, the notes a rep typed go into Text so the profile reflects what the conversation turned up.
Need help

Need help automating Humantic AI with n8n?

A person reads every message.

FAQ

Humantic AI and n8n, the questions that come up next

01Is the Humantic AI n8n integration free?
On the n8n side, yes. The Humantic AI node ships with n8n, so there is nothing to install and nothing extra to pay for it, whether the workflow runs on n8n Cloud or on a self-hosted instance under the Community Edition and its Sustainable Use license. What Humantic AI itself costs is a separate matter this page does not get into. The credentials documentation does say an API key can be tried as a free trial from the Humantic AI API page, which is enough to build a first workflow and watch what create and get actually return before anyone decides how far to take it.
02What credentials does the Humantic AI node need in n8n?
An API key. Create a Humantic AI account, then get the key from the Humantic AI API page. In n8n, open the Credentials menu, add a Humantic AI entry, and fill its only field, API Key. Save it once and it appears in the dropdown of every Humantic AI node added afterwards, in any workflow on that instance. There is no authentication selector on the node itself, so nothing else has to be chosen, and no scopes have to be granted. The same credential is what the HTTP Request node reuses through predefined authentication when a call falls outside the node.
03What are the limits of the Humantic AI node in n8n?
The node works on one resource, Profile, with 3 operations: create, get, update. Anything in the Humantic AI API beyond those is reached with the HTTP Request node, which can reuse the same credential through predefined authentication so the key stays in a single place. Two details are worth knowing before building. Update currently only supports profiles created using a LinkedIn URL. And on create, sending a resume changes what User ID means: it becomes a unique string you pick rather than a URL or an email ID, and that string is what every later call has to repeat.
04Does Humantic AI have a trigger node in n8n?
No, it does not, so the workflow has to start somewhere else. A Schedule Trigger runs it at a fixed interval, which suits a nightly pass over a list of prospects or candidates. An n8n Webhook, meaning a URL another service calls, kicks the run off the moment that service has something new. Or another tool's trigger does the work: a new row, a new message, a new form entry. From there the Humantic AI node is simply the next step in the chain, and the identifier it receives decides which profile gets created or read.
05n8n or Make for Humantic AI?
It depends on where the data should sit and how the bill should behave. Make is hosted by Make, with no self-hosting option, and it is billed per operation, so a large enrichment pass costs more as the number of people processed grows. n8n runs on n8n Cloud or on a server you control, which keeps profile data inside your own infrastructure, and the workflow is identical in both cases. Both offer a visual canvas to build on. The decision comes down to hosting, control over the data, and the cost model rather than to a feature comparison.
Same platform

Other docs you might need on this stack.

Browse all integrations