Skip to main content
Support tickets and recorded conversations carry some of the strongest churn and expansion evidence — escalations, commitments, sentiment, competitor mentions. Each source connects differently.

​
Pylon — support tickets

Paste the token in Integrations → Pylon, then finish the webhook step if prompted — without it, tickets don’t arrive in real time.

​
Gong — call recordings

OAuth from Integrations → Gong, then complete the webhook step shown in the connection detail.

​
Fireflies — meeting notes

Paste the key in Integrations → Fireflies. No mapping step.

​
Granola — meeting notes

Personal Granola keys connect per person (like Gmail). If your team uses Granola Enterprise, one admin connection covers the workspace.

​
Google Calendar

Covered alongside Gmail — see Gmail and Google Calendar.

​
Troubleshooting

For Gong and Pylon, check the webhook step — OAuth/token connect and webhook delivery are separate, and both show their state on the connection detail. For Granola personal keys, the teammate who took the notes must connect their own key.
Pylon’s webhook may have lapsed — the connection detail shows webhook health. Re-saving the token doesn’t restore webhooks; finish the webhook step.
Meeting evidence attaches by participant/domain matching. If participants aren’t recognized contacts yet, confirm the customer’s domain and contacts are set — see Customers.