Keap OAuth2 API credentials

Fields

Field	Type	Required	Notes
Client ID clientId	string	Yes	The OAuth2 Client ID
Client Secret clientSecret	password	Yes	The OAuth2 Client Secret
Authorization URL authUrl	string	No	The Keap OAuth2 authorization URL
Access Token URL accessTokenUrl	string	No	The Keap OAuth2 token endpoint URL
Scope scope	string	No	OAuth2 scope.
Access Token accessToken	password	No	OAuth2 access token. Required for API calls.
Refresh Token refreshToken	password	No	OAuth2 refresh token. Required for automatic token renewal. Leave blank only if the token never expires.
Token Expiry (Unix timestamp) expiresAt	string	No	Unix timestamp (seconds) when the access token expires. Managed automatically after refresh.

Getting your credentials

1. Sign in to the Keap developer portal and register an application for this integration.
2. Register BusyBot’s redirect URL against the application’s allowed redirect URIs.
3. Copy the application’s Client ID and Client Secret into the credential.
4. Complete the OAuth2 authorisation flow so the credential stores an access token and a refresh token.

The Auth URL, Token URL and Scope fields carry working defaults. Change them only if Keap’s documentation tells you to.

Permissions and scopes

The application acts with the permissions of the Keap account that authorised it, so authorise from an account whose visibility matches what the workflow should reach.

Troubleshooting

• Token expired and not renewing — the credential has no refresh token. Re-run the authorisation so one is stored; expiresAt is then managed automatically.
• Redirect mismatch during authorisation — the redirect URI registered on the Keap application does not exactly match the one used in the flow.
• 403 on a resource — the authorising account does not have access to it in Keap.