Skip to main content

​
At a glance

  • Availability: Experimental (how to enable).
  • Authentication: OAuth 2.0.
  • Connection: A user authorizes the connection in the provider’s consent screen.
  • Provider documentation: Authentication reference.

​
Credentials

Set these per environment. See Connect an integration. These variables are required only when you supply your own OAuth app. If a managed app is available, you can connect without setting them. Provider permissions and consent still apply.

​
Setup

  1. Create a CleverReach account: Sign up at cleverreach.com - the free Lite plan (up to 250 recipients) is enough for development and testing.
  2. Create an OAuth app: In your CleverReach account go to Account > Extras > REST API and create an OAuth app. Note the Client ID and Client Secret it contains, and register your redirect (callback) URL.
  3. Store the credentials and connect: Set CLEVERREACH_CLIENT_ID and CLEVERREACH_CLIENT_SECRET, then complete the OAuth authorization-code flow: the user logs in at the CleverReach consent screen and the returned code is exchanged for an access token.

​
Provider notes

  • The authorization request must include the extra parameter grant=basic alongside client_id, response_type=code, and redirect_uri.
  • Access tokens are long-lived (expires_in in the token response, for example 31536000 seconds) and a refresh_token is issued for renewing them via grant_type=refresh_token.
  • Each OAuth token is scoped to the CleverReach account that authorized the app; the app’s permissions are configured on the OAuth app itself rather than via per-request scopes.
Provider API reference.

​
Tools

​
Verify the connection

Call a read tool such as cleverreach__list_groups with arguments for your account. Confirm that the result comes from the intended account or workspace before enabling write tools.