Webflow OAuth2 credentials

Fields

Field	Type	Required	Notes
Access Token accessToken	password	Yes	Populated by the OAuth2 flow.
Refresh Token refreshToken	password	No	Webflow OAuth tokens are currently non-expiring, so refresh is usually unused.
Client ID clientId	password	Yes	—
Client Secret clientSecret	password	Yes	—

Getting your credentials

1. Sign in to Webflow and open the workspace settings area covering apps and integrations.
2. Register a new app, and add BusyBot’s redirect URL to its allowed redirect URIs.
3. Select the scopes the workflow needs — CMS read and write, site publishing, forms, and so on. Scopes are granted at authorisation and cannot be widened afterwards without re-authorising.
4. Copy the app’s Client ID and Client Secret into the credential.
5. Complete the authorisation flow, choosing the site or workspace the app may access. This populates the access token.

Permissions and scopes

Authorisation is per site as well as per scope: an app authorised on one site cannot reach another. If you add a site later, authorise the app on it too.

Grant the narrowest scopes that cover your operations. Publishing rights in particular are worth withholding from a workflow that only reads collections.

Troubleshooting

• 403 or missing scope — the scope was not selected at authorisation. Widening it requires re-authorising the app.
• Site not found — the app was never authorised on that site.
• Field validation errors on CMS items — field slugs must match the collection schema exactly, and required fields must be present.
• Published changes not visible — creating an item is separate from publishing the site; check whether the workflow needs a publish step.