Linking Telnyx as a source
Let AI connect your sources for you
Skip the manual setup — run this in your project and the wizard auto-detects your databases and APIs and connects them to PostHog.
This source is currently in alpha. The interface and available tables may change.
The Telnyx connector syncs your messaging, voice, verification, wireless, and media storage detail records into the PostHog Data warehouse, so you can analyze your communication data alongside your product data.
Prerequisites
You need a Telnyx account with API access so you can create an API v2 key.
Adding a data source
- In PostHog, go to the Sources tab of the data pipeline section.
- Click + New source and click Link next to this source.
- Enter your credentials (see Configuration below) and click Next.
- Select the tables you want to sync, choose a sync method and frequency, then click Import.
Once the syncs are complete, you can start querying this data in PostHog.
When linking Telnyx, you'll need:
- API key – create one under API Keys in the Telnyx portal.
Sync modes
Each table can be synced in one of several modes, depending on what the source supports:
- Webhook (when available) – the source pushes changes to PostHog in real time. Fastest freshness, lowest ongoing cost, and the only mode that reliably captures updates and deletes.
- Incremental – only new or updated rows are synced on each run, using a cursor field (such as an
updated_attimestamp). Cheaper than a full refresh, but deletes aren't captured. - Append only – new rows are appended using a cursor field; existing rows are never updated. Ideal for immutable, append-only tables like event logs.
- Full refresh – the whole table is reloaded on every sync. Use it when a table has no reliable cursor or when you need deletions reflected.
See sync methods for a full explanation of how each mode works and how to choose between them.
The messaging, verify, wireless, and media storage detail record tables support incremental syncs using the record's created_at timestamp. Conference, conference participant, and AMD detail record tables use full refresh since they don't have a documented server-side timestamp filter.
Configuration
| Option | Type | Required |
|---|---|---|
API key | password | Yes |
Supported tables
| Table | Description | Sync method | Incremental field | Primary key |
|---|---|---|---|---|
MessagingDetailRecords | Per-message detail records (MDRs) for SMS/MMS sent or received through Telnyx Messaging. | Incremental, Full refresh | created_at | — |
VerifyDetailRecords | Detail records for Telnyx Verify (2FA) verification attempts. | Incremental, Full refresh | created_at | — |
WirelessUsageDetailRecords | SIM card data usage events for Telnyx Wireless. | Incremental, Full refresh | created_at | — |
MediaStorageDetailRecords | Events for Telnyx Media Storage API actions (uploads, downloads, links). | Incremental, Full refresh | created_at | — |
ConferenceDetailRecords | Detail records for Telnyx Call Control conferences. | Full refresh | — | — |
ConferenceParticipantDetailRecords | Detail records for individual participants of a Telnyx Call Control conference. | Full refresh | — | — |
AmdDetailRecords | Detail records for Telnyx Answering Machine Detection (AMD) feature invocations. | Full refresh | — | — |
Troubleshooting
- If you get an authorization error (401), your Telnyx API key is invalid or has expired. Generate a new key from API Keys in the Telnyx portal, then reconnect.
- If you get a permission error (403), your API key doesn't have the required scopes. Check the key's permissions in the Telnyx portal, then reconnect.
If your sync is failing or data looks wrong, see the Data warehouse troubleshooting guide. If that doesn't help, contact support – we're happy to help.