Updating and Removing Connections

How to update credentials or remove connections.

Overview

Workflows reference connections by ID, so updating a connection's credentials or settings is the standard way to rotate keys, change service URLs, or fix a misconfiguration without rebuilding anything downstream. Removing a connection, by contrast, breaks every workflow that references it - so it pays to check usage first.

Both operations live on the connection's detail page under Connections. Updates take effect on the next workflow execution; removals are immediate.

Before You Start

For credential updates: the new key, token, or OAuth account you intend to use.
For removals: a quick review of which workflows currently use the connection so you know what will break.

Updating a Connection

Go to Connections and click the connection you want to update.
Edit the fields you need to change: Name, Credentials, Service URL, or Visibility.
For OAuth connections, click Reconnect to re-authorize against the upstream service. The connection ID stays the same.
Click Save. Spojit re-verifies the credential and updates the status to Active on success.
The new settings apply to every subsequent workflow execution. In-flight runs continue with the credential they already loaded.

Removing a Connection

Go to Connections and click the connection.
Check the Usage view to see which workflows reference this connection.
Either repoint those workflows to a different connection or disable them before continuing.
Click Remove and confirm. Spojit deletes the connection and its stored credentials.

What Updates Are Safe

Name - Safe to change at any time. Workflows resolve by ID, not by name.
Credentials - Safe to rotate in place. The next execution picks up the new credential automatically.
Service URL - Safe for the same instance (e.g. domain change). Repointing to a different upstream account or environment is effectively a different connection - prefer creating a new one.
Visibility - Safe to widen (private to shared). Narrowing (shared to private) hides the connection from teammates whose workflows may depend on it.

Tips

Rotate keys without rebuilding workflows: edit the connection, paste the new credential, save. Done.
Before removing, repoint any workflows that use the connection to an alternative, or pause them, so you do not get a wave of failed runs.
If you need a clean break (e.g. moving from a personal to a service account), create a new connection alongside the old one, switch workflows over one at a time, then remove the old one.

Common Pitfalls

Removing a connection still in use - Every workflow that references it will fail on the next run. Check usage before confirming.
Repointing the service URL across environments - Reusing one connection for staging then production hides which environment a run hit. Create separate connections instead.
Reconnecting OAuth as a different user - The consent screen may default to a different account; the connection then acts on behalf of whoever you authorized as.
Forgetting in-flight runs - Updates apply on the next execution. A long-running workflow already mid-flight uses the credential it loaded at start.