Test asks the service whether it still accepts the connection, without running a workflow. Refresh renews a sign-in's access straight away. Use them when a step fails and you want to know whether the connection is the cause.
Who can do this
Workspace Admins and Editors. Viewers do not see the buttons.
Before you start
Test is offered for the connections that have something to test against: Microsoft 365, Google Workspace, HubSpot, PostgreSQL and Microsoft SQL. An AI key or an API key for HTTP Request has no Test — running a step that uses it is the test.
Refresh is offered for connections you signed in to (Microsoft 365, Google Workspace), not for keys or tokens.
Steps
- Select Connections in the bar at the top.
- Select the connection. Its panel opens on the right.
- Select Test. It shows Testing while Bizomate asks the service.
- Read the toast:
- "“Consulace Outlook” works", with who it signed in as — "Connected as Rohan Mehta (rohan@consulace.com)". A database says "Signed in to PostgreSQL." A HubSpot token says "HubSpot accepted the private app token."
- "“Consulace Outlook” did not answer", with the service's reason.
- For a sign-in, to renew its access now, select Refresh. It shows Renewing, then:
- "Access renewed" — "“Consulace Outlook” has a fresh token."
- "Could not renew it" — "Reconnect “Consulace Outlook” — someone needs to sign in to it again."
What happens next
- A test changes nothing when it works.
- When the service refuses to renew a sign-in — during Refresh, a test, or a run — the connection's status changes to Needs reconnecting, and the workspace's Admins and Editors get a notification: "Consulace Outlook needs reconnecting". See Reconnecting a connection that stopped working.
Good to know
- You can also test a key, token or database before it is kept: leave Test the connection before saving ticked when you add or reconnect it. If the service refuses, nothing is saved or changed.
- A database test signs in and runs
select 1, with 15 seconds to connect. - Bizomate renews sign-ins by itself before they lapse. Refresh is for checking, not something you need to do.
If something goes wrong
| What you see | Why | What to do |
|---|---|---|
| "Microsoft Graph returned 401. The token may be invalid or lack permission." | Microsoft no longer accepts the sign-in. | Reconnect it. |
| "Google returned 401. The sign-in may have been withdrawn — reconnect it." | The Google account withdrew Bizomate's access, or the sign-in ended. | Reconnect it. |
| "Access token expired and refresh failed. Reconnect this connection." | The sign-in could not be renewed. | Reconnect it. |
| "This connection has no valid token. Reconnect it." | The connection holds no sign-in — it was revoked, for example. | Reconnect it. |
| "HubSpot refused the connection: … Reconnect it, or replace the token." | HubSpot no longer accepts the token. | Reconnect it with a new private app token. |
| "PostgreSQL refused: …" or "SQL Server refused: …" | The database turned the sign-in down, with its own reason. | Check the user, password and firewall, then reconnect. |
| "… is not on the public internet, so workflows cannot reach it." | The server's address is a private one. | Use the server's public address. |
| "Test connection isn't available for this provider yet." | That service has no test. | Run a step that uses it instead. |