Copper currently provides 11 triggers that can start a workflow and 20 actions a workflow can run. Use those building blocks to keep account, contact, and deal context attached to the work around it.
New Activity
Triggers when a new activity is logged
New Person
Triggers when a new person/contact is created.
New Lead
Triggers when a new lead is created.
New Task
Triggers when a new task is created.
Updated Lead
Triggers when a lead is modified.
Updated Task
Triggers when a task is updated.
Updated Opportunity
Triggers when an opportunity changes.
Updated Opportunity Stage
Triggers when an opportunity stage changes
Updated Opportunity Status
Triggers when an opportunity's status changes.
Updated Project
Triggers when a project is updated.
Updated Lead Status
Triggers when the status of a lead changes.
Create Person
Adds a new person/contact.
Update Person
Updates a person based on matching criteria.
Create Lead
Adds a new lead.
Update Lead
Updates an existing lead.
Convert Lead
Converts a lead into a person (optionally with company/opportunity).
Create Company
Adds a new company.
Update Company
Updates a company record.
Create Opportunity
Adds a new opportunity.
Update Opportunity
Updates an opportunity using match criteria.
Create Project
Adds a new project.
Update Project
Updates a project record.
Create Task
Adds a new task under a person, lead, or opportunity.
Create Activity
Logs an activity related to CRM entities.
Search for an Activity
Find an existing activity by type/criteria.
Search for a Person
Lookup a person using match criteria.
Search for a Lead
Lookup a lead using match criteria.
Search for a Company
Lookup a company.
Search for an Opportunity
Lookup an opportunity.
Search for a Project
Lookup a project.
Custom API Call
Make a custom API call to a specific endpoint
These recipes are generated from the triggers, actions, and categories currently available for this piece. Use them as starting points, then choose the exact fields, conditions, and records your workflow should update.
Start from a supported Copper event, then create or update the appropriate CRM, project, or custom record with the source context preserved.
Starts with
New Activity
Finishes with
Create or update a Coherence record
Use a change in Coherence to run a supported Copper action, so the next step follows the record instead of relying on someone to copy it.
Starts with
A Coherence record or workflow changes
Finishes with
Create Person
Combine Copper with another integration and Coherence records to keep account, contact, and deal context attached to the work around it.
Starts with
New Activity
Finishes with
Create Person, then preserve the outcome in Coherence
The exact authentication fields depend on Copper. The workflow structure stays straightforward:
Authorize the Copper account and permissions the workflow needs.
Select one of the current triggers or actions listed above and map its fields.
Run a small test, inspect the result in both systems, and only then enable the workflow.
Explore apps that share a category with Copper or provide a complementary trigger or action.
Copper currently provides 11 triggers that can start a workflow and 20 actions a workflow can run. Use those building blocks to keep account, contact, and deal context attached to the work around it.
Copper currently lists 11 triggers and 20 actions in the integration catalog. The supported list is refreshed from the pieces available in Coherence, so review the capability names on this page before building a workflow.
Yes. A workflow can combine supported Copper triggers or actions with Coherence records and other available integrations. The exact flow depends on the authentication, permissions, triggers, and actions exposed by each connected app.
The listed triggers and actions are designed for visual workflows. If the pre-built integration does not expose a capability you need, HTTP and webhook steps can cover APIs that your team is authorized to use.
Start automating in minutes. No credit card required.
