Skip to main content
Use the @bijection/connectors/fivetran entrypoint to declare Fivetran resources.

Availability

This page describes the pinned source package. Published availability is unestablished for this artifact. Source build and package availability.

Resources and modes

Declare a resource in application code, then bind deployment-specific settings and credentials. See typed resources, connections and source inspection.

Connections

control: Sync lifecycle with signed webhook hints and sync trigger

The following example matches configuration standard.

Configuration: standard

Case: fivetran/connections/control/standard. Connection and resource configuration are declared by this exact case. Credential kind: fivetran. Keep credential material in the private credential inventory.
Native admission analysis is available for this exact declaration. Collection: records
Recorded checks Hosted qualification: unestablished for this catalog configuration. Installed connections report their own identity, authority and current status.

Configuration: controlled

Case: fivetran/connections/control/controlled. Connection and resource configuration are declared by this exact case. Credential kind: fivetran. Keep credential material in the private credential inventory.
Native admission analysis is available for this exact declaration. Collection: records
Commands
Recorded checks Hosted qualification: unestablished for this catalog configuration. Installed connections report their own identity, authority and current status.

Provider guidance

fivetran.connections.control({ webhooks?, sync? }) observes the connections of one Fivetran destination group, selected by the binding’s group setup; the connection’s discovery lists the account’s groups (GET /v1/groups). Fivetran runs every connector and owns its compute.
  • GET /v1/connections?group_id=… is walked with Fivetran’s stated next_cursor. Each record is id, service, schema, paused, setup_state, sync_state, succeeded_at and failed_at. A listing claims no coverage and no deletion; a removed connection stays published.
  • With webhooks: true, a Fivetran webhook signed with X-Fivetran-Signature-256 (HMAC-SHA256 of the raw body, hex) is a refresh hint for the connector_id it names: the engine reads GET /v1/connections/{id} again. The webhook’s payload is never published. Fivetran states no delivery id, so the event’s created instant names the delivery. A daily refresh-only sweep reads every published connection by id.
  • sync sends POST /v1/connections/{id}/sync with force: false. A 200 proves Fivetran accepted the request; it does not prove a sync started, ran or succeeded, and Fivetran may ignore it while a sync is running. Fivetran keeps no receipt, so a lost answer stays unknown.
A succeeded sync is visible as a new succeeded_at. Its destination data enters Bijection through the destination-snapshot importer in packages/iceberg, whose provider_run names the sync and its completion instant so the importer captures the destination snapshot committed by then. Bind a fivetran credential: HTTP Basic with the API key and secret, with allowed_resource_origins ["https://api.fivetran.com"]. The webhook endpoint is configured with the webhook secret as its signing credential.

Provider references

Provider references and prerequisites are maintained in the connector guidance above. No separate provider-documentation review date is recorded.

Source and evidence

Canonical connector source, native analysis and check receipts. Connector artifact: 905888ea276a2a28e36981a79e8142b2547ea451c3e63162cb6915ad4a7d1305. The resource declaration examples above are compiled and compared with exact catalog declarations. Recorded checks apply only to their source, declaration and runtime identities. Configure a connection and inspect its status to establish deployment-specific readiness.