Linking Spotler CRM as a source
This source is currently in alpha. The interface and available tables may change.
The Spotler CRM (formerly Really Simple Systems) connector syncs your CRM data – accounts, contacts, opportunities, activities, and more – into PostHog, so you can analyze your sales pipeline alongside your product data.
Prerequisites
You need a Spotler CRM account on a plan with API access (Professional or Enterprise). Some record types need paid add-ons: campaigns require the Marketing tool, and cases require the Service & Support tool.
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 Spotler CRM, you'll need:
- API access token – in Spotler CRM, go to Settings, then Integrations, then API V4, and click Generate new key. The token is shown only once, so copy it right away.
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 Spotler CRM API doesn't support server-side incremental filtering, so all tables sync as a full refresh.
Configuration
| Option | Type | Required |
|---|---|---|
API access token | password | Yes |
Supported tables
| Table | Description | Sync method | Incremental field | Primary key |
|---|---|---|---|---|
Accounts | Companies and organizations stored in the CRM. | Full refresh | — | — |
Activities | Tasks, calls, meetings, and other activities logged against records. | Full refresh | — | — |
Campaigns | Marketing campaigns. Requires the Spotler CRM Marketing tool add-on. | Full refresh | — | — |
Cases | Customer service cases. Requires the Spotler CRM Service & Support tool add-on. | Full refresh | — | — |
Contacts | People linked to accounts. | Full refresh | — | — |
Documents | Documents attached to CRM records. | Full refresh | — | — |
Opportunities | Sales opportunities in the pipeline. | Full refresh | — | — |
OpportunityHistories | Historical stage and forecast changes for opportunities. | Full refresh | — | — |
OpportunityLines | Line items attached to opportunities. | Full refresh | — | — |
Troubleshooting
If a table fails to sync with a permission error, check that your plan includes that record type: campaigns need the Marketing tool add-on, and cases need the Service & Support tool add-on.
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.