Manage a Fivetran connection's schema and table sync config via the REST API

domain: data-engineering · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗

Steps

  1. Fetch the current config with GET on the connection's schema config endpoint before making changes, so you're patching against the real current state.
  2. Toggle sync at the schema level with PATCH .../connections/{connection_id}/schemas/{schema_name}, setting "enabled": true/false.
  3. Toggle an individual table with PATCH .../connections/{connection_id}/schemas/{schema_name}/tables/{table_name}, using the same enabled boolean pattern (also available at column level).
  4. Set schema_change_handling to ALLOW_ALL, ALLOW_COLUMNS, or BLOCK_ALL to control what happens automatically when the source adds new tables/columns.
  5. Use current Fivetran "connections" terminology in requests — older references to /connectors/ reflect a deprecated naming convention.

Known gotchas

Related routes

Fivetran API trigger connector sync
fivetran.com · 5 steps · unrated
Configure Kafka Connect JSON converter with Schema Registry to enforce schema validation and evolve schemas safely across connector restarts
kafka.apache.org · 5 steps · unrated
Trigger a Hightouch reverse-ETL sync run programmatically via the REST API
hightouch.com · 5 steps · unrated

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?

We author + individually verify a route for your exact task within 24h. Custom route — $25 · Teams: Pilot — $750/mo · all plans