24
Meetings booked in week one
“The appointments you're booking are crazy: Hugo Boss, AboutYou, Drykorn, Jack Wolfskin, all within a week.”

Christian Schmidt & Mike Klaßen
Co-Founders & Owners
Rebuilding lists and copying replies by hand is selling time gone. The Argorant node brings 54 operations into n8n, from counting a market to launching a campaign, and its trigger starts a workflow on every reply, bounce and ready list, next to everything else n8n connects.
Coming soon to n8n
Attach the Argorant node to an AI Agent as a tool. It counts the market, saves the right people to a list and drafts the campaign, and a launch only happens with Confirm Launch switched on.
Check an email inside the workflow, and Add Leads lets only valid addresses join a campaign. Your CRM and your sending tool get addresses that work.
A new reply, a reply marked interested, a bounce, an unsubscribe, a paused campaign, a ready export: the trigger starts your workflow the moment it happens, signed so only Argorant can call it.
Six workflows teams build first. Each takes a few minutes to set up in n8n and runs while you sell.


The owner sees who answered and what they wrote, in the team channel, the moment it lands.

A new Typeform entry gets a checked work email from Argorant and joins the campaign for its segment.


A running log of who answered, from which campaign and what they wrote, without copying a line.

When an address bounces or someone unsubscribes, they leave your newsletter audience as well.

Every reply goes to your own model with the full thread. It labels the reply and drafts the answer, and you decide what is sent.


When someone adds a contact by hand, Argorant fills in the job title and checks the email before anyone writes to it.
Every Argorant event can start a workflow in n8n, and any app there can ask Argorant to do the work.
Ten events, signed by Argorant. Webhooks come with the Pro plan.
Every reply a lead sends to a campaign. Out of office replies are left out.
reply.receivedA reply was labelled Interested.
reply.positiveA campaign email could not be delivered.
email.bouncedSomeone asked not to be contacted again.
email.unsubscribedA list finished filling, also after you added people.
list.readyNew people match the filters of a saved list.
segment.new_matchesAn export finished, with its download link.
export.readyA single email check finished.
verification.completedSending stopped, for example after too many bounces.
campaign.pausedSending goes on again.
campaign.resumedAny Argorant action, one request with your key.
From a name and a company website, checked before you get it.
POST /api/v1/email-finder/findThe person behind an email, a name at a company, or the company itself.
POST /api/v1/enrichValid, invalid, catch-all or risky, before it reaches another tool.
POST /api/v1/verificationsHow many people fit your filters. Free.
GET /api/v1/people/countWho fits, with contact details hidden. Free.
GET /api/v1/people/searchA search or the people you picked. Free.
POST /api/v1/listsYour own rows or a list. Only checked addresses join.
POST /api/v1/campaigns/{campaign_id}/leadsEvery reply, or only the interested ones, with the thread.
GET /api/v1/inboxInterested, not interested or any label of yours, for your own reports.
POST /api/v1/inbox/{event_id}/classifySends right away, from the mailbox that got the reply.
POST /api/v1/inbox/{event_id}/reply
On self-hosted n8n you install the Argorant node in a minute. On n8n Cloud it appears in the nodes panel once n8n has verified it. Until then, the HTTP Request node works there with the same key.
n8n-nodes-argorantCreate your account, then follow the steps above. It takes a few minutes.
Full n8n guide in the docsPublished by Argorant
Use n8n's built-in HTTP Request node with your Argorant API key stored as a credential. Useful recipes: a scheduled market count, an ICP preview with approval, a verified export that runs in the background, a HubSpot push, and a Smartlead or Instantly handoff.
Use n8n's standard node with Header Auth or bearer credentials, JSON bodies, response status, pagination, and retry logic.
The HTTP Request node can be attached as a tool to an n8n AI Agent, with the same spending and approval controls.
Community Edition can run self-hosted workflows; unverified community nodes are not available on n8n Cloud.
For ready-made fields instead of raw requests, see the Argorant node on the n8n integration page.
Store the Argorant bearer key in n8n credentials; classify 401 and 402 as intervention states, 429 and 5xx as bounded retry states.
Implement scheduled TAM count and ICP form to count and masked preview with human approval.
Create an approved export, poll the job with backoff, download, and record the result.
Push approved rows to HubSpot, Smartlead, or Instantly with stable IDs and reconciliation.
The matching count is visible before any contact is shown. Check it and a masked sample before you pay for an export or send contacts to another tool.
Customer stories
What happened when these teams put the right contacts into their outreach.
24
Meetings booked in week one
“The appointments you're booking are crazy: Hugo Boss, AboutYou, Drykorn, Jack Wolfskin, all within a week.”

Christian Schmidt & Mike Klaßen
Co-Founders & Owners
16.81%
Reply rate across the campaign
“We've gotten 16.81% in replies after working with you guys. Can only recommend you.”

Jannik Linke
Founder & CEO
€759K
Pipeline generated
“Yesterday I got confirmation for a pilot - and it was the very first appointment.”

Armin L. Rau
Founder & Managing Director
n8n + Argorant
Still have questions? Talk to us
“The appointments you're booking are crazy: Hugo Boss, AboutYou, Drykorn, Jack Wolfskin, all within a week.”
Christian Schmidt & Mike Klaßen, Co-Founders & Owners, Boldbrands · Germany