HubSpot is a native destination in Argorant. You connect your HubSpot account once, and from then on any finished export goes into HubSpot as contacts with one button and one confirmation. There is no CSV to download, no import wizard and no key to copy.
Before you start
- Pushing into HubSpot is included from the Pro plan.
- You need a HubSpot user who may create and edit contacts in the HubSpot account that should receive them.
- You need a finished export. Build it in the app, with the API, with the CLI or through an AI connector; they all end up on the same Exports list.
Step 1: connect HubSpot
- In Argorant, open Settings, then Connected tools.
- On the HubSpot card under CRMs and sheets, click Connect HubSpot.
- HubSpot's own page opens. Sign in if asked, pick the HubSpot account if you have several, and approve. Argorant asks only for permission to read and write contacts.
- You land back in Argorant. The HubSpot card now shows Connected.

Step 2: push an export
- Stay on Connected tools. The part Send an export to a connected tool now lists your latest exports.
- Next to a finished export, click Push to HubSpot.
- A window says how many contacts go into your HubSpot account, for example "This sends 482 contacts from Export #12 into your HubSpot account. It can't be undone from Argorant."
- Click Push 482 contacts (the number is the size of your export), or Cancel.
- A note confirms the push and gives it a number. The contacts appear in HubSpot within minutes.


What happens during a push
- Argorant reads the export file and takes every row with an email address, up to 100,000 rows per push.
- Phone numbers are only included when the export itself included them.
- The contacts go to HubSpot in batches of 100. HubSpot matches each one on the email address: a new address creates a contact, an address HubSpot already has updates that contact.
- If HubSpot asks Argorant to slow down, the push waits and tries the batch again.
- When the last batch is through, the push is done. A batch HubSpot refuses is counted as failed and the push carries on with the next one.
Field mapping
| Column in the export | HubSpot contact property |
|---|---|
email (also the matching key) | |
| First Name | firstname |
| Last Name | lastname |
| Title | jobtitle |
| Company | company |
| Phone | phone |
| City | city |
| State | state |
| Country | country |
hs_linkedin_url, when your HubSpot account has this property |
Empty cells are not sent, so an empty title in the export never wipes a title you already have in HubSpot. A filled cell does overwrite the HubSpot value. Each value is cut at 250 characters. If your HubSpot account does not have the LinkedIn property, the push sends the rest without it.
Test before the big push
A push cannot be undone from Argorant, so start small. Create an export of the same audience with a limit of 10 and push it. In HubSpot, open Contacts and sort by create date. Open two or three of the new contacts and check the name, job title, company and city. If your team uses lifecycle stages, lead status or owners, check how your HubSpot workflows treated the new contacts. When it all looks right, push the real export. The 10 test contacts are matched on email and simply updated.
Check the result in HubSpot
- Filter contacts by Create date is today to see who is new.
- Contacts that already existed keep their create date; their job title, company or city may have been updated from the export.
- If you want to find these contacts again later, put them in a HubSpot list right after the push, for example a static list named after the export.
Duplicates
Because HubSpot matches on email, pushing the same export twice does not create doubles. Contacts your team created by hand before the first push are matched the same way, as long as the email address is the same. The second push updates the same contacts again. Two exports that share people also end up as one contact per person.
From your own code
Pushes into HubSpot start in the app. With an API key, GET /api/v1/integrations shows your HubSpot connection, but API pushes (POST /api/v1/integrations/{id}/pushes) only go to Smartlead and Instantly today. To automate HubSpot, download the export with the API (GET /api/v1/exports/{job_id}/download) and create the contacts with HubSpot's own API, or let a tool like Zapier or n8n do that step.
Limits
- Up to 100,000 contacts per push.
- Pushes into HubSpot are included from the Pro plan. They do not cost credits; you paid for the contacts when the export was made.
- The connection belongs to the Argorant user who made it. Teammates connect their own.
Common mistakes
- No Push to HubSpot button. HubSpot is not connected yet, or the export is still running and shows a percentage instead.
- Contacts went into the wrong HubSpot account. You approved access for another account. Disconnect, sign out of HubSpot in the browser, connect again and pick the right account.
- Some contacts are missing in HubSpot. HubSpot refused a batch, for example because the access was removed on the HubSpot side. Connect again and push the same export once more; contacts that already arrived are only updated, not doubled.
- Expecting the push to undo. It cannot be undone from Argorant. Delete or merge contacts in HubSpot itself.
What happens next
Connect HubSpot with a user whose access you expect to keep, for example a shared operations user rather than someone who may leave. If the person who connected leaves HubSpot, the connection stops working and someone else has to connect again.
The contacts are ordinary HubSpot contacts. Assign owners, add them to lists or enroll them in sequences in HubSpot. To disconnect, click Disconnect on the HubSpot card; further pushes stop and the contacts already in HubSpot stay.