Imported workflow fails due to missing connection: how connection mapping works

Incorta
1

Problem

When a workflow is imported from another environment (e.g., Dev → Test, Test → Prod), it may fail to run because the connection is not mapped correctly.

This usually happens even when valid credentials exist in the target environment.

How connection mapping works in imported workflows

In imported workflows, connections are matched by connection name.

If the connection name used in the workflow does not exist in the target environment, the workflow will not be able to resolve the connection.

Solution

  1. Open the imported workflow JSON (or view the workflow configuration).

  2. Identify the connection name referenced in the workflow.

  3. In the target environment:

    • Either create a connection with the same name,

    • Or update the workflow JSON to use the existing connection name.

  4. Re-run the workflow to confirm the mapping works.

A user confirmed that editing the connection name in the JSON resolved the issue.

Best Practices

  • Keep connection names consistent across environments.

  • Maintain a standard naming convention for shared connections.

  • Validate connection mapping immediately after importing workflows.

Summary

If an imported workflow fails due to connection issues:

  • Check the connection name, not just the credentials.

  • Matching names across environments is the key to successful mapping.