Linking Motion 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 Motion connector syncs workspaces, users, projects, and tasks into the PostHog data warehouse, so you can analyze how work moves alongside your product data.
Prerequisites
A Motion account with API access. Only the account holder can create an API 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.
Create an API key in Motion under Settings, then API. Motion shows the key once, so copy it before closing the dialog.
You'll be asked for:
- API key: the key from your Motion settings.
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 Motion tables are full refresh. Motion's list endpoints have no server-side date filter, so each sync replaces the contents of the table.
Motion rate limits API keys, and individual accounts get a smaller allowance than teams. A first sync of a large workspace can take a while, and PostHog waits out the limit rather than failing the sync.
Configuration
| Option | Description |
|---|---|
API keyType: password Required: True | Create this in Motion under Settings, then API. |
Supported tables
| Table | Description | Sync method | Incremental field | Primary key |
|---|---|---|---|---|
workspaces | A Motion workspace, the container that holds a team's projects, tasks, and statuses. | Full refresh | — | — |
users | A person with access to one of the workspaces this API key can read. | Full refresh | — | — |
projects | A project in a Motion workspace, grouping related tasks. | Full refresh | — | — |
tasks | A task in a Motion workspace, including tasks Motion has auto-scheduled. | Full refresh | — | — |
Troubleshooting
- If the connection fails with an authorization error, the API key is wrong or has been revoked. Create a new one in Motion under Settings, then API, and reconnect the source.
- If a sync is slow, check whether other tools share the same Motion API key. The rate limit applies per key.
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.