Get replies and meetings into your CRM

Argorant has no built-in sync that writes replies or meetings into a CRM. Connected tools sends the contacts of an export to a CRM, not the replies that come back. To get replies into your CRM, use a webhook, the API, or both. They work with any CRM that n8n, Zapier, Make or your own code can reach.

How Argorant knows about meetings

Argorant does not see your calendar. It knows about a meeting from the reply itself. Every reply gets a label, and two labels are about meetings:

• Meeting request: the person asks for a call, agrees to one, proposes times or asks for a booking link. This label is on from the start.
• Meeting booked: a meeting is confirmed. It is off until you switch it on under Settings, then Workspace, More labels. You can also set it by hand in the Unibox once the meeting is in your calendar.

More on labels in Reply labels.

Way 1: a webhook

1. In your automation tool, add a step that receives a webhook and copy its address. In Zapier that is Webhooks by Zapier with the Catch Hook trigger, in Make a Custom webhook, in n8n a Webhook node. Your own server works too.
2. In Argorant, open Settings, then API keys, scroll to Webhooks and paste the address.
3. Pick reply.received and reply.positive. Add email.unsubscribed if your CRM should mark opt-outs too.
4. Click Add webhook, then Send test, so your tool sees one sample delivery.
5. In your tool, find the contact by lead_email or create it. Add a note or activity with subject and snippet, and set a status from classification.

Which event each label sends:

• A webhook goes out once, when a new reply gets its label from Argorant. If you change a label by hand later, for example to Meeting booked, no new event is sent. The API below catches those changes.
• The snippet holds the first 500 characters of the reply. For the full text, open the conversation through the API.
• Setup, signatures, retries and limits are in Webhooks.

Way 2: read replies through the API

Your flow runs on a schedule, asks for replies and writes them into the CRM. This also picks up labels your team changed by hand.

curl -s -G https://app.argorant.com/api/v1/inbox \
  -H "Authorization: Bearer $ARGORANT_API_KEY" \
  --data-urlencode "classification=meeting_request"

• GET /api/v1/inbox lists the conversations of all your campaigns with their label, newest first. Filter with classification, campaign_id or folder. Texts are cut to 400 characters here.
• GET /api/v1/inbox/{event_id} opens one conversation with the full text.
• GET /api/v1/campaigns/{campaign_id}/replies lists the replies to one campaign.

Remember which conversations are already in the CRM, so nothing lands there twice. Every field is in the API reference.

Common mistakes

• Only reply.positive picked. Then most replies never reach the CRM. Pick reply.received as well.
• Duplicates in the CRM. The same event can arrive twice, for example after a retry. Skip a delivery_id you already handled, and match contacts on their email address.
• Waiting for bookings from your calendar. Argorant only knows what the reply says and the labels your team sets. It does not see bookings made in your calendar.