Skip to content
Docs

Start here

↑ ↓ navigate · Enter open · Esc closeSearch all 418 articles

Create and authorize a connection

Configure credentials, OAuth consent, and service access without sharing secrets in chat.

Choose the service in the catalog, then complete the connection form for that connector. The required fields come from the selected service: an API token, account identifier, endpoint, database details, or another provider-specific credential. Read the field descriptions before submitting; credentials for a different account or product can be valid yet point to the wrong data.

Credential connections

Use a credential issued for the account and resources you intend Strive to access. Complete secret fields in the connection form or the Assistant's secure credential card. Do not paste a secret into an ordinary conversation, document, connection name, or workflow description. A connection reference is sufficient for later use.

Some services use API keys; others require service-account information. The service's requested fields determine the configuration. Strive does not convert a personal credential into a service account or expand a provider permission that the credential lacks.

OAuth connections

For OAuth, continue to the provider, confirm the signed-in account, review the requested access, and complete consent. The connection remains pending until authorization succeeds. Cancelling consent or closing the provider window early leaves authorization incomplete. Return to the connection and finish authorization before testing it or starting a dependent workflow.

Choose the correct organization or account at the provider, especially if you have several sessions open. Strive can only access what the provider grants. If files are missing afterward, check account selection and provider permissions before creating a duplicate connection.

Confirm the result

Give the connection a useful display name and open its detail page. Check the service identity and status, then test access. If creation reports an existing connection, inspect that connection first; retrying with a different name does not necessarily create a separate resource.