Disconnect apps

Remove a Nock app connection, distinguish it from pausing access, and recover from incomplete connection changes.

Launch preview Build and service availability vary. Check availability →

Disconnect a service when you no longer want its account connected to Nock. If you only want to pause the agent temporarily, use Agent access instead; that keeps the connection for later.

Before disconnecting

Review any task currently using the service. If a request may already have reached the provider, disconnecting cannot reverse it. Check messages, records, or other affected data in the destination before retrying or starting a replacement task.

Confirm which provider account is connected. A personal account and a company account can have similar names. If the connection details are unclear, verify them with the provider before removing access.

Remove the connection

Open Settings → Apps.
Find the service marked Connected in the App Store.
Use its connected switch or open the detail sheet and choose the disconnect control.
Wait for the list to refresh and confirm that the service is no longer shown as connected.

The desktop refreshes the agent’s app session after connection changes, so the new state applies to subsequent requests. If the list does not update, reopen the Apps view and inspect the error rather than assuming the request succeeded.

Provider-side authorization

You can also review the provider’s own connected-app or security settings. Revoking there is useful when the Nock interface is unavailable or you want to confirm which permissions the integration holds. Provider interfaces differ; follow that service’s instructions.

Disconnecting does not delete your provider account, erase messages created earlier, or reverse changes made by a tool. It is also separate from deleting a locally built preview in My Apps. A saved preview and a service connection are different objects.

Reconnect later

Find the service in Available and choose Connect. Complete authorization in the browser and return to Nock to confirm the status. The desktop checks the pending sign-in for a limited period; if it expires, begin a fresh connection instead of continuing to refresh an old authorization tab.

Only one app sign-in runs at a time in the interface. Finish or leave the current flow before starting another. If the service requires a developer-app setup that is unavailable for your account, the setup message is an availability limit, not a password failure.

If access still seems possible

Check whether the action actually used the disconnected integration, a separate connected account, or a browser session. Disconnecting one route does not sign you out of unrelated apps or websites. Review the route used and pause the task before changing additional settings.

Hosted app-tool execution remains unavailable publicly during launch preparation. See Availability and Support if the shown state conflicts with a task result.