Introduction
3 min
Connectors bring external data into Activate on a repeatable schedule, detect changes, and trigger the right workflows automatically. Each connector is a self-contained unit with its own schema, workflow, and change handlers, so you can run many connectors in parallel without overlap.
What Connectors do
- Import data from source systems into a staging (Import) table
- Compare staged data with current (Data) table to detect create / update / delete events
- Process each change using configurable handlers (e.g., Users, Roles, Generic, Script, Tickets)
- Act by submitting jobs, executing scripts, publishing/unpublishing, or sending notifications
Why use them
- Keep Activate aligned with HR, ERP, CMDB, or ticketing systems
- Drive lifecycle automation from real data changes
- Maintain a clear audit of imports and state changes
How a connector is structured
- Schema — Defines tables (dataTable, importTable, historyTable) and their columns, keys, and delete rules
- Workflow — Defines steps that load data, detect changes, and run handlers (clearImport, import, processImport, process, plus optional steps like execute, run, notify)
- Change & Link Handlers — Define how detected changes are acted upon or linked to existing Activate objects (e.g., AD users, roles, tickets)
Who this section is for
- Implementers & Administrators designing data flows and guardrails
- Developers extending import providers or event logic
- Operations teams monitoring connector runs and troubleshooting errors
Typical use cases
- HR feed → User provisioning: create, move, and disable users automatically
- Department hierarchy → Roles: keep organisational roles aligned with external structures
- Service desk integration → Ticket sync: update Activate tickets based on external statuses
Think of a connector as: **Data shape (Schema)** ➜ **Change detection (Workflow)** ➜ **Business action (Handlers)**.