Resources · Make integration

Copper Make integrationAutomate Copper with Make.

What if your CRM updated itself while your reps kept selling? The Copper Make integration gives you 54 modules, including 7 instant triggers and 34 actions, to move leads, deals and tasks without code. This guide connects your account and walks you through a first scenario.

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Copper Make integration do for your team?

The Copper Make integration links your Copper CRM to Make, a no-code tool where you build a scenario (the automation itself) out of modules (single bricks: a trigger, an action or a search). Copper can alert Make the instant a lead, person, company, deal, project, task or activity changes, and Make then creates, updates, links or removes records for you.

Follow-ups that write themselves. Listen for Opportunity Events fires when a deal is created or edited, and Create Task drops a reminder on the owner's list. Nobody has to remember to add it by hand.

Leads that graduate cleanly. When a lead is qualified, Convert Lead turns it into a person and can attach a company and an opportunity in the same step, so a sales team keeps one record instead of three half-filled ones.

A tidy relationship map. Relate Items (Advanced) ties leads, people, companies, opportunities, projects and tasks together, and Create Connection records links like a referral or a parent company. Useful for agencies that sell to groups of related clients.

What Make does not offer here: Copper has no Make an API Call module, so an operation missing from the 54 modules is out of reach from this app, and the Copper documentation lists no limits to plan around. Before choosing a plan, the Make pricing page explains how operations are counted.

Copper also exists as a node in n8n. If your team hesitates between the two tools, read the Copper n8n integration page and the n8n vs Make comparison side by side.

Connect

How do you connect Copper to Make?

  1. 01

    Add a Copper module

    Open your scenario, click the big +, type Copper and pick any module. In its settings, click Create a connection. A connection is your Copper account linked to Make once, then reused by every Copper module.

  2. 02

    Name it and authorize Make

    Give the connection a name if you like, handy when a colleague connects a second Copper account later. Then follow what Make asks: approve access on the Copper page that opens, or paste the key Copper gives you.

  3. 03

    Save and check the lists

    Click Save. Back in the module, Make can now read your Copper data, so the fields that expect a record start offering choices instead of an empty box. That is the sign the link works.

First scenario

Your first scenario with Copper and Make

GoalWhen a deal is created, edited or removed in Copper, Make adds a task so the owner checks it.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the + in the middle of the canvas. This first slot always holds the trigger, the module that starts everything.

  2. 02

    Add the deal trigger

    Search for Copper and choose Listen for Opportunity Events. Select your connection or click Create a connection. It is an instant trigger: Copper calls Make through a webhook as soon as a deal changes.

  3. 03

    Add Create Task

    Click the + on the right of the trigger, pick Copper again, then Create Task. Map data from the deal into the task, such as its name, so the reminder says which opportunity to review.

  4. 04

    Test with Run once

    Click Run once, then edit a test deal in Copper. Each module shows a bubble with the bundles it received (a bundle is one item, here one deal). Open them and confirm the task appeared in Copper.

  5. 05

    Switch it on

    Look at the Scheduling clock on the first module, keep the setting that suits you, and turn the scenario on. From now on every deal change creates a follow-up task without anyone lifting a finger.

Triggers

What can start a Copper scenario?

7 modules start a scenario when something happens in Copper. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by Copper as soon as it happens.

Copper1Listen for Activity Events

Listen for Activity Events

Instant trigger

In MakeReceives notifications about activity creation/deletion/update.

Every call, note or meeting logged in Copper can start a scenario the moment it is created, edited or deleted. Make receives the activity as a bundle, ready to be copied into a report, a sheet or a team chat.

How it fires
Instant: Copper calls Make through a webhook as soon as it happens, with no polling interval to wait for.
When to use it
a sales manager wants each logged client call echoed to a shared sheet without asking reps to enter it twice.
Watch out
creations, edits and deletions all come through this single trigger, so test each kind with Run once before mapping anything.
Copper2Listen for Company Events

