Connections in workflows

Find dependent workflows and manage synchronization where it runs.

A connection supplies access; a workflow defines what to do with that access. Use Workflows from the connection detail page to find workflows that reference it. The filtered list helps you assess the impact of a credential change or removal and trace which automation reads or writes a resource.

Synchronization belongs to the workflow

To pull records from a connected source, use a workflow configured for connector synchronization. Run it on demand to refresh data, or configure its schedule in Workflows. The connection's edit dialog is for connection configuration; it is not a substitute for changing the referencing workflow's schedule.

A sync can create new records, update changed records, and leave unchanged records intact. Use the sync run's result and source activity to understand the outcome. A queued run means the request was accepted, not that all records are already available in Data.

Before changing a connection

Inspect both reading and writing workflows. A new credential may point to a different account, and a revoked credential can interrupt scheduled work. If the intent is to stop an automation temporarily, change the workflow's execution behavior rather than deleting the connection and its resources.

If no workflows appear, the connection can still be used in other contexts, such as direct browsing or Assistant tools. The list answers which workflows reference the connection; it is not a complete inventory of every human interaction with the provider.

After a credential update, test access and inspect a new run. Review its step-level error if it fails. Connection success, workflow success, and the presence of the expected output records are separate checks.

Continue with sync history, workflow guides, or record provenance.