Integrations
Published by Argorant
Argorant with the rest of your stack.
How Argorant connects to the rest of your stack
Four connection shapes, and which one your tool uses.
Connect Google Workspace mailboxes
A Workspace admin authorises Argorant once per domain, then every mailbox on the domain can send. No login per mailbox. About three minutes.
Connect a Microsoft 365 or Outlook mailbox
Turn on Authenticated SMTP and IMAP for the user once, then connect with a normal Microsoft sign-in. About three minutes.
n8n: the Argorant node
Community node or HTTP Request, plus exposing Argorant as a tool to n8n AI agents.
Zapier: connect with Webhooks by Zapier
No native tile yet, and none needed. One header and you are connected.
Make: HTTP modules against the Argorant API
One connection, four module recipes, full JSON to map from.
Clay: Argorant as an HTTP API enrichment column
Row-by-row enrichment inside your Clay tables, no marketplace install.
HubSpot: push verified exports into your CRM
OAuth once, then a button on every completed export.
Pipedrive: push verified exports into your pipeline
OAuth against your own Pipedrive domain, then one button per export.
Salesforce: CSV import or API automation
Two paths. One takes minutes, the other runs itself.
Smartlead: push a list into a campaign
Paste your Smartlead API key once, then send exports straight into any campaign.
Instantly: import a verified export
The CSV drops straight into a campaign, no column wrangling.
lemlist: import a verified export
Fields map one to one, and the API path keeps campaigns fed.
Google Sheets: send an export to a fresh spreadsheet
One narrow permission, one button, no download and re-upload.
What is in an Argorant export file
The columns you get, and how they map into common tools.
Scheduled refreshes and event-triggered runs
Keep a segment current with a schedule, or fire on an event from your own stack.