Listen for Company Events

Instant trigger

In MakeReceives notifications about company creation/deletion/update.

Keep other tools in step with your account list: this trigger tells Make whenever a company record in Copper is added, changed or removed, and hands over that company for the next modules to use.

How it fires
Instant: Copper calls Make through a webhook as soon as it happens.
When to use it
finance keeps customers in a separate billing tool and needs a new company in Copper to appear there too, spelled the same way.
Watch out
a scenario that updates the same company in Copper would wake this trigger again; send the change elsewhere rather than back into Copper.
Copper3Listen for Lead Events

Listen for Lead Events

Instant trigger

In MakeReceives notifications about lead creation/deletion/update.

New prospects get attention faster when Make hears about them straight away. This trigger reacts when a lead is created, edited or deleted in Copper and passes the lead to your scenario.

How it fires
Instant: Copper calls Make through a webhook as soon as it happens.
When to use it
a lead captured at a trade show lands in Copper and you want a welcome email or a chat alert to the right rep right after.
Watch out
converting that lead with Convert Lead in the same scenario changes it, which can fire the trigger a second time; keep conversion in a separate flow.
Copper4Listen for Opportunity Events

Listen for Opportunity Events

Instant trigger

In MakeReceives notifications about opportunity creation/deletion/update.

Deals are where revenue moves, and this trigger lets Make follow them. It fires when an opportunity is opened, edited or removed in Copper, and the deal travels on as a bundle to your next steps.

How it fires
Instant: Copper calls Make through a webhook as soon as it happens.
When to use it
the owner of a deal should receive a review task, or the delivery team a heads-up, whenever a deal changes.
Watch out
any edit counts, including small ones, so expect more runs than won deals and account for the operations they consume.
Copper5Listen for Person Events

Listen for Person Events

Instant trigger

In MakeReceives notifications about person creation/deletion/update.

People records hold your contacts, and this trigger alerts Make each time one is added, edited or deleted in Copper. The person arrives as a bundle that later modules can copy, enrich or file elsewhere.

How it fires
Instant: Copper calls Make through a webhook as soon as it happens.
When to use it
a marketing team keeps its newsletter list in another tool and wants each new Copper contact added there without an export.
Watch out
converted leads become people, so a conversion elsewhere can also start this scenario; test with Run once to see what arrives.
Copper6Listen for Project Events

Listen for Project Events

Instant trigger

In MakeReceives notifications about project creation/deletion/update.

After the sale, Copper projects track the work, and this trigger lets Make react when one is created, updated or deleted. The project comes through as a bundle you can pass to the tools your delivery team uses.

How it fires
Instant: Copper calls Make through a webhook as soon as it happens.
When to use it
an onboarding checklist or a shared folder should appear as soon as account managers open a project for a signed client.
Watch out
deletions fire too, so make sure a removed project does not create a fresh folder somewhere else by mistake.
Copper7Listen for Task Events

Listen for Task Events

Instant trigger

In MakeReceives notifications about task creation/deletion/update.

Tasks are the small promises made to clients, and this trigger tells Make whenever one is added, edited or removed in Copper, passing the task to the next module.

How it fires
Instant: Copper calls Make through a webhook as soon as it happens.
When to use it
a team lead wants a chat message each time a colleague assigns a callback, so nothing waits in a personal list.
Watch out
pairing this trigger with Create Task or Update Task in the same scenario can make it fire on its own output and loop; route tasks to another app instead.
Modules

What can Make do in Copper?

Copper gives you 47 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Copper1

Convert Lead

Action

In MakeConverts a selected lead to a person in the system (optionally assigns company and opportunity).

Turns a qualified lead into a person in Copper, and can attach a company and an opportunity along the way, so the prospect moves into your pipeline in one step instead of three manual edits.

