Connecting a service
1
Open Integrations in your workspace
Go to Settings → Integrations and find the service you want.
2
Click Connect
GoConva sends you to the provider’s own sign-in and consent screen.
3
Approve the requested access
The provider shows exactly what GoConva is asking for. Each service guide
lists these permissions so you know what to expect before you see the
screen.
4
You land back in GoConva
The connection appears in your Integrations list, ready to use in agents and
workflows.
Who can connect
Connecting requires the admin or builder role. Members cannot start a connection. Connections belong to the workspace, not to the person who authorized them. Once an admin connects Slack, everyone in the workspace can use it.Staying connected
Access tokens expire, so GoConva stores a refresh token where the provider supports one and renews access automatically in the background. You should not need to reconnect routinely. Credentials are encrypted at rest. A connection does stop working if someone revokes GoConva’s access at the provider, the authorizing user’s account is disabled, or the provider’s app registration changes. In each case the fix is to reconnect.Checking a connection
Each connection in the Integrations list has a Test action. Use it after connecting, and whenever an agent or workflow step involving that service fails unexpectedly — a revoked or expired grant shows up here first.When permissions change
The permissions a connection holds are fixed at the moment you approve them. If a GoConva update starts requesting additional access, existing connections keep the access they were granted until someone reconnects and approves the new set. If a workflow step fails with a permissions error on a service that used to work, reconnecting is usually the fix.Common problems
The first two rows are configuration on the provider side, not something you can
fix inside GoConva. If you are self-hosting, see the setup section of the
relevant service guide.