Integrations
Three suite products write activity to CoreCNX by default. SendGrid handles email events. Signed webhooks fan everything else out to wherever you need. The REST API and OpenAPI spec cover the rest.
Native CNX Suite
If your account has Beacon, CampaignCNX+, or Alma turned on, every event those products produce lands on the CoreCNX timeline within seconds. No setup. No webhook configuration. No keys to copy between dashboards.
Beacon · Field ops
Every disposition logged on a canvasser's phone fires an event into CoreCNX the moment they tap "Contacted."
Wired by default · no setup
CampaignCNX+ · SMS
Broadcast and 1-on-1 SMS activity from CampaignCNX+ lands on the contact's timeline alongside everything else.
Wired by default · no setup
Alma · Website chatbot
Every conversation Alma runs on your website, and every lead it captures, writes to CoreCNX with full transcript context.
Wired by default · no setup
, Email infrastructure
Native email sending and event tracking, with every open / click / reply / bounce posted back to the contact timeline.
Email campaigns sent from CoreCNX go out through SendGrid. SendGrid's event
webhook posts back to corecnx.com/api/webhooks/sendgrid with a
verified signature. Each event resolves to the original send record, updates
the campaign metrics, and writes an activity row onto the contact's timeline
in the same format as a door knock or an SMS reply.
, Outbound
Subscribe to CoreCNX events and receive signed POSTs to any URL you control. Retry-safe: duplicates from retries don't double-fire on your end.
Create a webhook subscription in the dashboard, pick the event types you care
about, drop in a URL. CoreCNX POSTs JSON payloads to that URL whenever
a matching event happens. Each request includes an X-CoreCNX-Event
header and a signed signature so you can verify it really came
from us.
, Inbound
Full read/write access to contacts, pipelines, activity, lists, tags, segments, and reports. JSON in, JSON out. JWT-auth.
Every action you can take in the CoreCNX UI (creating contacts, moving them through pipeline stages, tagging, importing, exporting, querying activity) is available over a JSON REST API. Activity ingest accepts a unique
source_record_id per event, so the same event arriving twice still
lands on the timeline once.
Roadmap
We try to be honest about the difference. "Committed" = on the build sheet, dated. "Aspirational" = we want it but it isn't started.
Zapier Aspirational
Listed as a candidate. The webhook + REST API combo covers most use cases people would reach for Zapier for, so it isn't urgent. Will revisit when there's clear customer pull.
Stripe billing webhooks Aspirational
Useful for B2B accounts that want subscription churn / upgrade events on the timeline next to email opens. Not on the build sheet yet.
CRM exports (HubSpot, Salesforce) Aspirational
One-way sync of CoreCNX contacts to a destination CRM. The opposite (pulling contacts into CoreCNX) is already covered by CSV import.
Public docs site Committed
OpenAPI spec rendered as browsable docs at a public URL with copy-pasteable curl examples. URL TBD
Slack notifications Aspirational
Push pipeline-stage changes or threshold alerts into a Slack channel. Today this is doable via the webhook → Slack-incoming bridge, just not native.
Voter-file enrichment Committed
Match a CoreCNX contact to L2 / state voter file data. Already wired through the enrichment service for political accounts.
Test it
Sign up, copy the activity-ingest curl, fire a test event from your terminal. Watch it land on the timeline in seconds.