When to use it
a lead books a demo and your sales team treats that as the moment it becomes a real contact with an open deal.
Watch out
the lead stops being a lead afterwards, so test on a dummy record before running it on live prospects.
Copper2

Create Activity

Action

In MakeCreates a new activity.

Logs an activity on the Copper timeline for you, which keeps the history of a client complete even when the exchange happened outside the CRM, in a form tool or a phone system.

When to use it
a support ticket is closed in another app and the account manager should see a trace of it next to the client record.
Watch out
map the record it belongs to from an earlier module, otherwise the activity has nothing to attach to.
Copper3

Create Company

Action

In MakeCreates a new company.

Adds a company record to Copper from data collected elsewhere, which saves your team from retyping account details that already exist in a signup form or an invoicing tool.

When to use it
a business signs up on your website and you want its organization in the CRM before a rep calls.
Watch out
to avoid a duplicate, run List Companies first and create only when the search comes back empty.
Copper4

Create Connection

Action

In MakeUse connect fields to create custom relationships between records. Common examples include keeping track of the relationship between parent/child companies, people to people referrals, assignments, managers, investors and more.

Records a custom relationship between two Copper records through connect fields, for links a plain contact card cannot show: a parent and a child company, a referral between two people, a manager, an investor.

When to use it
a new client arrives through a partner's referral and you want that link visible on both records.
Watch out
despite the name, this is not your Make connection to Copper; it creates a link between records inside the CRM.
Copper5

Create Lead

Action

In MakeCreates a new lead.

Drops a new prospect into Copper as a lead, so contact requests from ads, webinars or landing pages reach the sales team without anyone copying them over.

When to use it
someone fills in the contact form on your site and the details should become a lead that a rep can qualify.
Watch out
if the same person submits twice, you get two leads; search with List Leads first when repeat submissions are likely.
Copper6

Create Opportunity

Action

In MakeCreates a new opportunity.

Opens a deal in your Copper pipeline from outside the CRM, so a quote or a signed proposal becomes a trackable opportunity at once.

When to use it
a prospect accepts a quote in your proposal tool and the deal should appear in the pipeline with the right contact.
Watch out
an opportunity without a related person or company is hard to follow; link it afterwards with Relate Items or Relate Items (Advanced).
Copper7

Create Person

Action

In MakeCreates a new person.

Creates a contact directly as a person in Copper, skipping the lead stage for people you already know, such as a new colleague at a client or an attendee you met in person.

When to use it
a client adds a teammate to a shared project tool and that teammate should exist in your CRM too.
Watch out
use Create Lead instead when the contact still needs qualifying, or your contact list fills with cold prospects.
Copper8

Create Project

Action

In MakeCreates a new project.

Starts a project in Copper so delivery work is tracked in the same place as the sale that produced it.

When to use it
a deal is marked won and the onboarding team needs a project ready, without waiting for a sales rep to create it by hand.
Watch out
if Listen for Project Events runs in another scenario, each project created here will wake it too; plan for that before you switch both on.
Copper9

Create Task

Action

In MakeCreates a new task.

Adds a to-do in Copper for your team, which turns an event in any app into a clear next step on someone's list.

When to use it
a deal changes stage and its owner needs a reminder to call the client, or an invoice is overdue and the account manager should follow up.
Watch out
do not pair it with Listen for Task Events in the same flow: the new task fires the trigger, which creates another task.
Copper10

Get Activity

Action

In MakeGets details for a selected activity ID.

Fetches the full details of one Copper activity when you already hold its ID, so the next modules can read what was logged rather than a bare reference.

When to use it
a trigger or a list gives you only the activity's ID and you need its content to write a summary.
Watch out
it needs an exact ID; without one, reach for List Activities, which returns several activities at once.
Copper11

Get Company

Action

In MakeGets details for a selected company ID.

Reads one company record in Copper from its ID and hands every detail to the rest of the scenario, which is handy when a deal or a person only points at the company.

