MCP
A2APrerequisites
Before continuing, you should have already completed the following for this connector:Configure the Connector
Connector Profile
Link an Account
Link Account
How webhooks are set up
There is no manual webhook setup in Fivetran — it is fully automatic. On connection, StackOne calls Fivetran’s POST /v1/webhooks/account endpoint with your API key to create one account-level webhook covering every supported event, using a delivery URL unique to this connection that carries a secret token. As part of creation, Fivetran sends a one-time test_event validation POST to the URL and requires a 2xx response before it activates the webhook — StackOne answers this automatically. Fivetran then sends one HTTP POST per event, StackOne routes it to your integration, and only the events you have enabled are dispatched. Disconnecting the account deletes the webhook.
Review the available webhook events
Each delivery carries the firing event in the top-level event field, the affected connection in connector_id, and the timestamp in created. Only the events you enable in StackOne are dispatched.
Review sync events
Fired as a connection’s data sync runs.
- Sync Start (
sync_start) — Fired when a connection sync begins. - Sync End (
sync_end) — Fired when a connection sync completes (checkdata.statusforSUCCESSFUL/FAILED).
Review connection health events
Fired for connection setup-test results.
- Connection Successful (
connection_successful) — Fired when a connection’s setup test succeeds. - Connection Failure (
connection_failure) — Fired when a connection’s setup test fails.
Review connector lifecycle events
Fired as connections are created, edited, paused, and resynced.
- Create Connector (
create_connector) — Fired when a connection is created. - Edit Connector (
edit_connector) — Fired when a connection’s settings are edited. - Pause Connector (
pause_connector) — Fired when a connection is paused. - Resume Connector (
resume_connector) — Fired when a connection is resumed. - Delete Connector (
delete_connector) — Fired when a connection is deleted. - Force Update Connector (
force_update_connector) — Fired when a connection is force-updated (e.g. a manual sync via the API). - Resync Connector (
resync_connector) — Fired when a full connection re-sync is triggered. - Resync Table (
resync_table) — Fired when a single table re-sync is triggered.
Review transformation events
Fired as transformations (e.g. dbt) run.
- Transformation Start (
transformation_start) — Fired when a transformation run begins. - Transformation Succeeded (
transformation_succeeded) — Fired when a transformation run completes successfully. - Transformation Failed (
transformation_failed) — Fired when a transformation run fails.
Inspect the delivery format
Fivetran sends each event as an HTTP POST with a JSON body. Top-level fields are event (the firing event, e.g. sync_end), created (ISO 8601 event time), connector_type, connector_id, connector_name, sync_id, destination_group_id, and data (event-specific detail, e.g. data.status of SUCCESSFUL/FAILED). StackOne maps event to the event type, connector_id to the record id, and created to the event timestamp, and passes the full body through as the event data.
Understand delivery and retries
Your endpoint must return a 2xx status quickly. If a delivery fails (endpoint unavailable or a non-2xx response), Fivetran retries for up to 24 hours in increasing intervals, then stops for that event instance. Repeated failures can automatically deactivate the webhook. Design your integration to handle occasional duplicate deliveries idempotently.
Verify delivery authenticity
StackOne registers the webhook with a signing secret, so Fivetran signs each delivery with an X-Fivetran-Signature-256 header — an HMAC-SHA256 of the raw request body. StackOne authorizes each delivery using the secret token embedded in the per-connection webhook URL, so no extra configuration is required on your side.