Copper integration

What it does

The Copper integration lets you run CRM automations on behalf of any client whose Copper account you manage. Connect a Copper account once, then create and read people, push new leads and opportunities into the right pipeline stage, schedule follow-up tasks, and watch for newly added contacts without writing any code.

Connect a Copper account

1. In TaskJuice, open Settings -> Connections and choose Add connection -> Copper.
2. In Copper, sign in as the user TaskJuice should act on behalf of, then open Settings -> Integrations -> API Keys.
3. Generate a new API key, copy it, and paste it into the API Key field in TaskJuice.
4. Enter the email address of the Copper user that owns the key in the Account Email field. Copper requires this on every request alongside the access token.

The connection is read- and write-capable across people, leads, opportunities, tasks, and pipelines scoped to that user's permissions in Copper. Rotate or revoke the API key from the same Settings -> Integrations -> API Keys page at any time.

Triggers

• copper/new-person. Polls Copper for newly created people and emits one activation per cycle wrapping every observed person in an items array. Drop a Loop node downstream to process each contact individually.

Actions

• copper/create-person. Create a new person (contact) with emails, phone numbers, title, company, notes, and tags.
• copper/get-person. Fetch a single person by Copper ID.
• copper/create-lead. Create a new lead with contact details, company, monetary value, and status.
• copper/create-opportunity. Create a new opportunity against a specific pipeline and stage, with monetary value, close date, and primary contact.
• copper/create-task. Create a follow-up task tied to a related record (person, lead, opportunity, or company) with assignee, due date, priority, and status.
• copper/list-pipelines. List all opportunity pipelines and their stages, useful for populating pipeline and stage pickers in downstream actions.

Known limitations

• Copper applies a per-account rate limit of 600 requests per minute documented at https://developer.copper.com/introduction/requests.html. TaskJuice retries on 429 responses honoring the Retry-After header.
• Copper does not publish outbound webhooks for newly created records on every plan tier. The new-person trigger uses polling so it works on every Copper plan. Tune the poll interval and per-cycle ceiling on the trigger's advanced settings.
• API key authentication is scoped to the Copper user whose key was copied. Switching users requires rotating the connection's API key and updating the account email.
• Date fields on opportunities use Copper's documented MM/DD/YYYY string format; tasks use Unix epoch seconds. Mismatches will surface as 422 VALIDATION_ERROR responses.