When to use it
an invoice needs the client's company details and the opportunity bundle holds only a reference to it.
Watch out
to look up a company by name you need List Companies instead; this module does not search.
Copper12

Get Lead

Action

In MakeGets details for a selected lead ID.

Pulls up a single lead from Copper by its ID, giving later modules the complete prospect record to score, route or copy.

When to use it
Listen for Lead Events fired and you want the freshest version of the lead before sending it to your email tool.
Watch out
map the ID from the trigger bundle rather than typing it, or the scenario will read the same lead on every run.
Copper13

Get Opportunity

Action

In MakeGets details for a selected opportunity ID.

Retrieves one deal with all its details from Copper by ID, useful whenever a later step needs more than the name, such as the details a trigger does not carry.

When to use it
a task or an activity refers to a deal and you want to post the deal details into a team channel.
Watch out
map the ID from an earlier module rather than typing it in, or the scenario will always read the same deal.
Copper14

Get Person

Action

In MakeGets details for a selected person ID.

Loads one contact's record from Copper by ID, so the scenario works with complete details instead of the partial data a trigger or a list may carry.

When to use it
before sending a contract, you want the client's latest details straight from the CRM.
Watch out
it reads a person, not a lead; for someone still in the lead stage, pick Get Lead.
Copper15

Get Project

Action

In MakeGets details for a selected project ID.

Opens a single Copper project by its ID and hands its details to the next module, which helps when a task or a trigger mentions the project without describing it.

When to use it
a task linked to a project changes and you want to tell the project's team in their own workspace.
Watch out
no ID, no result; List Projects is the module to start from when you only know the project exists.
Copper16

Get Task

Action

In MakeGets details for a selected task ID.

Reads one Copper task in full from its ID, so a scenario can check its details before deciding what to do next.

When to use it
Listen for Task Events signals a change and you want the task's current state before posting a reminder elsewhere.
Watch out
if the task was deleted in the meantime there is nothing left to fetch, so expect the run to stop on that bundle.
Copper17

Get User

Action

In MakeGets details for a selected user ID.

Looks up one member of your Copper account by user ID, which turns an owner or assignee reference into a real person you can notify.

When to use it
a deal changes hands and you want to message the new owner, but the deal bundle only carries that owner's ID.
Watch out
users are your teammates in Copper, not the contacts stored in it; for a client, use Get Person.
Copper18

Relate Items

Action

In MakeRelates People and Opportunities to each other.

Links a person and an opportunity in Copper, so the deal shows who is involved and the contact shows which deals concern them.

When to use it
Create Opportunity just opened a deal from a quote and the client who signed should appear on it.
Watch out
this version handles only people and opportunities; for companies, projects or tasks, choose Relate Items (Advanced).
Copper19

Relate Items (Advanced)

Action

In MakeRelates Leads, People, Companies, Opportunities, Projects, and Tasks to each other.

Ties any two Copper records together among leads, people, companies, opportunities, projects and tasks, which keeps the CRM connected when records arrive from different tools.

When to use it
a project created by Make should point to the company and the deal it came from.
Watch out
you need the IDs of both records, so place the module after the steps that created or found them.
Copper20

Remove Activity

Action

In MakeRemoves the activity with a given ID.

Deletes a logged activity from Copper by its ID, a way to clean timelines filled by an earlier automation or an import that went wrong.

When to use it
a test scenario logged fake calls on real clients and you want them gone.
Watch out
treat deletion as final; run the scenario once on a single test activity before letting it loop over a list.
Copper21

Remove Company

Action

In MakeRemoves the company with a given ID.

Deletes a company from Copper when you give it the record's ID, useful for clearing duplicates or accounts you no longer keep.

When to use it
a cleanup pass found two copies of the same client and you keep only the complete one.
Watch out
people and deals may point at that company, so check its related records before removing it, and test on a copy.
Copper22

Remove Lead

Action

