Connect Pylon to your
customer knowledge graph
Overview
For B2B teams that run support in Pylon, some of the sharpest early signals of churn and expansion live in those threads — a bug that keeps resurfacing, a feature ask from an economic buyer, a conversation that’s gone quiet. Connect Pylon and those support interactions become part of the same customer knowledge graph that powers your health scores, enrichments, and chat.
What syncs
Add your Pylon API key and Sonora brings in:
- Issues — support tickets and their status, mapped to the right account.
- Issue messages — the full conversation threads, not just the latest reply, tied to the contact who wrote them.
- Feature requests — asks captured in Pylon, linked to the account so you can see who wants what.
Syncing is read-only: Sonora imports from Pylon and doesn’t modify anything in it. You choose whether to bring in issue messages and feature requests, and set the sync schedule.
What Sonora does with it
Every synced Pylon issue is scored and connected like any other source:
- eCSAT and sentiment read from the support thread, factored into the same health score as email, calls, and product usage — with the reasoning attached.
- Issues and feature requests surface on the account and roll up across your book, so you can ask “which customers keep hitting the SSO bug?” in chat or Canvas and get an answer grounded in the actual Pylon threads.
- Stakeholders from the conversation populate your People graph, with engagement tracked per contact.
On a customer’s profile, Pylon sits alongside Salesforce, Slack, email, and calls — one timeline, one health read.
Get started
Head to Settings → Data Sources → Pylon, paste your Pylon API key, and run the connection test. Choose whether to import issue messages and feature requests, set a sync schedule, and the first import kicks off. Full setup is in the Pylon integration docs.


