Connections and sample data

Bind jobs to saved connections and develop transformations with predictable inputs.

Connection-backed steps use saved connection settings to read or write data. A connection can represent a database, application service, file store, or another supported provider. The available operations depend on that provider's capabilities.

Bind a connection

1. Select the source or destination job.
2. Choose the required connection in its configuration.
3. Confirm the provider and supported operation.
4. Select the stream, table, path, or resource required by the handler.
5. Review provider-specific configuration and validate.
6. Run a small example and confirm both the records and their destination.

Choosing a provider name is not always enough. A step that needs an authenticated saved connection must have a valid reference and appropriate access. Managed connections keep credentials in their connection settings; avoid pasting secrets into prompts, test records, or ordinary configuration text.

A connection created while configuring a job can be returned to that job. Confirm that the intended step received it when several jobs are open.

Use sample inputs

Test Data provides a predictable source for designing the graph. A sample connection can expose automatic or manually supplied sample settings. Use manual records to cover empty values, unusual characters, and alternative record shapes.

Edits to a sample connection's settings can save automatically and affect other workflows using that same connection. Wait for its save confirmation. A workflow's saved indicator does not prove a separate connection edit succeeded.

Replace a source safely

When switching connections, recheck its resource names, selected files, stream, and output shape. Similar providers do not guarantee identical record fields. Revalidate downstream JSONPaths and mappings.

Before changing a shared connection, open its workflows view to understand the affected processes. Replacing credentials may repair authentication without changing workflow logic; replacing the source often requires a new full run or reviewed baseline.

See connections, run modes, and apps and connection sync.