In MakeRemoves the lead with a given ID.

Takes a lead out of Copper by ID, which keeps your prospect list free of spam submissions and test entries.

When to use it
a form tool flags a submission as spam after it already reached Copper as a lead.
Watch out
removing a lead also fires Listen for Lead Events if another scenario listens to it; make sure that scenario can handle a deletion.
Copper23

Remove Opportunity

Action

In MakeRemoves the opportunity with a given ID.

Deletes a deal from Copper by its ID, useful when a pipeline carries entries that were created twice or by mistake.

When to use it
an automation opened the same opportunity from two sources and only one should stay.
Watch out
a lost deal is still history; if you want to keep a trace, update it with Update Opportunity rather than deleting it.
Copper24

Remove Opportunity from Person

Action

In MakeRemoves a related opportunity from a person.

Breaks the link between a person and a deal without deleting either of them, so the contact stays in Copper and the deal stays in the pipeline.

When to use it
a client contact leaves the buying committee and should no longer appear on that opportunity.
Watch out
pick this rather than Remove Opportunity when you only want to detach; the other module deletes the deal itself.
Copper25

Remove Person

Action

In MakeRemoves the person with a selected ID.

Erases a person from Copper using their ID, for example when a contact asks to be forgotten or turns out to be a duplicate.

When to use it
an unsubscribe or a deletion request in another tool should also clear the contact from the CRM.
Watch out
run it on one test contact first, because a wrong ID mapping removes the wrong person.
Copper26

Remove Project

Action

In MakeRemoves the project with a selected ID.

Removes a project from Copper by ID, handy when a deal falls through and the project opened for it has no reason to exist.

When to use it
a signed deal is cancelled and the onboarding project created by Make should disappear with it.
Watch out
tasks and records linked to the project may lose their context, so check the project is truly empty of useful work first.
Copper27

Remove Task

Action

In MakeRemoves the task with a selected ID.

Deletes a Copper task by its ID, which stops reminders that no longer make sense from cluttering your team's lists.

When to use it
a client pays an invoice and the follow-up task created for it can go.
Watch out
if a colleague already worked on the task, removing it erases that trace too, so agree with the team on which tasks the scenario may delete.
Copper28

Remove Webhook Subscription

Action

In MakeRemoves the webhook subscription with a selected ID.

Cancels one webhook subscription in Copper from its ID, the plumbing that lets Copper call an outside address when records change.

When to use it
you are tidying up after old tests and want Copper to stop calling addresses nobody listens to anymore.
Watch out
the instant triggers on this page rely on webhooks, so make sure the ID you remove does not belong to a scenario still in use.
Copper29

Update Company

Action

In MakeUpdates a selected company.

Changes an existing company in Copper, so the account card stays current when details are corrected in another system.

When to use it
finance updates a client's billing details in the invoicing tool and sales should see the same thing in the CRM.
Watch out
if Listen for Company Events feeds this scenario, updating the same company fires the trigger again and can loop.
Copper30

Update Lead

Action

In MakeUpdates a selected lead.

Edits a lead already in Copper, for instance to add what you learned about the prospect since the first contact.

When to use it
the prospect answers a qualification form and the answers should land on the existing lead instead of a new one.
Watch out
you need the lead's ID; find it with List Leads when all you have is the form data.
Copper31

Update Opportunity

Action

In MakeUpdates a selected opportunity.

Modifies a deal in your Copper pipeline, which lets other tools move it forward without a rep opening the CRM.

When to use it
a contract gets signed in your e-signature tool and the matching opportunity should reflect it at once.
Watch out
a scenario started by Listen for Opportunity Events should not update that same deal, or each update restarts the run.
Copper32

Update Person

Action

In MakeUpdates a selected person.

Refreshes a contact in Copper with new details, keeping your address book accurate without anyone typing corrections twice.

