Copper Trigger

Start workflow from Copper CRM events

Overview

Triggers a workflow when events happen in Copper CRM. Listens for create, update, or delete events on companies, leads, opportunities, people, projects, and tasks. Copper sends a webhook POST with the event payload, which is verified using an MD5 secret derived from the account credentials.

Category: Sales
Tool Name: copper_trigger
Version: 1

Appearance: Icon: lucide-CircleDollarSign | Color: #f7a925

Node Type

Trigger — webhook (receives incoming HTTP callbacks)

Input / Output

Direction	Port(s)
Input	None (trigger node)
Output	`Output`

Credentials

This tool requires Copper API credentials. See the Credentials Guide for setup instructions.

Resources

Resource	Value
Company	`company`
Lead	`lead`
Opportunity	`opportunity`
Person	`person`
Project	`project`
Task	`task`

Select the resource that fires the event. It is required.

Parameters

Parameter	Type	Required	Default	Description
Event	`options`	Yes	—	The event to listen to.
				Options: `delete` (an existing record is removed), `new` (a new record is created), `update` (any field in the existing entity record is changed)

Output Data

Each delivery from Copper produces one output item. The webhook payload is copied onto the item unchanged, and three fields are added:

_trigger — always copper_trigger_webhook
_timestamp — ISO 8601 timestamp of when the request arrived
_webhookEvent — the resource and event joined with a dot, e.g. person.new

The Copper payload itself carries:

type — the resource type that changed, e.g. person
event — the event that occurred: new, update, or delete
ids — the IDs of the affected records
subscription_id — the Copper webhook subscription that delivered the event
updated_attributes — the fields that changed, on update events

Copper also sends a secret field, which the trigger checks before starting the workflow; deliveries that do not match are rejected.

Reference the payload downstream by expression, e.g. {{ $json.ids[0] }}.

Usage Examples

trigger workflow when a new lead is created in Copper
start when a company is updated in Copper CRM
listen for deleted opportunities in Copper
react to new person records in Copper
watch for task changes in Copper CRM

Example Configuration

Fire when a new lead is created:

{
  "type": "copper_trigger",
  "parameters": {
    "resource": "lead",
    "event": "new"
  }
}

Trigger Behavior

Activation: When the workflow is activated, a webhook endpoint is registered with the service.
Deactivation: The webhook is automatically unregistered when the workflow is deactivated.
Payload: The incoming webhook payload is parsed and output as workflow items.
Verification: Supports signature verification where applicable.

Tips

Entry point that fires when Copper CRM sends a webhook for the selected resource and event type. Outputs the full event payload including resource data, event type, and metadata.

Frequently asked questions

What credential do I need to connect Copper Trigger?

You need a Copper API credential (copperApi) configured in BusyBot. Copper Trigger uses this credential to derive an MD5 secret, which is used to verify that incoming webhook payloads genuinely originate from your Copper account and have not been tampered with.

Which Copper resources and event types can this node listen to?

Copper Trigger supports six resource types: companies, leads, opportunities, people, projects, and tasks. For each, you can listen to create, update, or delete events. You select one resource and one event type per node instance — if you need to cover multiple combinations, use multiple Copper Trigger nodes in your workflow.

What data does the node actually output when it fires?

The node outputs the full webhook payload sent by Copper, which includes the resource data (the fields of the affected record), the event type (create, update, or delete), and associated metadata. Everything Copper includes in its POST is passed through, so downstream nodes have the complete context of what changed.

How does Copper know where to send webhook events?

Copper Trigger is a webhook trigger, meaning BusyBot generates a webhook URL when you activate the workflow. You register that URL inside your Copper account's webhook settings, pointing it at the resource and event type you want to monitor. Once registered, Copper will POST to that URL whenever the matching event occurs.

How does the node verify that incoming webhooks are legitimate?

Copper Trigger validates each incoming request using an MD5 secret derived from your Copper API credentials. This ensures that only webhooks originating from your Copper account are accepted and processed — any request that fails verification will not trigger the workflow.