Integrations

CoreCNX integrations: native CNX Suite, webhooks, REST API.

Three suite products send activity to CoreCNX automatically, and SendGrid reports email events. Signed webhooks (automatic messages with a signature proving they are genuine) pass events to your other tools. For everything else, there is a REST API (a standard way for other software to read and write your data), described in a published OpenAPI specification.

Built-in CNX Suite connections

Connected for you when you buy the suite, with one bill and one contact record.

When you buy Beacon, CampaignCNX+ or Alma as part of the suite through CoreCNX, each one is connected to your CoreCNX account for you, and the events it sends appear on the CoreCNX timeline. There are no webhooks to configure and no access keys to copy. If you already have an account with one of them, contact us and we will connect it.

Beacon · Field work

Door knocks & field activity

Each door-knock result is saved on the canvasser's phone and sent to CoreCNX when the phone syncs, usually within a few minutes. The timeline keeps the time of the knock itself.

  • Door knocked, answered, not home or refused
  • Literature dropped
  • Appointments booked in the field

Connected for you when bought with the suite

CampaignCNX+ · Texting (SMS)

Texts sent, replies & opt-outs

Mass texts and one-to-one conversations from CampaignCNX+ appear on the contact's timeline.

  • Text sent, delivered or failed
  • Replies & two-way conversations
  • Opt-outs and opt-ins (requests to stop texts, or to receive them again)
  • Enrollment & each step in a drip sequence (texts sent on a schedule)
  • Keyword texts received & automatic responses

How texts reach the CoreCNX timeline

Connected for you when bought with the suite

Alma · Website chatbot

Chatbot conversations & leads

Alma sends CoreCNX each lead it captures, and each finished conversation with a visitor who has given an email address or phone number.

  • Chatbot conversation completed
  • Lead captured
  • Appointments booked through the chat window
  • Broadcast messages sent to subscribers

Connected for you when bought with the suite

Email delivery

SendGrid

Built-in email sending and tracking. Every open, click, bounce and unsubscribe is added to the contact's timeline.

Campaigns sent from CoreCNX go out through SendGrid, which sends a signed webhook to corecnx.com/api/webhooks/sendgrid for each email event. CoreCNX links the event to its email, updates the campaign results and adds it to the contact's timeline.

  • Delivered, opened, clicked, bounced, unsubscribed
  • Results for each campaign & engagement history for each contact
  • Unsubscribes marked on the contact record; bounces shown on the timeline

Outgoing

Webhooks

Choose the events you want, and CoreCNX sends a signed message to any web address you control each time one happens. Each delivery carries an activity_id, so your system can recognize a repeat and ignore it.

Create a webhook subscription in the dashboard, choose event types and enter a web address. CoreCNX sends each matching event there in JSON, a standard data format, with an X-CoreCNX-Event header naming the event and a signature so you can confirm it came from us.

# Payload posted to your endpoint POST https://your-app.com/hooks/corecnx X-CoreCNX-Event: stage_changed X-CoreCNX-Signature: <HMAC-SHA256 of the raw body, as hex, keyed with your subscription secret> { "contact_id": "8a4f...", "account_id": "3c91...", "source_product": "corecnx", "summary": "Maria Santos moved from 'Contacted' to 'Soft Support'", "data": { "old_stage": "Contacted", "new_stage": "Soft Support", "old_stage_id": "51d0...", "new_stage_id": "9e72..." }, "occurred_at": "2026-04-22T14:31:08+00:00", "activity_id": "b7e3..." }
  • Pipeline stage changed (stage_changed, a contact moved to a new stage on your board) · contact created (contact_created) · contacts merged (contact_merged)
  • Activity logged · note added (note) · tag added or removed (tag_added, tag_removed)
  • Each delivery recorded with its response code
  • Every message is signed. Check the signature before you act on it.
  • Failed deliveries are retried automatically. A subscription pauses after repeated failures.

Incoming

REST API

List your contacts, read one contact or add a new contact from your own software. Data is sent as JSON, and each request is authorized with an API key (a secret code that identifies your account).

The public API covers contacts: you can list them, read one, or add one. Contacts added through the API count toward your plan's contact limit, the same as contacts added on screen. Moving contacts between stages, tagging, importing and exporting are done in the app.

  • OpenAPI 3 specification, generated from the live server Public link TBD
  • API keys, sent as Authorization: Bearer cnx_... · API access for each account on the Growth plan and above
  • Contacts export as CSV or XLSX in the app, and as JSON through the API
  • Bulk import in two steps: preview the data, then confirm it
  • Each key records when it was last used, and can be revoked or set to expire
# Add a contact from your own system POST https://corecnx.com/api/v1/contacts Authorization: Bearer cnx_<your API key> { "first_name": "Maria", "last_name": "Santos", "phone": "+15551234567", "email": "maria@example.com" }

Roadmap

Planned integrations, and how firm each plan is.

"Committed" means it is on our build schedule with a date. "Aspirational" means we would like to build it, but work has not started.

Zapier Aspirational

Zapier (a service that connects apps without code) is under consideration. Webhooks and the REST API already cover most reasons people use it, so we will revisit it when customers clearly ask for it.

Stripe billing webhooks Aspirational

This would show subscription cancellations and upgrades from Stripe, the payment service, on the timeline next to email opens, for business (B2B) accounts. It is not on the build schedule yet.

CRM exports (HubSpot, Salesforce) Aspirational

This would copy CoreCNX contacts one way into another CRM (a shared contact database). Importing from those systems already works through CSV import.

Public docs site Committed

The OpenAPI specification, published as browsable documentation at a public web address, with curl command examples you can copy and paste. URL TBD

Slack notifications Aspirational

This would post stage changes or alerts to a Slack channel. You can do this today by connecting a CoreCNX webhook to a Slack incoming webhook, but it is not built in.

Voter-file enrichment Aspirational

This would match a CoreCNX contact to voter file data automatically. It is not built yet. Today, you bring voter file data into CoreCNX with a CSV import, and the enrichment service can fill in missing phone numbers, email addresses and demographic details.

Test it

Receive your first webhook today.

Sign up, add a webhook subscription in your settings, and move a contact to a new pipeline stage. CoreCNX sends a signed message about the stage change to the web address you chose.

API access
Growth plan and above
Webhooks
Every paid plan
OpenAPI
Public specification, browsable documentation