Copper

Copper

· #366 most-used

The CRM that lives inside Google Workspace

CRMSalesMarketingCommunicationAutomation

Copper is a Google-native CRM built for teams that live in Gmail, Calendar, and Drive — contacts, leads, opportunities, and pipeline management all surface inside the tools your team already uses. Connect it to Actionist and your agents can create companies and contacts on first contact, log call notes automatically, advance opportunities through stages, search for any person or deal in seconds, and fire workflows the moment a lead is created or a deal closes — all without a rep ever opening the CRM tab.

Average time saved
12 hours
per person · per month
≈ 2 workdays back

Eliminates manual work. Agents eliminate the manual CRM data entry, activity logging, and cross-system copy-paste that Google Workspace teams do between Gmail, Calendar, Drive, and Copper every day.

Schedule

What your Copper agent runs on autopilot

A week of scheduled jobs your Actionist agent will execute on your behalf.

28Scheduled jobs
7Agents at work
24/7Always on
Agents
WedFri
Wed
Thu
Fri
7a
8a
9a
10a
11a
12p
1p
2p
3p
4p
5p
6p
Multi-app workflows

Copper × every other app you use

End-to-end automations that span multiple apps — each one a real business outcome.

6Workflows
9Apps spanned
~34 hrsSaved / week
6Personas served
For customer success
Featured4 apps

Gmail inquiry → Copper record → CSM briefed

When a customer emails the support alias with a renewal concern, your agent searches Copper for the contact, reads their open opportunities and last activity date, logs a 'Email Received' activity on the record, and posts a CSM brief to Slack — with account health, open tasks, and renewal date — before the CSM has finished reading the subject line. No context-switching, no missed signals, no surprise churn.

~6 hrs

Time saved for your team — every week, on autopilot

The flow
Trigger·When a new email arrives in Gmail from a customer address matching a Copper person record
Result
Log 'Email Received' activity on the opportunityPost CSM brief with account health and renewal dateCreate follow-up call event on CSM's calendar
The win
Saved per run
25 min
Runs / week
~15×
Every customer email becomes instant CSM context
Driven byCustomer Support Agent
ROI

Savings

What your team gets back — two angles: what you stop doing manually, and what that's worth.

Without Actionist

What you do manually today

With Actionist

What your agent runs for you

  • Sales
    21 min / week
    Manual deal entry

    Reps hand-type every new opportunity into Copper after each discovery call, pulling from notes, email threads, and calendar invites.

    Sales Agent
    0 min
    Opportunity auto-created on call end

    Agent creates the Copper opportunity the moment a qualifying call ends, pre-populated with company, contact, and estimated value from the conversation.

  • Marketing
    15 min / week
    MQL lead routing

    Marketers manually export MQLs from their automation platform and paste them into Copper, tagging source and assigning reps one by one.

    Marketing Agent
    0 min
    MQL upserted with source tag

    Agent upserts each MQL into Copper with UTM source, campaign name, and lead score the instant the marketing platform fires the qualification event.

  • Customer Support
    21 min / week
    Ticket-to-account lookup

    Support reps manually search Copper to identify which account a ticket belongs to, then cross-reference the CSM and account health before responding.

    Customer Support Agent
    0 min
    Account context fetched instantly

    Agent searches Copper by the ticket sender's email, returns the account owner, renewal date, and last activity, and attaches the summary to the ticket in under five seconds.

  • Human Resources
    8 min / week
    Rep offboarding cleanup

    When a sales rep leaves, HR and sales ops manually reassign every Copper company, opportunity, and task owned by the departing employee across dozens of records.

    Human Resources Agent
    0 min
    Ownership batch-transferred

    Agent reads the departing rep's record list from Copper and updates every owned company, opportunity, and task to the designated cover in a single automated pass.

  • Finance
    15 min / week
    Closed-won revenue capture

    Finance manually checks Copper for newly closed deals each week, tallying values and copy-pasting deal names into the revenue recognition spreadsheet.

    Finance Agent
    0 min
    Revenue row written on close

    Agent detects each Closed Won opportunity in Copper, writes the deal value, close date, and rep to the revenue Google Sheet within seconds of the stage change.

  • Operations
    33 min / week
    Pipeline data exports

    Ops runs weekly Copper exports, reformats the CSV, removes duplicates, and pastes the data into the board-ready Google Sheet and Notion dashboard manually.

    Operations Agent
    0 min
    Pipeline synced automatically

    Agent queries Copper every Monday, computes weighted ARR per stage, and writes the result directly to the forecast Google Sheet and Notion board before standup.

  • Legal
    7 min / week
    Contract counterparty lookup

    Legal manually searches Copper for company and contact details when preparing NDAs and MSAs, then copy-pastes addresses and signatory names into contract templates.

    Legal Agent
    0 min
    Counterparty data auto-filled

    Agent fetches the company and primary contact from Copper by deal name, then pre-populates the contract template with legal entity, address, and authorised signatory.

