Automate and extend Gluesync
Most automation belongs on Chronos webhooks. They ship with every deployment, authenticate with a single token, log every run, and can wait for an action to finish. Reach for the Core Hub REST API only when your use case goes beyond what a webhook can express.
|
Start with webhooks. Use the REST API once you have tried webhooks and hit a real limit — typically provisioning, introspection, or generated configuration. |
Choose an integration path
| What you want to do | Use | Guide |
|---|---|---|
Fire an action, or an ordered chain of actions, from an external system |
Chronos webhook |
|
React to something that happened inside Gluesync, such as a snapshot completing |
Chronos platform event |
|
Run the same actions on a recurring schedule |
Chronos schedule |
|
Provision pipelines, attach agents, push credentials, or define entities from code |
Core Hub REST API |
|
Discover schemas, tables, and columns on a connected source |
Core Hub REST API |
|
Let an AI assistant read and operate your deployment conversationally |
Core Hub MCP server |
|
Build a module or a custom integration against the Core Hub |
SDKs |
Why webhooks first
A webhook-triggered event gives you, without writing any of it yourself:
-
Authentication scoped to one flow, rotatable, and verified in constant time
-
Execution logs per run, with the last error recorded on the flow
-
Ordered chains where sync steps wait on real Core Hub completion events
-
An off switch — disable a flow and every fire request is rejected while it is off
-
A UI your operators can use without a shell
The REST API has none of these. Its command endpoints answer 202 Accepted as soon as the instruction reaches the agents, not when the work finishes, so anything resembling "run this, then that" is yours to build.
Start at Build trigger flows, or use Schedules in the Control Plane.
When the REST API earns its keep
The REST API is the Control Plane’s own interface, so it reaches everything the UI reaches. That makes it the right tool for:
-
Provisioning pipelines, agents, credentials, and entity definitions as infrastructure-as-code
-
Introspection — reading a pipeline’s full configuration, or walking a source’s schemas and tables to generate entity definitions
-
Generated configuration that has no Control Plane form
-
Metrics collection from the per-pipeline Prometheus endpoint
See Core Hub REST API for the annotated endpoint reference, and OpenAPI explorer for the specification itself.
Other extension points
| Surface | What it is for |
|---|---|
Exposes Gluesync to AI assistants with the same authorization model as the Control Plane. |
|
Handle the Core Hub handshake, authentication, and protocol so you can build modules and integrations. |
|
Outbound notifications to your own endpoint when Gluesync raises an event or alert. |
|
One-off conversion of existing Syniti Replicate metadata into Gluesync configuration. |