Receive a CRM's own webhook
Point Pipedrive, HubSpot, Zoho or Salesforce webhooks straight at Atlis and pick the fields, with no custom code.
Available on: Growth, Scale or an active trial
Most CRMs send their own JSON (or form fields), not Atlis's field names. /api/v1/inbound accepts that payload as-is and uses a field mapping you set once to find the user ID, email, name and any status fields.
- 1
Copy the inbound URL
In Settings → Integrations → Server API & CRM → Receive your CRM's own webhook, copy
https://theatlis.com/api/v1/inbound?key=YOUR_SECRET_KEYand replaceYOUR_SECRET_KEYwith your API key. You can send the key in anAuthorization: Bearerheader or as the Basic auth password instead. - 2
Create the webhook in your CRM
Point a POST webhook at that URL. JSON and form-encoded bodies both work.
- 3
Paste an example payload
Copy one real payload from your CRM's webhook log or test tool into Example payload. It stays in your browser. Atlis lists every field it finds.
- 4
Pick the fields
Choose the User ID field, Email field and optionally the Name field. Under Extra fields, add status fields such as
lead_status, then map their values in CRM status mapping. - 5
Check the preview and save
The preview shows exactly what Atlis would receive, including any status outcome. Click Save field mapping.
- If the User ID field is empty in a payload, Atlis uses the email as the user ID. Use the same ID your app sends so people aren't duplicated.
- Paths use dots between levels and numbers for list items, for example
data.emails.0.value. - Values that look like
{ "value": "..." }(common in HubSpot) are read automatically. - Each inbound call works like an identify call: the same plan, user-limit and status-mapping rules apply.
Pipedrive
Create a webhook in Pipedrive for person or deal events and use the inbound URL. Pipedrive can send an HTTP username and password, so you can put your API key in the password field instead of the URL. Paste a payload from a test event to pick the fields.
Salesforce
Salesforce Outbound Messages send XML, which Atlis doesn't read. Use a record-triggered Flow with an HTTP Callout action (or Apex) that POSTs JSON. You can send Atlis's own fields to /api/v1/identify, or send Salesforce field names to /api/v1/inbound and map them.
HubSpot without custom code
If your HubSpot plan includes the workflow Send a webhook action, point it at the inbound URL and map the fields from a sample payload. Otherwise use the Custom code action.
More in Server API & CRM
Try it in your own workspace
Start with a 14-day trial with Growth features. No credit card needed.
Start free