Reference · built on requestConnectorStreams, queues & webhooks

Fivetran

Connection status, sync history, and sync_start and sync_end webhook events from Fivetran, with syncs and pauses through its REST API.

Request accessPricing ↗

About

Fivetran is a managed ELT service. It copies data from SaaS applications, databases, and files into a warehouse on a schedule. Each pipeline is a connection that belongs to a destination group. Fivetran's REST API at api.fivetran.com/v1 lists connections, reports their setup_state and sync_state, starts or pauses syncs, and registers webhooks that post sync_start, sync_end, and connection_failure events to a URL you name. The API is available on every Fivetran plan, including the free trial.

Through Fibric, an operator watches sync_end payloads and update_state for connections that have gone delayed, then proposes a sync, a resync, or a pause. You approve. The connector makes one request and leaves a receipt of what it changed.

This is a reference listing. It documents what Fibric would read from Fivetran and what it could propose, based on the vendor's published interfaces. Fibric builds it under a managed deployment when you request it; selecting it here installs nothing.

Inputs

  • Connections from GET /v1/connections with paused, sync_frequency, schedule_type, daily_sync_time, and the succeeded_at and failed_at timestamps
  • status.setup_state of incomplete, connected, or broken, and status.sync_state of scheduled, syncing, paused, or rescheduled
  • status.update_state of on_schedule or delayed, with the tasks and warnings lists on the status object
  • Webhook events sync_start, sync_end, connection_successful, connection_failure, pause_connector, resume_connector, and resync_connector, signed with HMAC SHA-256 when a secret is set
  • Transformation events transformation_start, transformation_succeeded, and transformation_failed
  • The current sync state of one connection from GET /v1/connections/{connectionId}/state

Proposed actions

  • Target capability: propose an incremental sync with POST /v1/connections/{connectionId}/sync
  • Target capability: propose a historical re-sync with POST /v1/connections/{connectionId}/resync
  • Target capability: propose pausing or resuming a connection, or changing its schedule, with PATCH /v1/connections/{connectionId}
  • Target capability: propose running setup tests with POST /v1/connections/{connectionId}/test after a source credential changes
  • Target capability: propose registering a webhook with POST /v1/webhooks/account or POST /v1/webhooks/group/{groupId}

Proposed actions are target capabilities. Every action runs propose-first and needs a validated deployment and the appropriate permissions.

What you can build

  • Catch a delayed pipeline before the morning numbers

    The operator reads update_state across connections and flags any that turn delayed, with the last succeeded_at. It proposes a sync and posts the receipt.

    With Data Freshness

  • Re-run a failed sync once the source is back

    A connection_failure webhook arrives. The operator waits for connection_successful, then proposes POST /sync so the warehouse catches up. You approve once.

    With Webhook Replay, Integration Health

  • Pause connections during a source migration

    Before a source cutover, the operator proposes PATCH with paused set to true on the affected connections, and the resume afterwards, leaving both changes on record.

    With Change Freeze, Integration Health

Requirements

  • A Fivetran account; its REST API is available on all plans, including the free trial
  • An API key generated from the API Key page under your username in the Fivetran dashboard, saved when it is shown
  • A Fivetran user role that covers the connections in scope, such as Manage Connection or Account Administrator
  • For webhooks, an HTTPS endpoint that answers Fivetran's post with a 2xx within 10 seconds
Authentication
HTTP Basic with a Fivetran API key and secret, base64-encoded as key:secret in the Authorization header; the secret is shown once when generated.

Limits

  • Requests are capped at 20,000 per rolling hour on non-trial accounts and 500 per hour on a trial. Excess calls get HTTP 429 with Retry-After
  • Source interaction requests are limited to 500 per minute and 5,000 per hour, and setup test requests to 250 per minute
  • Posts time out after 10 seconds. Fivetran retries at most five times over 24 hours, then deactivates a webhook after three days of non-2xx answers
  • Service account API keys, for access without a dashboard login, are in Private Preview

Access and pricing

Reference listing. Fibric builds the connector under a managed deployment when you request it. Your quote covers the build, capabilities, usage, and support.

Request Fivetran ↗

Questions and answers

Which events can a Fivetran webhook send?
sync_start, sync_end, connection_successful, connection_failure, create_connector, pause_connector, resume_connector, edit_connector, delete_connector, force_update_connector, resync_connector, resync_table, and the transformation_start, transformation_succeeded, and transformation_failed events. The status event is deprecated. A webhook is registered for the whole account or for one destination group.
How does Fivetran sign webhook payloads?
When you set a secret on the webhook, Fivetran computes an HMAC SHA-256 signature over the payload body. The secret is masked as ****** in API responses after creation. Payloads carry event, created, connector_id, connector_type, destination_group_id, sync_id, and a data object that varies by event.
What are the Fivetran REST API rate limits?
Limits apply per account over a rolling window. Non-trial accounts get 20,000 requests per hour, 500 source interaction requests per minute, and 250 setup test requests per minute. Trial accounts get 500 requests per hour. Over the limit, Fivetran returns HTTP 429 with X-Rate-Limit-Remaining and Retry-After headers.
Ask about Fivetran

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.

This connector listing is developed, published, and supported by Fibric. It describes integration with Fivetran through published interfaces. Third-party names and logos identify the systems an integration connects to; they are the property of their respective owners, who are not affiliated with Fibric and do not sponsor or endorse this listing. Trademark policy