domain: fivetran.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Generate a Fivetran API key and secret from the Fivetran dashboard under API Config; encode them as Base64 for use in HTTP Basic Auth.
Send POST https://api.fivetran.com/v1/connectors/{connector_id}/sync with header Authorization: Basic YOUR_ENCODED_CREDS and an empty or minimal JSON body.
The response includes a code field; CONNECTOR_SYNC_SCHEDULED (or similar success code) confirms the sync was triggered.
Poll GET https://api.fivetran.com/v1/connectors/{connector_id} and inspect data.status.sync_state until it transitions from syncing to scheduled or ready.
Check data.status.last_sync for the timestamp of the most recently completed sync and data.failed_tasks_count for any partial failures.
Known gotchas
Triggering a sync while one is already in progress returns a success response but the new sync is queued, not run concurrently; check sync_state before triggering.
The connector_id is the internal Fivetran identifier, not the connector name; retrieve it from the connector list endpoint or the Fivetran dashboard URL.
Fivetran enforces connector-specific sync frequency limits; manually triggered syncs that exceed the plan's allowed frequency may be silently throttled.
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?