Workforce data in Redshift, beside everything else you model.
Warehouse export into Redshift for stacks that already live there. In beta: the adapter ships, the connect path is landing.
Connected once, scoped per organisation
A connection belongs to your organisation and nothing else. Tenant isolation is enforced by composite foreign keys in the database, so a cross-tenant read is an error rather than a code-review question.
Incremental, cursor-tracked syncs
Syncs resume from where the last one stopped rather than replaying from the beginning, and every run is recorded with its outcome, so a failed sync is visible instead of silent.
Scoped credentials, revocable
Access is held as a scoped credential you can rotate or revoke, and every use of it lands on the same hash-chained audit trail as the rest of the account.
How it works
Warehouse export into Redshift for stacks that already live there. In beta: the adapter ships, the connect path is landing. The connection is scoped to your organisation, holds a credential you can rotate or revoke, and records every sync with its outcome, so a run that fails is visible rather than silent.
The Amazon Redshift connector is implemented and covered by tests, but the self-serve connect path is still landing. Today it is enabled with help from us rather than from Settings. It is listed as beta for exactly that reason: shipped in the sense that matters to our codebase is not shipped in the sense that matters to you.
Amazon Redshift connects to WorkMonitor through a first-party connector maintained in this codebase. Warehouse export into Redshift for stacks that already live there. In beta: the adapter ships, the connect path is landing.
Four steps, once
- 01Open Settings → Integrations and choose the connector.
- 02Authorise the connection and pick the scope it may read.
- 03Run the first sync, then review what it brought across.
- 04Set the schedule, and watch the sync history for failures.
What you get either way
Connected once, scoped per organisation
A connection belongs to your organisation and nothing else. Tenant isolation is enforced by composite foreign keys in the database, so a cross-tenant read is an error rather than a code-review question.
Incremental, cursor-tracked syncs
Syncs resume from where the last one stopped rather than replaying from the beginning, and every run is recorded with its outcome, so a failed sync is visible instead of silent.
Scoped credentials, revocable
Access is held as a scoped credential you can rotate or revoke, and every use of it lands on the same hash-chained audit trail as the rest of the account.