+ 100s of other Copper automations
Average monthly
12 hrs / person / month
Average monthly
12 hrs / person / month
Calculator

Calculate what your team saves

Team size
10 people
Hourly rate
$20 / hr
Hours saved / week
30
Hours saved / year
1,500
Annual ROI
$30,000

Based on Copper's typical team usage — the visible tasks plus a few other automations the agent runs: ~3 hrs / person / week of admin work automated.

Connect

How to plug Copper into Actionist

Pick the connection method that suits your environment.

The fastest path for Google Workspace users. Actionist's MCP server connects to Copper through a permissioned handshake — no tokens to rotate, no webhook URLs to configure. Your agent gets read and write access to companies, contacts, leads, opportunities, projects, and tasks within seconds.

1
Open the Apps tab

Find Copper in the Apps library and click Connect. MCP is selected by default.

2
Authorise in Copper

You'll be redirected to Copper's authorisation page. Sign in with your Copper account and grant Actionist the requested read/write permissions for your workspace.

3
Test the connection

Actionist runs a read-only call to verify the handshake. You're ready.

Actions

36 actions your agent can call

Read and write operations available to your Actionist agent.

Triggers

10 events your agent can react to

Events your agent watches for, and the actions it kicks off in response.

Skills

Skills that pair with Copper

Reusable agent skills that work well alongside this app.

Frontend Design Ultimate

Generates production-grade React and Tailwind UI components for Copper-connected dashboards, CRM report pages, or account-portal interfaces.

Market News Analyst

Analyses market-moving news and earnings events to surface timely account intelligence an agent can log as Copper activities before rep outreach.

MCP servers

MCP servers that work with Copper

Connect Actionist to MCP servers built for or around this app.

No MCP servers indexed for this app yet.
FAQs

Questions about Copper + Actionist

How do I connect Copper to Actionist?
Open the Apps tab, find Copper, and click Connect. The default MCP path redirects you to Copper's authorisation page where you grant Actionist read/write access to your workspace. The whole process takes under two minutes. If you prefer token-based access, switch to the API Key method and paste your Copper API key and the email address that generated it.
What permissions does Actionist need in Copper?
Actionist requests read and write access to companies, people, leads, opportunities, projects, tasks, and activities. The MCP path uses a permissioned OAuth handshake scoped to your Copper workspace — no admin-level access is required. If you use the API key method, the key inherits the permission level of the Copper user account that generated it, so use an account that has access to all records your agent needs to read or update.
Which Copper objects can agents read and write?
Agents can create, read, update, and delete companies; create and update people, leads, opportunities, and projects; create tasks; log activities (calls, emails, meetings, notes); and associate records to projects. Search actions across all these object types let agents look up records before writing to avoid duplicates. The full action list is in the Actions tab above.
Can Actionist react to real-time Copper events?
Yes — Copper fires webhook events for new and updated companies, people, leads, opportunities, projects, and tasks, plus new activities and deletions. Actionist listens to these webhooks so your agent can react within seconds: enriching a new lead the moment it lands, advancing a deal when a contract is signed, or alerting a CSM when a key contact's record is updated.
How do I avoid creating duplicate Copper records?
Use the upsert actions — 'Create/Update Company', 'Create/Update Person', 'Create/Update Lead', 'Create/Update Opportunity', and 'Create/Update Project' — which match on domain or email before deciding whether to create or update. Alternatively, use the Search actions first to confirm a record doesn't exist before calling Create. For high-volume inbound flows, the upsert pattern is the safest default.
How do I prevent trigger loops when my agent updates Copper records?
Copper's Update webhook fires on every field change, including ones your agent writes. Guard against loops by checking a distinguishing field before acting — for example, only process the event if the changed field is 'Stage' and the new value is 'Closed Won', not on every update. Actionist lets you add these conditions as filter steps at the start of trigger-based workflows. You can also use a custom Copper field like 'Agent Processed' and skip the workflow when it's already set.
Does Actionist work with Copper's Google Workspace integration?
Yes. Copper is built to surface inside Gmail, Google Calendar, and Google Drive, and Actionist can orchestrate across all four in one workflow. For example, an agent can detect a new Gmail message, look up the sender in Copper, log a 'Email' activity on the matching opportunity, and create a Calendar follow-up — without leaving Gmail. The Google app connections (gmail, google-calendar, google-sheets) are all available as companion steps in Copper workflows.
What are Copper's API rate limits and how should I plan around them?
Copper's REST API enforces rate limits per account — typically 600 requests per minute on standard plans. For bulk operations like importing a list of 500 companies, design your workflow to batch records and include a short delay between calls. Upsert actions are especially efficient here: one call per record instead of a separate search plus create. Check your Copper plan documentation for the exact limits on your subscription tier before running large automated imports.