Log calls from your external dialer via API

If your team calls through an external dialer (Trellus, Nooks...) alongside lemlist call steps, those calls can now be logged into lemlist as first-class calls, just like calls made with the lemlist dialer. Ask your dialer vendor to use the new API — it's documented in the Calls section of the API reference.

New routes:

  • POST /api/calls logs a call: rep, direction, numbers, start date, duration, call status, note, recording URL and transcript. The contact is matched by taskId, leadId, contactId, email or phone.

  • GET /api/call-statuses lists your team's call statuses so the dialer can map its outcomes.

  • PATCH /api/calls/{id} completes a call later, for example once the recording is ready. GET /api/calls/{id} reads a call back.

What this unlocks:

  • When a taskId is included, the call task completes with the right status and the campaign moves on automatically.

  • Call status drives the same automations as in the app: Interested / Not interested, pauses, phone number verdict, CRM outcome.

  • The recording and transcript are copied into lemlist, so they play in the call modal and feed the AI summary.

  • Logged calls show up in the timeline, the Calls page, call stats, outgoing webhooks and the CRM (Call in HubSpot, completed Task with Call Result in Salesforce, call activity in Pipedrive).

  • Each call requires an externalId from the dialer, so retries never create duplicates.

A call logged against a contact only, without a taskId or leadId, is still pushed to the CRM but doesn't trigger campaign automation. The recording URL must be public https. This is available on Email Pro plans and above, through the API only — nothing changes in the app interface. PATCH only works on calls logged through this API, not on lemlist dialer, Aircall, Ringover or manually logged calls.