Trigger Historical Resync

fivetran.resync_connector
ActionBusiness appsconnection required

Calls the Fivetran API with the connection's credentials.

Start a full historical re-sync of a connector.

Connection

Required
Yes — the node will not save without one
Auth type
Username & password
Providers
Fivetran
Secret shape
{"api_key": "…", "api_secret": "…"}
Resolved by
config.connection_id, else node.connection_id

Configuration

1 field, 1 required. A dotted path is a nested object and name[] an array of objects — the editor renders the same tree.

FieldTypeRequiredDefaultConstraintsExample
connector_id
Fivetran connector id.
stringYes———

Output

One shape.

result

FieldTypeExample
status
string—
{
  "status": ""
}

Notes

  • A historical resync re-imports all data — can be slow and costly.

See Trigger Historical Resync run in a workflow.

In a technical demo we add the Fivetran connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.