Reference · Credentials
Netlify API credentials
Used by 2 BusyBot nodes.
netlifyApi 1 field The Netlify credential holds a personal access token created in your Netlify user settings. It acts as your user across every team and site you can reach, so treat it as a full-access secret.
Fields
| Field | Type | Required | Notes |
|---|---|---|---|
Access TokenaccessToken | password | Yes | Your Netlify Personal Access Token. |
Getting your credentials
- Sign in to Netlify and open your User settings.
- Go to Applications and create a personal access token, naming it for where it will be used.
- Copy the token immediately — it is shown only once.
- Paste it into the credential’s Access Token field in BusyBot.
Permissions and scopes
A personal access token carries your full Netlify access, including every team you belong to. There are no per-token scopes, so revoke and replace it rather than trying to narrow it.
Troubleshooting
- 401 Unauthorized — the token is wrong or was revoked in Applications settings.
- 404 on a site — the site ID is wrong, or your account is not a member of the team that owns it.
- Deploy operations rejected — check your role on the team; site-level permissions still apply.
Frequently asked questions
Where are Netlify tokens created?
Under User settings → Applications, as a personal access token.
Can I limit what the token can do?
Not per token — it carries your full account access. Revoke and replace it if it needs to be retired.
Does one token cover the Netlify node and its trigger?
Yes, both declare the same credential type.
Nodes that use Netlify API
One credential works across every node below — create it once and reuse it.
Last updated . Spotted something wrong? Tell us.