Linking OPUSWatch 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.
Contents
This source is currently in alpha. The interface and available tables may change.
The OPUSWatch connector syncs client, locations, rows, 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.
Import master data, work registrations, and productivity sessions from OPUSWatch by OPUS Solutions.
You'll be asked for:
- API key: the API key for the OPUSWatch external API, issued by OPUS Solutions.
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 OPUSWatch tables are full refresh. Each sync replaces the contents of the table.
Configuration
| Option | Description |
|---|---|
API keyType: password Required: True | The API key for the OPUSWatch external API, issued by OPUS Solutions. |
Start dateType: text Required: False | Sync registrations and sessions created from this date, in YYYYMMDD format. Defaults to 20250101. |
Supported tables
| Table | Description | Sync method | Incremental field | Primary key |
|---|---|---|---|---|
client | The OPUSWatch client (company account) the API key belongs to. | Full refresh | — | — |
locations | Locations or areas within the greenhouse or nursery. | Full refresh | — | — |
rows | Physical rows or sections where plants are cultivated. | Full refresh | — | — |
users | People with access to the OPUSWatch system. | Full refresh | — | — |
workers | Workforce members registered in OPUSWatch. | Full refresh | — | — |
worker_groups | Groupings of workers. | Full refresh | — | — |
tasks | Tasks workers can register their work against. | Full refresh | — | — |
task_groups | Groupings of tasks. | Full refresh | — | — |
labels | Labels used to categorize workers, rows, and varieties. | Full refresh | — | — |
varieties | Plant varieties cultivated at the client's locations. | Full refresh | — | — |
registrations | Individual work registrations recorded by workers on their OPUSWatch. | Incremental, Full refresh | updatedTimestamp | — |
sessions | Work sessions with productivity metrics such as counts, performance, and labor cost. | Incremental, Full refresh | updatedTimestamp | — |
Troubleshooting
- If the connection fails with an authorization error, the API key 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.