Revoke stops Bizomate using a connection straight away and forgets its credential, but keeps it on the page so it can be reconnected. Delete removes it from the workspace for good. A working connection is revoked first; Delete appears once it is revoked, expired or needs reconnecting.

Who can do this

Workspace Admins and Editors. Viewers do not see the buttons.

Before you start

Open the connection's panel and look under Used by to see which workflows use it. Each workflow listed will fail at the steps that use it.

Steps

To revoke a connection:

  1. Select Connections in the bar at the top.
  2. Select the connection. Its panel opens on the right.
  3. Select Revoke. The window Revoke “Consulace Outlook”? says: "Bizomate stops using “Consulace Outlook” at once and forgets its credential. Workflows that use it fail until someone reconnects it. To withdraw the access on the service's side too, do that in the service itself."
  4. Select Revoke connection.

The toast "Connection revoked" says "Bizomate can no longer use “Consulace Outlook”." Its status reads Revoked, and the panel now shows Reconnect and Delete.

To delete it:

  1. Select the revoked (or expired, or needs reconnecting) connection.
  2. Select Delete. The window Delete “Consulace Outlook”? says: "“Consulace Outlook” is removed from this workspace. Workflow steps that used it need another connection chosen. This cannot be undone."
  3. Select Delete connection.

The toast "Connection deleted" says "“Consulace Outlook” is gone." It disappears from the list.

What happens next

  • After revoking: the workspace's other Admins and Editors get a notification — "Rohan Mehta revoked Consulace Outlook" — "Workflows in Consulace that use it fail until it is reconnected." Its credential is wiped at once, whatever kind it is: a sign-in's tokens, an API key, a password or connection string, a bot token or a connector's other fields. Steps that use it fail with "“Consulace Outlook” is revoked. Reconnect it on Connections."
  • After deleting: the connection and everything it held are removed. Its notifications clear. Steps that used it — in drafts and in the live version — still point at it, so they fail with "The step's connection no longer exists. Choose another in the designer." In the designer, choose another connection in the step's Connection list, then publish again.
  • On the service's side, neither removes Bizomate's access from the account. Withdraw it there too if you want:
    • Microsoft: remove it from My Apps (myapps.microsoft.com), or ask your IT admin.
    • Google: your Google Account's Security page, under third-party apps and services.
    • HubSpot: delete the private app in Settings › Integrations › Private apps.
    • A database: drop or change the password of the user Bizomate signed in as.
    • An API key: delete or rotate the key in the service's own settings.

Good to know

  • Revoking cannot be undone, but you can Reconnect the same connection afterwards and its workflows carry on. Reconnect asks for the credential again — an API key connection remembers how the key is sent, so it asks for the key alone.
  • Deleting cannot be undone. To use the service again, add a new connection and choose it in each step.
  • A connection variable that pointed at a deleted connection needs another connection chosen on Variables.

If something goes wrong

What you see Why What to do
No Delete button The connection is still active. Revoke it first, then Delete.
Runs fail with "The step's connection no longer exists. Choose another in the designer." The connection was deleted. Choose another connection in the step, then publish.
Runs fail with "No connection is chosen for this step." The step's Connection was cleared. Choose a connection in the step.