Copper Trigger

Start a workflow when a Copper record is created, or when a property on an existing record changes, so downstream steps can react to CRM activity in Copper.

What It Does

Fires when a Copper company, person, opportunity, lead, or project is created, or when a property on an existing record changes on an update. For update events, you can narrow the trigger to a single watched property and add a value filter so the workflow only runs on the specific change you care about.

When It Fires

Fires on every qualifying event. There is no per-record enrollment memory, so if the same record qualifies more than once, the workflow runs again each time; add a deduplication node downstream if you need once-per-record behavior. Created events do not support property or value filters. Updated events can watch one property at a time; to watch multiple properties, add multiple trigger nodes. If an updated trigger has no watched property set, the output reflects the first field Copper reports as changed for that event.

Configuration

Configure the node with these settings:

Field	What it controls
Event type	`created` or `updated`. Required.
Object type	`companies`, `people`, `opportunities`, `leads`, or `projects`. Required.
Watched property	The Copper field to monitor on update events. Required whenever a filter operator or filter value is set.
Filter operator	How to compare the watched property, such as `changes_to`, `changes_from`, `is_greater_than`, `crosses_above_threshold`, `is_set`, or `contains`. Only applies to update events.
Filter value	The value to compare against. Required for operators that need one.

Outputs

The node passes these values downstream. Check the Outputs tab on the configured node to confirm exact paths.

Variable	Type	Description	Example
`eventType`	`"created" \| "updated"`	"created" or "updated"	`{{nodeId.eventType}}`
`objectType`	`"companies" \| "people" \| "opportunities" \| "leads" \| "projects"`	Copper object type	`{{nodeId.objectType}}`
`objectId`	`string`	Copper record ID of the affected object	`{{nodeId.objectId}}`
`occurredAt`	`string`	ISO 8601 timestamp of the event	`{{nodeId.occurredAt}}`
`propertyName`	`string \| null`	Internal name of the watched property when the event was an update, otherwise null	`{{nodeId.propertyName}}`
`propertyValue`	`string \| null`	New value of the watched property at trigger time	`{{nodeId.propertyValue}}`
`previousValue`	`string \| null`	Previous value before the change, null for created events	`{{nodeId.previousValue}}`
`name`	`string \| null`	Display name for the Copper record when available	`{{nodeId.name}}`
`email`	`string \| null`	Primary email for people or leads when available	`{{nodeId.email}}`
`copperCompanyId`	`string \| null`	Copper company ID when objectType is companies	`{{nodeId.copperCompanyId}}`
`copperPersonId`	`string \| null`	Copper person ID when objectType is people	`{{nodeId.copperPersonId}}`
`copperOpportunityId`	`string \| null`	Copper opportunity ID when objectType is opportunities	`{{nodeId.copperOpportunityId}}`
`copperLeadId`	`string \| null`	Copper lead ID when objectType is leads	`{{nodeId.copperLeadId}}`
`copperProjectId`	`string \| null`	Copper project ID when objectType is projects	`{{nodeId.copperProjectId}}`
`properties`	`object`	Hydrated Copper record fields serialized as strings	`{{nodeId.properties}}`

Example Workflow

Watch opportunities for updates where a pipeline stage field changes to "Closed Won", then run the Copper Agent to add a note and notify the account team.

Copper Agent
On HubSpot Object Event
On Salesforce Deal Updated

Need More Help?

Reach the AskElephant support team by:

clicking the Support tab on the right side of your screen,
emailing [email protected],
or using @askelephant support in your dedicated Slack channel.