When to use it
a client changes jobs, updates a profile in your customer portal, and the CRM should follow.
Watch out
make sure the ID points at the right person; searching with List People by the data you have is safer than guessing.
Copper33

Update Project

Action

In MakeUpdates a selected project.

Edits a Copper project so its details match what happens in your delivery tools.

When to use it
the last milestone is ticked in your project management app and the Copper project should show the work as done.
Watch out
a scenario listening to project events will receive this update too; keep the two scenarios from feeding each other.
Copper34

Update Task

Action

In MakeUpdates a selected task.

Modifies a task in Copper, for example to reflect work finished in another tool.

When to use it
a callback booked through your scheduling tool happens and the matching Copper task should close itself.
Watch out
started from Listen for Task Events, updating the same task fires the trigger again; send the update from a separate scenario instead.
Copper35

List Activities

Search

In MakeLists all activities related to a connected account.

Returns the activities visible to your connected Copper account, each one as a separate bundle, so you can report on calls and notes across the whole team.

When to use it
you want a sheet with every logged activity to review how clients were contacted.
Watch out
each activity returned counts as its own bundle for the modules after it, so a long list uses many operations.
Copper36

List Companies

Search

In MakeLists all companies related to a connected account.

Brings back the companies from your Copper account, zero, one or many, ready to check, copy or compare with another tool.

When to use it
before Create Company, to see whether the organization already exists and avoid a duplicate.
Watch out
an empty result is normal and does not stop the run on its own; decide what the scenario does when nothing comes back.
Copper37

List Company's Activities

Search

In MakeLists all activities for a selected company.

Gathers the activities of one chosen company, giving you its full contact history in a single step instead of scrolling the Copper timeline.

When to use it
ahead of a renewal, you want every call and meeting with that client sent to the account manager.
Watch out
you must say which company; map its ID from Get Company or List Companies placed earlier in the flow.
Copper38

List Leads

Search

In MakeLists all leads related to a connected account.

Lists the leads in your Copper account, each as its own bundle, so you can sort, check or sync your prospect pool with another tool.

When to use it
a form submission arrives and you want to know if the person is already a lead before creating one.
Watch out
modules placed after it run once per lead returned, which adds up quickly on a large prospect list.
Copper39

List Lead's Activities

Search

In MakeLists all activities related to a connected account.

Collects activities tied to leads, so you can see how much follow-up a prospect received before anyone decides to convert or drop it.

When to use it
before Convert Lead, you want the call and email history attached to the qualification note.
Watch out
the directory describes it in broad terms, so click Run once and check which activities actually come back before building on it.
Copper40

List Opportunities

Search

In MakeLists all opportunities related to a connected account.

Returns the deals in your Copper account as separate bundles, a starting point for a pipeline report or a sync with a forecasting sheet.

When to use it
management wants a spreadsheet of open deals built from the CRM, not typed by hand.
Watch out
the Free plan caps a run at 5 minutes, so a large pipeline processed deal by deal may need a paid plan.
Copper41

List People

Search

In MakeLists all people related to a connected account.

Pulls every person saved in the Copper account behind your connection, so the next modules receive one bundle per contact.

When to use it
your whole contact base needs the same treatment, such as a copy of each person in an Airtable table; for a single known contact, Get Person is lighter.
Watch out
every module placed after it runs once per person, and each run is one operation counted on your Make plan.
Copper42

List Person's Activities

Search

In MakeLists all activities of a selected person.

Fetches the activity history of one chosen person in Copper, so a later module can read what already happened with that contact before acting.

When to use it
right after a person trigger or Get Person, an account manager wants the calls and notes of that contact gathered in another tool.
Watch out
it needs the person's ID; map it from the previous module rather than typing it, or the scenario will always read the same contact.
Copper43

List Projects

Search

In MakeLists all projects related to a connected account.

Returns all the projects stored in the connected Copper account, one bundle each, giving a delivery team a feed it can push into a planning sheet or a report.

