Workflow run failed: trigger is linked to a CRM connection that no longer exists

Updated

Applies to: Workflows triggered by HubSpot or Salesforce

A workflow run failed with this message:

This workflow's trigger is linked to a CRM connection that is disconnected or no longer exists. If your CRM was disconnected, reconnect it. Otherwise open the workflow, re-link the trigger to your current connection, and publish it.

The fix is to point the trigger at a working connection and publish the workflow again.

Why it happens

The workflow's trigger is linked to a HubSpot or Salesforce connection that was disconnected or deleted. OnRamp can't find that connection for your organization anymore. Runs fail with this message when they reach the step that links the account to its CRM record, and the run is recorded with an error status.

In the workflow builder, the trigger step on the canvas is marked as invalid. The trigger panel shows this warning: This trigger is linked to a HubSpot connection that no longer exists, so the workflow can't run. For a Salesforce trigger, the warning names Salesforce instead.

Fix it

  1. If your CRM was disconnected, reconnect it first. Go to Settings > Integrations+ and connect HubSpot or Salesforce again.

  2. Open the workflow and select the trigger step on the canvas.

  3. Select Edit from v followed by the version number, such as Edit from v3, to start editing.

  4. In the trigger panel, make sure your current connection for the same CRM is selected.

  5. Select Re-link to current HubSpot connection or Re-link to current Salesforce connection. The button only appears while you're editing and a current connection for the same CRM is selected. The warning clears right away.

  6. Select Save.

  7. Select Publish.

Until the trigger is re-linked, the workflow counts as invalid and Publish stays unavailable. Publish also needs your changes to be saved first.

If the panel says Connect HubSpot in Integrations, then re-link this trigger. (or Salesforce), there's no current connection for that CRM yet. Connect it under Settings > Integrations+, then come back and repeat steps 2 to 7.

Still stuck?

Contact support with the workflow name, the version you published, the time of the failed run, and which CRM the trigger uses.

More in Troubleshooting