Argorant Help
EN|DEargorant.comOpen Argorant
Help/Integrations

Salesforce: CSV import or API automation

Published by Argorant

Get Argorant contacts into Salesforce: import the export file with the Data Import Wizard, or automate it with the REST API. Column mapping, duplicates and common mistakes.

Argorant has no Salesforce connection under Connected tools and no AppExchange package. You still have two dependable ways in: import the export file by hand, which takes a few minutes, or let your own code move the data with the Argorant API and the Salesforce API.

Path 1: import the export file

  1. In Argorant, build your audience and create the export. Open Exports and download the finished CSV file.
  2. In Salesforce Setup, open the Data Import Wizard and click Launch Wizard.
  3. Choose Leads (or Contacts if you file people under accounts) and Add new and update existing records.
  4. Under Match Lead by, choose Email, so a person who is already in Salesforce is updated instead of added twice.
  5. Upload the CSV file and map the columns as in the table below. Leave columns you do not need unmapped.
  6. Start the import. Salesforce emails you when it is done.

The Data Import Wizard handles up to 50,000 records per import. For bigger files, split them or use Salesforce's Data Loader. Argorant already splits exports above 50,000 rows into several files with the same columns.

Before the first import

  • Create the custom fields first. If you want to keep the LinkedIn URL or the check result, add a URL field and a text field on Leads in Setup before you start. The wizard only offers fields that exist.
  • Test with a small file. Create an export with a limit of 10, import it, and look at three records in Salesforce. Fix the mapping, then run the real file. A small test export costs at most 10 credits.
  • Save the mapping. The columns never change, so the same mapping works for every later file.
  • Decide on a lead source. Many teams set Lead Source to a value like Argorant for the whole import, so reports can tell these leads apart later.

Column mapping

Every Argorant export has the same columns, so a mapping you save once keeps working.

Export columnSalesforce Lead field
First NameFirst Name
Last NameLast Name (required by Salesforce)
TitleTitle
CompanyCompany (required for Leads)
EmailEmail, and the matching key
PhonePhone, filled only when the export included phone numbers
City, State, CountryCity, State/Province, Country
LinkedInA custom URL field, if you have one
Verify StatusA custom text field, if you want to keep the check result
Company Normalized, Additional emails, Additional phonesUsually left unmapped

The Verify Status column tells you how each address did in the check when the export was made. Most rows are valid. Catch-all rows belong to companies whose mail server accepts every address, so the address cannot be confirmed one by one; whether you include them is your choice when you create the export. If you keep this column in a custom field, your reps can see it on the Lead, and you can build a report or a list view that leaves catch-all addresses out of the first sequence step.

If your org uses State and Country picklists, the values must match your picklist entries. Rows that do not match fail in Salesforce's import, and its result email lists them.

Path 2: automate it with the API

Use this when a territory should refresh on a schedule. Your middleware, a Salesforce Flow with an HTTP callout, or a tool like n8n, Zapier or Make runs four steps:

  1. Create the export with POST /api/v1/exports, your filters and a limit.
  2. Wait until it is ready. Poll GET /api/v1/exports/{job_id} every few seconds until downloadable is true, or subscribe a webhook to export.ready and let Argorant tell you.
  3. Download the file with GET /api/v1/exports/{job_id}/download. Downloading again later is free.
  4. Upsert the rows into Salesforce on Email with Salesforce's own API, for example the Bulk API with Email as the external match.

Matching on Email in Salesforce needs a field it can match on. Many orgs mark a custom email field as an External ID for this, or use a duplicate rule on the standard Email field. Your Salesforce admin will know which one your org uses.

curl -s https://app.argorant.com/api/v1/exports \
  -H "Authorization: Bearer ag_live_xxxxxxxxxxxxxxxxxxxxxxxx" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: sf-uk-logistics-2026-10" \
  -d '{"filters": {"title": "operations manager", "keywords": "logistics", "country": "United Kingdom"}, "limit": 1000}'

The Idempotency-Key makes a retry of the same request safe: you get the first export back instead of paying for a second one.

Settings, API keys, with a newly created key and its Copy button
The automated path needs an API key from Settings, then API keys.

Keeping a territory current

Exports leave out people you already exported, by default. So a monthly export of the same filters returns only people who are new to you, and the email match in Salesforce takes care of anyone who is already there. Counts are free, so you can watch how a territory grows between imports without spending credits.

Limits

  • One Argorant export holds up to 500,000 rows. Above 50,000 rows it arrives as several files.
  • Every working email costs 1 credit when the export is created. Downloading the file again is free.
  • Search, counts and masked previews do not deduct credits. Account permissions and rate limits still apply.

Common mistakes

  • Duplicates in Salesforce. The import ran as "add new records" only, or matched on name. Use Add new and update existing records and match on Email.
  • Rows rejected for a missing company or last name. Salesforce requires both on Leads. Fill them in the file before the import or skip those rows.
  • Strange characters in names. Open the file as UTF-8, or import it directly without opening and saving it in a spreadsheet first.
  • Catch-all addresses mixed in. The Verify Status column says which addresses are catch-all. Filter on it before the import if you only want valid ones.

What happens next

The people are ordinary Salesforce Leads or Contacts. Assign them with your assignment rules and start your cadence. Keep the export file for a while; if an import goes wrong, you can fix the mapping and run the same file again without paying for a new export. If you later move to HubSpot or Pipedrive, those connect directly; see HubSpot and Pipedrive.

Related
What is in an Argorant export fileREST: POST /api/mcp/exports/createWebhooksHubSpot: push verified exports into your CRM

Still stuck? support@argorant.com

Help homeargorant.comPricingRoadmap
support@argorant.com