When to use it
a delivery lead needs a full export or a bulk check of projects; when a project trigger already hands you the right record, Get Project or the trigger output is enough.
Watch out
the search can return zero results, so test with Run once and see how the modules after it behave on an empty list.
Copper44

List Tasks

Search

In MakeLists all tasks related to a connected account.

Returns the tasks recorded in the connected Copper account, each task arriving as its own bundle ready to be copied into another tool or counted.

When to use it
a sales lead wants open follow-ups mirrored in a shared board; to react to a task the moment it changes, Listen for Task Events fits better.
Watch out
a long task list multiplies the operations of every downstream module, so test with Run once and keep the steps after it as few as possible.
Copper45

List Users

Search

In MakeLists all users related to a connected account.

Lists the users of the Copper account linked to Make, which is how a scenario learns who on the team can own a record, a task or an opportunity.

When to use it
you assign new leads to teammates and need the list of possible owners first.
Watch out
it lists the team, not your contacts; people and companies you sell to live in List People and List Companies.
Copper46

View Opportunities Related to Person

Search

In MakeShows all opportunities related to the person with a selected ID.

Shows the deals already tied to one person in Copper, so a scenario can tell whether a contact is a fresh prospect or someone with an open opportunity.

When to use it
a buyer comes back, and you check before Create Opportunity to avoid opening a second deal for the same buyer, or to route a returning customer to the right salesperson.
Watch out
it only covers opportunities; for every kind of linked record around that person, View Records Related to Person casts a wider net.
Copper47

View Records Related to Person

Search

In MakeShows all records related to the person with a selected ID.

Collects every record linked to a chosen person in Copper, which gives the full context around a contact in one step instead of chaining several searches.

When to use it
a support or customer success team needs to see all that surrounds a client before replying, whatever the record type.
Watch out
results mix record types, so check with Run once which bundles arrive before mapping them into a module that expects one kind.
Need help

Need help automating Copper with Make?

A person reads every message.

FAQ

Copper and Make: frequently asked questions

01Is the Copper Make integration free?
Yes, Copper is a standard app in Make, so you can use it on the Free plan. That plan gives you 2 active scenarios, a minimum of 15 minutes between scheduled runs, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) lower the interval to 1 minute, remove the cap on active scenarios and allow 40 minutes per run. Usage is counted in operations: each module run on one bundle is one operation.
02What do you need to connect Copper to Make?
A Copper account and a Make account. The Copper documentation lists no special prerequisite. In any Copper module, click Create a connection, give it a name if you want, then authorize Make on the page Copper opens or paste the key Copper gives you, depending on what the window asks for. Click Save and the connection is ready. Every Copper module in every scenario can reuse it, so there is no reason to connect the same account twice.
03Do Copper triggers in Make react in real time?
Yes. All 7 Copper triggers are instant: Copper calls Make through a webhook as soon as a record changes, instead of Make checking on a schedule. That covers activities, companies, leads, opportunities, people, projects and tasks. Each trigger receives creations, updates and deletions for its record type, so your scenario starts right after the change. Keep in mind that a scenario that edits the same record type in Copper can wake its own trigger again.
04What if the Copper module you need is missing in Make?
It depends on what is missing. The 54 modules cover creating, reading, updating, relating, listing and removing the main Copper records, and the documentation lists no limits to plan around. Copper has no Make an API Call module in Make, though, so an operation outside those 54 cannot be reached through this app. In that case, check whether another app in Make fits your need, or ask the team for help designing a workaround.
05Should you use Make or n8n for Copper?
It depends on the tool your team already runs. Copper is available in both. In Make, you get 54 modules, including 7 instant triggers, 34 actions and 13 searches, and it works from the Free plan, but there is no Make an API Call module for this app. On the n8n side, Copper exists as a node too. Compare the modules you need on each side and pick the tool where the rest of your automations already live, so everything stays in one place.