Argorant Help
EN|DEargorant.comOpen Argorant
Help/Integrations

How Argorant connects to the rest of your stack

Published by Argorant

The ways Argorant connects to your CRM, spreadsheet, sending tool, automation platform and browser, which one each tool uses, and how to choose.

Argorant finds people and checks their email addresses. Most teams then want those people somewhere else: in a CRM, a spreadsheet, a sending tool or an automation. Every integration works in one of a few ways. Knowing which one your tool uses tells you what the setup looks like before you read a single step.

The ways

WayToolsSetupWhere you work
Push with a sign-inHubSpot, PipedriveConnect once under Connected tools and approve in the toolPush buttons under Connected tools
One-click sheetGoogle SheetsApprove Google access onceSend to Google Sheets on the Exports page
Lists and replies in your workspaceNotion, LinearConnect once under Connected tools and approve in the toolSend to Notion on a list page, and rules that turn replies and finished campaigns into rows or issues
Push with the tool's API keyInstantly, Smartlead, lemlist, PlusVibePaste that tool's API key under Connected toolsPush buttons under Connected tools, or Push to your sequencer on Exports
The Argorant app in your automation toolZapier, Make, n8n, AlbatoAn Argorant API key, pasted onceTriggers and actions inside the tool. Until an app is listed, the tool's HTTP step reaches the same API
The browser extensionChrome, Firefox, EdgeAn Argorant API key, pasted onceThe extension's window on any company website. In review at the three stores, out soon
Your own codeClay, Salesforce, the CLI and anything with HTTPAn Argorant API keyThe REST API, the CLI or webhooks

And one fallback works for every tool: every export is a CSV file with the same columns every time, so any tool that imports CSV files works today with no setup at all.

Settings, Connected tools, with the CRMs and sheets cards for Google Sheets, HubSpot and Pipedrive
Settings, Connected tools. The CRMs and sheets connect with a sign-in in the tool.

Which tools need an Argorant API key and which sign in instead is listed in Which key goes where.

How to choose

  • Your CRM is HubSpot or Pipedrive. Connect it and push. See HubSpot or Pipedrive.
  • You send campaigns in Instantly, Smartlead, lemlist or PlusVibe. Connect the tool with its API key and push into an existing campaign. Only valid addresses go in, and Argorant never starts the campaign.
  • You want to look at the list with your team first. Send it to Google Sheets. Or send it to Notion, where every list becomes its own database. See Notion.
  • Your team plans its work in Linear. Let positive replies and finished campaigns open issues there. See Linear.
  • Your CRM is Salesforce or something else. Import the CSV file, or automate it with the API. See Salesforce.
  • Things should happen on their own. Use the Argorant app for Zapier, Make, n8n or Albato: a positive reply, a new person in a list or a finished campaign starts your flow, and ready-made steps find leads, check emails and fill lists and campaigns. See Zapier, Make, n8n and Albato. To log replies and meetings in your CRM, see Get replies and meetings into your CRM.
  • You find companies while you browse. The browser extension shows who works at the company whose website you are on and reveals a checked email. See The browser extension.

Connect a tool

  1. Open Settings, Connected tools.
  2. Click Connect on the tool's card. HubSpot, Pipedrive and Google Sheets open their own sign-in, and so do Notion and Linear. Sending tools ask for their API key and say where to find it.
  3. The card shows Connected. For CRMs and sending tools, the part Send an export to a connected tool appears below.

The full walkthrough is in Connected tools.

Finished exports with Push to HubSpot, Push to Pipedrive and Download buttons
Once a tool is connected, every finished export gets a push button for it.

The automation path

Zapier, Make, n8n and Albato each have an Argorant app: you paste an API key once and pick triggers and actions from a list. While an app is still on its way to a tool's directory, that tool's HTTP step does the same with one header.

Everything else talks to the Argorant REST API with an API key. A common pattern: count for free, create an export, wait for export.ready (or poll the status), download the file, hand the rows to the next step.

curl -s -G https://app.argorant.com/api/v1/people/count \
  -H "Authorization: Bearer $ARGORANT_API_KEY" \
  --data-urlencode "title=CFO" --data-urlencode "country=Germany"

Setup guides for each platform: n8n, Zapier, Make, Albato and Clay. The basics of keys and calls are in API keys and the REST API.

Three setups that work well

A small sales team on HubSpot. Build the audience in the app, look at the free count and the masked preview, create an export of a few hundred people, and push it into HubSpot from Connected tools. Owners and sequences are then set in HubSpot as usual.

An agency that sends from Smartlead. Connect Smartlead with its API key. For each client, export the audience and push it into that client's existing Smartlead campaign. Only valid addresses go in, so bounce rates stay low, and the campaign starts only when you start it in Smartlead.

A RevOps team with n8n and Salesforce. An n8n flow runs once a month. It creates an export with an API key and an Idempotency-Key, waits for the export.ready webhook, downloads the file and upserts the rows into Salesforce on Email. Exports leave out people exported before, so each run brings only new people.

What stays the same everywhere

  • One account for the app, the API, the CLI, the apps and the AI connectors. Same credits, lists and exports.
  • Search, counts and masked previews do not deduct credits. Account permissions and rate limits still apply.
  • Email addresses are checked when the export is created, so what lands in the next tool has just been checked. Contacts with no working email are not charged.
  • Pushing into another tool costs no credits. You pay once, when the export is made.
  • Nothing is pushed from Connected tools without a confirmation that names the number of contacts.

Limits

  • Pushes into CRMs and sending tools are included from the Pro plan. On the free plan, Connect opens the upgrade screen.
  • Notion and Linear are included from the Pro plan.
  • Up to 100,000 contacts per push. One export can hold up to 500,000 rows.
  • Webhooks come with the Pro plan and up, with up to 10 per account. Albato's triggers are webhooks; the Zapier and Make triggers are not.
  • Connections belong to the person who made them. Teammates connect their own.

Common mistakes

  • Looking for a Salesforce or Instantly import wizard in Argorant. Salesforce uses the CSV file or the API. Instantly connects with its API key under Sending tools.
  • Expecting Argorant to start a campaign in a sending tool. It only loads people into a campaign you already have.
  • Sharing one API key across all automations. Create one per tool, so you can switch one off without breaking the rest.
  • Pasting an API key into Claude or ChatGPT. AI apps sign in to Argorant instead. See Which key goes where.

What happens next

Pick the guide for your tool from the list above. Copy-paste recipes for developers are at docs.argorant.com.

Related
Which key goes whereConnected tools: CRMs, sheets, sending tools, Notion and LinearZapier: the Argorant appMake: the Argorant appn8n: the Argorant nodeThe browser extension: people and checked emails on any company website

Still stuck? support@argorant.com

Help homeargorant.comPricingRoadmap
support@argorant.com