Core Concepts
Systems
Connectors to PostgreSQL, MySQL, HTTP API, and Webhook.
Systems
What it is
A System is a configured connector: credentials, health, enablement, and execution behaviour for Rights jobs.
Why it exists
Deletion must touch real systems—not spreadsheets. Systems are the controlled outbound edge.
Types (v1)
| Type | Role |
|---|---|
| PostgreSQL | SQL delete via Data Map plans |
| MySQL | SQL delete via Data Map plans |
| HTTP API | HTTP call per case |
| Webhook | Signed outbound notify for delete |
v1 constraint: one connector per type per organization.
Secrets are encrypted at rest (AES-256-GCM). Lists do not return raw secrets (only hasSecrets / display hints). Rotate via dedicated rotate endpoints (Owner).
Health
| Status | Meaning |
|---|---|
| HEALTHY | Recent check succeeded |
| DEGRADED | Slow or partial issues |
| UNHEALTHY | Check failed |
| UNKNOWN | Not checked yet |
| DISABLED | Connector off |
Per-type summary (from connectors guide)
| Type | Config highlights |
|---|---|
| PostgreSQL | Connection string in secrets; tables on Data Map; parameterized DELETE |
| MySQL | Same model as Postgres with MySQL URL/dialect |
| HTTP API | baseUrl, pathTemplate ({{email}}, {{externalId}}), method; API key secrets |
| Webhook | Endpoint URL; signing secret; POST signed payload; no redirect following |
Production SQL TLS: Postgres ?sslmode=require (unless documented private-network insecure flag); MySQL ?ssl=true (or equivalent).
Related
- Data Maps
- Guides: Connect PostgreSQL, MySQL, HTTP, Webhook