Linking Mixmax 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 Mixmax connector syncs sequences, sequence folders, messages, and more into the PostHog data warehouse, so you can analyze them alongside your product data.
Prerequisites
Credentials that can read the data you want to sync. PostHog only reads data, so read access is enough.
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.
Enter your Mixmax API token to sync your Mixmax data.
Create an API token under Settings ▸ Integrations ▸ API in Mixmax. The token is scoped to the user that creates it, so it can only sync data that user can access.
API access requires a Growth+ or Enterprise plan with the API feature enabled on your workspace.
You'll be asked for:
- API token
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.
All Mixmax tables are full refresh. Each sync replaces the contents of the table.
Configuration
| Option | Type | Required |
|---|---|---|
API token | password | Yes |
Supported tables
| Table | Description | Sync method | Incremental field | Primary key |
|---|---|---|---|---|
sequences | Automated multi-step outreach sequences you have access to. | Full refresh | — | — |
sequence_folders | Folders used to organize sequences. | Full refresh | — | — |
messages | Tracked email messages sent through Mixmax. | Full refresh | — | — |
rules | Automation rules that trigger Mixmax actions. | Full refresh | — | — |
code_snippets | Reusable code snippets injected into emails. | Full refresh | — | — |
snippet_tags | Tags used to categorize snippets. | Full refresh | — | — |
meeting_types | Configured meeting/appointment types. | Full refresh | — | — |
insights_reports | Saved insights reports. | Full refresh | — | — |
polls | Polls embedded in Mixmax emails. | Full refresh | — | — |
file_requests | File requests sent through Mixmax. | Full refresh | — | — |
live_feed | Real-time email tracking events (opens, clicks, downloads). Full refresh only. | Full refresh | — | — |
appointment_links | The authenticated user's appointment (scheduling) links. | Full refresh | — | — |
users | The authenticated Mixmax user's profile. | Full refresh | — | — |
user_preferences | The authenticated user's Mixmax preferences. | Full refresh | — | — |
Troubleshooting
- If the connection fails with an authorization error, the API token is wrong, expired, or has been revoked. Create a new one, then reconnect the source.
- If a table syncs no rows, the credential may not have access to that data. Check its permissions, then reconnect the source.
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.