Disconnected integrations wait for one Reconnect

When a service stops honoring a connection, because someone revoked access, the workspace's OAuth app changed, or the service stopped accepting an API key, the integration now stays where it is, marked disconnected. Every workflow, trigger, and app wired to it waits instead of failing or turning off. Its owner hears about it once, and a single Reconnect, on the web or in the iPhone app, brings all of them back: sign in again, or enter a key the service accepts. Browse the integrations you can connect.

How it works

• Waiting, not failing. A run that needs a disconnected account is skipped and a polling trigger pauses; neither counts toward turning a workflow off or sends a failure notice. A workflow or app that marks the account optional runs without it.
• Same account, same access. Reconnect lands on the account you had, with at least the permissions it had before. Signing in to a different account is refused, so add that one as a new connection.
• Keys checked, not guessed. When something using an API key fails, the service's own check runs. Only a key it refuses twice, minutes apart, is disconnected, so a brief hiccup never takes one offline.
• Access found early. General Input Vault now checks any connection unused for a week, keeping sign-ins alive where services expire idle access and spotting a revoked one before a workflow needs it.

Also shipped

• The disconnect notice opens the account, and reconnecting or deleting it clears the notice on every device.
• A disconnected account shows as broken, with only Reconnect and Delete, and its integration reads "Needs reconnecting".
• Connection checks no longer keep copies of what they read from your services.