BusyBot

Reference · Credentials

Copper API credentials

Used by 2 BusyBot nodes.

Type copperApi 2 fields

The Copper credential needs two values: an API access token and the email address of the account it belongs to. Copper authenticates on the pair, so the email is required rather than optional.

Fields

FieldTypeRequiredNotes
API Key
apiKey		 password Yes Your Copper API access token.
Email
email		 string Yes The email address associated with your Copper account.

Getting your credentials

  1. Sign in to Copper.
  2. Open Settings → Integrations → API Keys.
  3. Generate an API key and copy it.
  4. Paste it into the credential’s API Key field, and enter the email address of the Copper user the key belongs to in the Email field.

Permissions and scopes

The key acts as the user whose email accompanies it, so records that user cannot see are invisible to the automation.

Troubleshooting

  • 401 Unauthorized — the email does not match the account that generated the key. Both values must belong together.
  • Records missing — the user behind the key lacks access to them in Copper.

Frequently asked questions

Why does it need my email as well as a key?

Copper authenticates on the pair — the token identifies the key and the email identifies the user it belongs to. A mismatch fails authentication.

Where are Copper API keys created?

Under Settings → Integrations → API Keys in the Copper interface.

Whose permissions apply?

Those of the user whose email is on the credential, so records that user cannot see will not appear.

Nodes that use Copper API

One credential works across every node below — create it once and reuse it.

Last updated . Spotted something wrong? Tell us.