Copper
Copper CRM lifecycle events on Gmail-native teams
Copper is the CRM built for teams already living inside Google Workspace, the lead, person, company, and opportunity surface, but with Gmail and Calendar treated as first-class data sources. Ten triggers cover the lifecycle: Lead Newd (new lead), Lead Updated, Lead Deleted, Opportunity Newd, Opportunity Updated, Opportunity Deleted, Company Newd, Company Updated, plus contact-level changes. Six actions cover the writes: Create Opportunity, Create Person, Update Person, Get Person, List Leads, List People. The integration uses Copper's OAuth, scoped to the user's permissions on the relevant pipelines and contact lists. Common patterns: an Opportunity Newd on Copper fires a workflow that creates the matching project in Asana, sets up a paired Notion CS handoff page, and DMs the assigned AE in Slack; or a Lead Updated with a stage-equals-qualified change syncs the lead into HubSpot for the marketing team's nurture sequence. Copper's Gmail-side data (the meeting and email associations on each contact) comes through automatically on every payload.
Workflows start when Copper does.
10 real-time triggers, each backed by a webhook subscription. Events arrive within seconds and you don't have to set up polling.
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.
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.
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.
Fires when a new lead is added to Copper. The base hook for "new lead → fan out to slack-channel + sheet + enrichment" workflows.
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.
Fires when an opportunity is removed from the pipeline. Useful for forecasting workflows that need to subtract deleted opportunities from running totals.
Fires when a new opportunity is added — manually, via automation, or via API. The pipeline-growth hook: log to revenue forecast, notify the AE in Slack, sync to a deal-tracking sheet.
Fires on any opportunity change — stage transitions, value updates, owner changes. For "stage moved to Closed Won" specifically, filter the payload before downstream side-effects.
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.
Fires on any change to a person record. For "title changed" or "company changed", filter on the specific updated field for downstream re-routing or re-segmentation.
Do anything Copper can do, from a workflow.
Every action accepts dynamic inputs from upstream nodes, whether that's an AI output, a form field, or a search result.
| Action | What it does |
|---|---|
| Create Opportunity | Creates a sales opportunity tied to a person and/or company with value, pipeline, stage, owner. For "form said they want to buy → auto-create opportunity for the AE" workflows. |
| Create Person | Inserts a new person with email, name, phone, optional company link, custom fields. Copper dedupes on primary email; existing emails error rather than upserting (wrap in search-first if uncertain). |
| Get Person | Returns a person by ID or email with all standard and custom fields plus related company and recent activities. The standard lookup before update workflows. |
| List Leads | Paginated leads with filters by status, source, owner, modified date. For sync workflows to a warehouse or for "leads stale 30+ days, send re-engagement" lifecycle automation. |
| List People | Paginated people with filters by company, owner, custom-field values. For warehouse syncs use the modified-since filter to incrementally pull only touched records. |
| Update Person | Partial update — only passed fields change. For "Clearbit enrichment ran → write firmographic data back to Copper" or "support ticket categorized → add tag to person" augmentation workflows. |
Pre-built Copper workflows.
Clone any recipe and customize it in one click. Every recipe is fully editable.
Three things worth knowing.
Tiny Command counts a run the moment a trigger fires. Filtering early means only matching events spend your usage budget.
Connect Copper once and every workflow on your account can use its triggers and actions. You don't have to re-auth per workflow.
Every Copper field shows up in the visual picker for downstream nodes. The raw payload is there for power users, optional for everyone else.
Questions about the Copper integration.
If we missed yours, ping support. We usually reply within an hour.
How do I connect Copper to Tiny Command?
What Copper triggers does Tiny Command support?
What Copper actions can I run from a workflow?
Is the Copper integration real-time?
Do I need to write code to use Copper with Tiny Command?
How much does the Copper integration cost?
More crm & sales apps people connect.
Same category as Copper, ordered by how often teams pair them. Hover the carousel to pause.
Do more with Copper.
Wire it to Slack, Notion, HubSpot, Stripe, or any of the other 438 apps in our catalog. Setup takes roughly two minutes. Free to try, no credit card.
