TriggerCopperReal-timeUpdated May 2026
When does Copper fire on new contacts?
Short answer: Drop the "Copper → Person Created" trigger on your workflow canvas, add filters if you want them, and publish. It fires within seconds of the event in Copper, not on a polling schedule.
Anatomy
What this trigger looks like in a workflow.
Drop it on the canvas. Configure a couple of fields. Publish.
In the builder
Trigger
Person Created
When the matching event happens
person newd addedwatch for person newdwhen a person is created in copperwhen person newdnew person newdon person newd
What this trigger returns
for the curiousYou don’t need to read this. Tiny Command auto-maps every field into the visual picker so downstream nodes can pull values by clicking. We show it here for power users who want to know what’s on the wire.
{"id": 12345,"type": "person","event": "new"}
Output shape
Fields available to downstream nodes.
Every field below can be referenced by name in any action or filter that comes after this trigger.
| Field | Type | Example |
|---|---|---|
| id | number | 12345 |
| type | string | "person" |
| event | string | "new" |
Pairs with
Drop these actions after Person Created.
FAQ
Questions about Person Created.
How does the Person Created trigger work in Copper?
Fires when a new person record is created. Useful for "auto-enrich with email-finder, push to email tool, create welcome task" cascading workflows on new contact creation.
Is the Person Created trigger real-time?
Yes. Person Created uses webhooks or push subscriptions, not polling. Your workflow fires within seconds of the event happening in Copper.
What data does Person Created return?
The full event payload from Copper. The output shape table on this page lists every field, its type, and an example value so you can map fields into downstream nodes.
Can I filter Person Created so only some events start a workflow?
Yes. Add a Filter node right after the trigger and match on any field, whether that's subject, sender, status, or anything else in the payload. Workflows only continue when the filter passes.
Do I need Copper admin permissions to use Person Created?
For most Copper accounts a standard user can authorize the trigger. Some Copper plans require an admin to enable third-party webhooks. Check Copper's docs if the trigger fails to register.
More triggers
Other Copper triggers.
Trigger
Company Created
Fires when a new company is created in the Copper CRM. Useful for "auto-enrich firmographic data via Clearbit/Apollo" workflows that augment the company record right after creation.
TriggerCompany Updated
Fires on any change to a company record — field edits, custom-field updates, owner reassignments. For specific transitions (e.g., status moved to Customer), filter the payload by changed-field.
TriggerLead Deleted
Fires when a lead is hard-deleted from Copper. Useful for compliance workflows ("ensure the lead was also removed from email tools") and for audit-trail workflows that log all CRM deletions.
TriggerLead Created
Fires when a new lead is added to Copper. The base hook for "new lead → fan out to slack-channel + sheet + enrichment" workflows.
TriggerLead Updated
Fires on any field change including status transitions. For "lead converted to person" or "lead status moved to Qualified", inspect the payload's changed-field for branching.
Build a workflow on this trigger.
One trigger. 6+ downstream actions. Zero glue.
