Connect services without putting secrets in chat

Use credential cards, OAuth sign-in, and reconnection flows.

Ask the Assistant to connect the service you need. It can find the connector, explain its requirements, and propose creating a connection. The sign-in method determines the next step.

Credential-based services

After the connection draft is created, use the secret card for its key or credentials. Those values are sent by the browser through the credential flow. Do not paste them into the conversation or an attached text file.

The Assistant can inspect the connection's status and whether setup is still required. It does not need to see the stored secret to test the connection or explain a failed test.

OAuth services

Use the service's sign-in and consent flow. Check which account you are authorising and the requested access. Finish the provider window and return to Strive. A connection stays pending until the sign-in succeeds.

If consent was cancelled or a popup was blocked, restart the connection's sign-in flow. Reconnecting an expired connection is usually preferable to creating another one because existing workflows may already reference it.

Managed and no-sign-in services

Managed Strive services can be provisioned without entering external credentials. A no-auth connector may also need no sign-in. “No sign-in” describes authentication; it does not mean every possible destination or file is accessible.

Rotate access

Ask to update or rotate the credentials on the existing connection. Use the credential form, test the connection, and check a dependent workflow. Revocation wipes stored credentials and stops access; deletion removes the connection itself. See connection lifecycle.