Linking tinyEmail as a source
This source is currently in alpha. The interface and available tables may change.
The tinyEmail connector syncs your email marketing data – campaigns, contact lists, contact members, and sender details – into PostHog, so you can analyze campaign performance and audience growth alongside your product data.
Prerequisites
You need a tinyEmail account on an Enterprise plan, since tinyEmail restricts API access to Enterprise accounts. If you're on a lower tier, contact tinyEmail about upgrading before connecting.
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 tinyEmail, you'll need:
- API key – in tinyEmail, go to My account > API keys and generate a new key.
The tinyEmail API allows 60 requests per minute per API key. PostHog automatically backs off and retries when this limit is hit, but if you have very large contact lists you can ask tinyEmail support to raise the limit.
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 tinyEmail API doesn't offer a way to filter records by modification time, so all tables sync as full refresh.
Configuration
| Option | Type | Required |
|---|---|---|
API key | password | Yes |
Supported tables
| Table | Description | Sync method | Incremental field | Primary key |
|---|---|---|---|---|
campaigns | An email campaign, including its content, schedule, and delivery statistics. | Full refresh | — | — |
contacts | A contact list (audience) that campaigns can be sent to. | Full refresh | — | — |
contact_members | A subscriber within a contact list, with their profile fields and tags. | Full refresh | — | — |
sender_details | A sender profile (from name, email, and postal address) used to send campaigns. | Full refresh | — | — |
Troubleshooting
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.