- Documentation
- Client portal
- Check and reconnect your connections
Check and reconnect your connections
View connection health and refresh, update, reconnect, or revoke an app from your client portal at /portal/connections.
Goal
When you connect an app for an agency, that connection stays in your portal so you can check its health and act on it later. The agency runs workflows on the credential you granted, so if it stops working those workflows pause until you reconnect.
This page covers everything you can do from Connections (/portal/connections): read each connection's status, refresh an expired credential, update an API key, password or database credential you shared, and revoke access.
When to use this
Use Connections when:
- A workflow has stopped and your agency tells you a connection needs attention.
- You want to confirm an app you authorized is still working.
- You are leaving a project and want to revoke access to an app.
If you still have an outstanding request to connect a new app, that lives in the Outstanding connection requests panel on the same page. See Connect an app for your agency for that flow.
Read the connections list
Sign into your portal and open Connections. The table lists every app you have connected for the current workspace, with four columns:
| Column | What it shows |
|---|---|
| App | The app you connected, such as Slack or HubSpot. |
| Label | The name on the connection. |
| Status | The connection's current health (see the table below). |
| Actions | A Manage link to the connection's detail page. |
Only connections you authorized appear here. Connections the agency set up under its own account do not show in your portal.
If you have not connected anything yet, you see No connections yet with the note "When your team asks you to connect an app, it will show up here."
Status values
The Status badge is one of four values. These describe the health of the credential, not the request that asked you for it.
| Status | What it means | What to do |
|---|---|---|
| active | Connected and working. | Nothing. |
| error | Reconnection needed. | Refresh the credential (OAuth), enter a new value, or revoke and reconnect. |
| pending | Waiting for the first sync. | Wait. The connection finishes setting up on its own. |
| revoked | This connection was revoked. Reconnect to keep workflows running. | Reconnect from a request email if your agency sends a fresh one. |
There is no separate "needs reauthorization" status. When a credential expires or is rejected by the provider, the status moves to error with the description "Reconnection needed."
Open a connection
Click Manage on any row to open /portal/connections/{connectionId}. The detail page shows the app name, the label, the status badge with its description, and, when available, the external account email and a Last refreshed timestamp.
From here you can Refresh credential (OAuth apps), enter a new value for an API key, password or database credential you shared, and Revoke.
Refresh a credential
Refreshing renews the access token without making you sign in again at the provider. Use it first when a connection shows error.
Open the connection detail page
From Connections, click Manage on the app you want to fix.
Click Refresh credential
The button sits next to the status. On success you see the toast Connection refreshed. and the page reloads with the updated status.
Confirm the status returned to active
If the badge reads active, the connection is working again and dependent workflows resume.
The Refresh credential button only appears when the connection can be refreshed (an OAuth app that still holds a stored token). If you do not see it, the detail page shows the line "Contact your agency if this integration needs to be reconnected." instead. In that case, ask your agency to send a fresh connection request.
If the refresh fails, you see Failed to refresh connection with "You may need to reconnect." A refresh cannot recover a credential the provider has fully revoked. When that happens, ask your agency to send a new request email so you can authorize the app again through the provider's consent screen.
Update an API key, password or database credential
When you shared an API key, a username and password, or a database connection with your agency, you can replace its value yourself while the connection is not revoked. You do not need a new request from the agency. The connection keeps its place in every workflow that uses it.
Open the connection detail page
From Connections, click Manage on the credential you want to change. The page reads "Enter a new value below to update this credential, or revoke it."
Enter the new value
Fill in the fields under the heading that names the app, such as Update your Typesense credential. They are the same fields your agency's request asked for.
Click Update credential
An API key or password is checked with the provider before it is saved. If the provider rejects it, you see an error under the form and nothing is changed. On success you see Credential updated and the status returns to active.
If your agency sent you a request for the same app, updating the value here also completes that request, so it leaves your inbox. Answering the request from its email link or your inbox instead updates this same connection; it does not create a second one.
Revoke a connection
Revoking cuts the agency's access to the app. Do this when you no longer want the connection used, for example when you finish a project.
Open the connection detail page
Click Manage on the connection, then find the Revoke button next to the status.
Confirm in the dialog
A dialog titled Revoke this connection? explains the impact: "Workflows that depend on this credential will pause until you (or another team member) reconnect it. You can reconnect at any time from this page or from a future request email." Click Revoke connection to proceed, or Keep connection to back out.
Note the result
On success you see Connection revoked with "Workflows using this connection will pause until reconnected." The status badge changes to revoked.
Revoking is not just removing a row. Any workflow the agency runs on this credential pauses immediately and stays paused until the connection is reconnected. Revoke only when you intend to stop the agency's access.
The Revoke button is hidden once a connection is already revoked, so you cannot revoke twice.
Verify it worked
- After a refresh, the status badge reads active and Last refreshed shows the current time.
- After an update, you see Credential updated and the status badge reads active.
- After a revoke, the status badge reads revoked and the Revoke button is gone.
- Back on the Connections list, the Status column reflects the same value.
Troubleshooting
The Refresh credential button is missing. It shows only for OAuth connections that hold a stored token. For an API key, password or database credential, enter a new value instead (see Update an API key, password or database credential). For an OAuth connection, the page tells you to contact your agency. Ask them to send a fresh connection request so you can reconnect through the provider.
Refresh says "You may need to reconnect." The provider rejected the stored token and a refresh cannot recover it. Reconnect by authorizing the app again from a new request email, not from this page.
I want to revoke but the button is gone. The connection is already revoked. Its status badge reads revoked, and there is nothing left to revoke.
A connection I expected is not listed. Only connections you authorized for the current workspace appear. Connections the agency owns under its own account, and connections in another workspace, do not show here.
I cannot cancel an outstanding request. Only your agency can cancel a request that asked you to connect an app. From your side you can connect the app, or later refresh or revoke the resulting connection.