CRM / Finance
Mailchimp OAuth
Use the OAuth metadata response to discover the account-specific API endpoint and data-center prefix.
Automated OAuth formProvider docs
What this workflow can do
- Build authorization URL
- Exchange authorization code
- Refresh token
- Verify access token
Before starting
- Client ID
- Client secret
- Redirect URI
- Provider-approved scopes
- PKCE only if your app requires it
- Callback code and state
Result handling
- Access token returns from exchange and can be verified in the result panel.
- Refresh token is not advertised for this provider.
- Callback state is only used to validate the current handshake.
- Anonymous OAuth Hub workflows do not store client secrets, authorization codes, access tokens, or refresh tokens.
- 01PrepareEnter provider credentials, scopes, callback details, and PKCE values if required.
- 02AuthorizeBuild the authorization URL and open provider consent.
- 03ExchangePaste the returned code and state, then exchange them for tokens.
- 04VerifyTest the access token against the provider verification endpoint.
- 05Next stepsCopy tokens or metadata, then store them safely outside anonymous mode.
Returned from provider
Callback summary
Review returned callback values before exchanging.
- Authorization code
- Present
- Returned state
- Present
- Provider error
- —
- Error description
- —
- Error URI
- —
Troubleshooting
- Mailchimp Marketing API requests must use the api_endpoint returned by the metadata endpoint.
- OAuth tokens do not use a standard refresh-token flow; re-authorize after revocation.