Integrations

The Integrations screen manages workspace connections for Stripe, Slack, Calendly, and Notion. A workspace can keep more than one labeled connection. Before you reconnect or disconnect a connection, you can see which agent behavior depends on it.

Find a connection

The screen has two panes. The left pane lists the four providers. Each provider row shows a status dot and the number of connections it holds. The dot rolls up the connections below it, so it shows the worst status of the group. Select a provider to open its connections in the right pane.

Select Add connection to add another connection to the selected provider. A provider with no connections shows Connect with the provider name instead.

Each connection shows its name, the account at the provider, a status dot with a supporting line, the granted scopes, the agents that use it, and the connection ID with a copy button. Stripe declares no scopes, so no scope list appears for it. A connection that needs attention gets an amber border and an inline Reconnect button.

Read the connection status

A connection reads Connected, Expiring, or Needs attention.

A connection that holds a refresh token reads Connected. It renews its own access token, so a short access-token expiry is normal there and is not a warning.

A connection that holds no refresh token reads Expiring inside the last 7 days of its access token, and Needs attention after that token expires. A connection whose refresh token stopped working reads Needs attention immediately, whatever its access-token expiry says. Only a reconnect clears that state. The next successful refresh clears the mark by itself.

AgentStack emails the organization owner once for each connection that needs attention. The check runs one time each day. The owner gets one message when the connection starts to expire, and one more after it expires. Admins do not get these messages, and no member other than the owner does. Watch the screen too, because a workspace whose owner does not read that mailbox gets no other warning.

Connection authorization requires an authenticated organization member. This check happens twice: when authorization starts, and when the provider callback returns. Any authenticated member can authorize a connection, not only administrators. Provider configuration can still prevent the flow from starting. Return targets stay limited to the workspace Integrations screen. Treat a failed callback as a failure to investigate. A failed callback is not proof that a provider account was linked.

Disconnecting a connection is an administrator-only action. The screen shows the impact of disconnecting before you confirm it. Review every linked agent, action, and channel first. A disconnected credential can leave configuration in place but unusable. For per-agent action behavior, see the Actions and Channels documentation. This page describes the shared workspace credential lifecycle.