Integrations

NUACOM ships ready-made integrations with HubSpot, Salesforce, Zoho, Pipedrive, Zendesk, Intercom, GoHighLevel, Microsoft Teams and others. They log calls to the CRM, match callers to CRM contacts, pull CRM contacts into the phonebook and map NUACOM users to CRM users. An account admin connects them in the NUACOM portal under Integrations: the portal runs the vendor's OAuth flow and stores the credentials. The endpoints behind those screens are not part of the public reference, because they only make sense inside that browser flow.

If NUACOM has no ready-made integration for your system, build your own with the public building blocks below. This is the route to take for any server-to-server integration.

Ready-made integrations#

An account admin connects each of these in the portal under Integrations; no code is involved. What each one does once connected:

Integration	Call details after hangup	Contacts sync	User mapping	SMS / WhatsApp push	Connection
HubSpot	Yes, with notes and tags, a link to the call in the NUACOM portal, and AI call data	On connect, then live through webhooks; full resync every Saturday	Yes	Yes, both directions	OAuth
ActiveCampaign	Yes, with notes and tags	On connect, then live through webhooks; full resync at the weekend	Yes	Yes, both directions	API tokens
Pipedrive	Yes, with notes and tags and AI call data	On connect, then live through webhooks	Yes	Yes, both directions	OAuth
Salesforce	Yes, with notes and tags and AI call data	On connect, then a full resync every Saturday	Yes	Yes, both directions	OAuth
Zoho CRM	Yes, with notes and tags and AI call data	On connect, then nightly	Yes, required	Yes, both directions	OAuth
Zoho Support	Yes	No	Yes	No	OAuth
Zoho Recruiter	Yes	No	Yes	No	OAuth
Intercom	Yes	No	Yes	No	OAuth
AutoTask	Yes, into the ticket linked to the call, with notes and tags	On connect, then live through webhooks	Yes	No	API tokens
Odoo CRM	Yes, with notes and tags and AI call data	On connect, then nightly	Yes	Yes, both directions	API tokens
OnePageCRM	Yes, with notes and tags and AI call data	On connect, then live through webhooks	Yes	Yes, both directions	API tokens
Keap CRM	Yes, with notes and tags and AI call data	On connect, then live through webhooks; full resync nightly	Yes	Yes, both directions	OAuth
Google Contacts	No	Phonebook contacts and organizations, on connect and then nightly	No	No	OAuth
Zendesk	Yes, with notes and tags (when the call listener is enabled) and AI call data	On connect, then nightly	Yes	No	OAuth
Gong	Yes	No	Yes	No	OAuth
Bullhorn	Yes, with notes and tags and AI call data	On connect, then changes pulled every two hours; full resync every Saturday	Yes	Yes, both directions	OAuth
GoHighLevel	Yes, with notes and tags, a link to the call in the NUACOM portal, and AI call data	On connect, then live through webhooks	Yes	Yes, both directions	OAuth

Connection: OAuth means you click Connect in the NUACOM portal and sign in at the vendor; API tokens means you copy an API token or ids from the vendor's settings into the NUACOM portal. User mapping pairs each NUACOM extension with a user of the other system, so calls are logged against the right agent. AI call data is the summary, topics, emotion, key points and action items NUACOM produces for a call.

Building your own integration#

1. Authenticate with an API key created by an account admin (see the Authentication guide). The key acts as its creator, so create it with a user that sees the calls and contacts you need.
2. Subscribe to events: POST /v2/webhook-subscriptions with a type and the url NUACOM should call. NUACOM then sends a JSON payload to that URL for every event of that type on the account; the event types and their payloads are described in the Webhooks guide. GET /v2/webhook-subscriptions lists them and DELETE /v2/webhook-subscriptions/{webhookSubscription} removes one.
3. Enrich on your side: a call event carries the call's call_id; use it with the Call Logs endpoints to fetch the row, the recording and the transcript, and with POST /v3/call-notes or POST /v2/add-call-tag to write back what your system knows.
4. Keep the phonebook in sync: push your records into NUACOM with the Contacts endpoints (create, update, bulk import) so inbound calls show your customers' names; the call_logs rows then carry the matched contact id.
5. Send messages: SMS and WhatsApp go through the Conversations groups: SMS with an approved sender name, WhatsApp with a sender connected in the portal and, outside the 24-hour reply window, an approved template.

Roles and access#

• Connecting or disconnecting a ready-made integration in the portal requires an account admin. Webhook subscriptions can be managed by any authenticated user of the account; they belong to the account, not to the user who registered them.
• Some integrations are enabled per account; the portal only shows those available to the account.

Pitfalls#

• A webhook delivery is sent once and never retried; make the receiving endpoint fast (answer 2xx first, process afterwards) and idempotent on the event's call_id.
• A call produces several events (initiated, answered or missed, updated) and several call-log legs sharing one call_id; de-duplicate on your side.
• The API key's creator must keep an active account membership, or every call with that key answers 401.