Resources · Make integration

Copilot Make integrationAutomate Copilot with Make.

Clients, files, contracts and invoices in Copilot can move on their own. The Copilot Make integration gives you 115 modules, including 46 triggers, to link Copilot with the rest of your tools. This guide connects your account and walks you through a first working scenario.

Try the Copilot integration on MakeSee the 115 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Copilot Make integration do for you?

The Copilot Make integration links your Copilot workspace to Make, a no-code tool where you build a scenario: an automation made of modules, each module being one brick that watches, reads or changes something in an app. Copilot brings 115 of them, spread across clients, companies, files, forms, contracts, messages, billing, notes and tasks.

Paperwork that follows the form. When a client finishes a form, Watch Completed Forms picks it up and Create a Task puts the follow-up on your team's list, so nobody has to scan responses by hand.

A welcome that sends itself. Watch Created Clients spots each new client at the next check, Create a Message Channel opens their conversation and Send a Message posts the first hello, so onboarding no longer depends on someone remembering it.

A cancellation nobody misses. When Watch Canceled Subscriptions finds a canceled plan, Create a Note records it on the client side and Create a Task hands the account manager a retention call.

Judging by their names, all 46 triggers are scheduled: Make asks Copilot for news on the scenario's clock instead of being told instantly. Check the clock badge on the module to confirm. If a Copilot endpoint has no ready module, Make an API call reaches it with the same connection. To weigh this setup against the other big tool, read n8n vs Make, check what each plan allows on Make pricing, and if you want a guided start, the Make training covers the editor step by step.

Connect

How do you connect Copilot to Make?

  1. 01

    Create an API key in Copilot

    Sign in to Copilot with an Admin account on a paid plan. In the left sidebar open Settings > API, then in the REST API section click Create key, give it a label and copy the value somewhere safe.

  2. 02

    Add a Copilot module in Make

    In your scenario, add any Copilot module and click Create a connection. The connection is your Copilot account linked to Make once; every Copilot module in your scenarios reuses it. The Connection name field is optional.

  3. 03

    Paste the key and save

    Paste the value into the API Key field and click Save. If Copilot asks you to authenticate and confirm access, accept. Make can now list and read what the key gives it.

First scenario

Your first scenario with Copilot

GoalWhen a client completes a form in Copilot, Make creates a task so your team follows up.

  1. 01

    Start a new scenario

    Open the Scenarios page in Make, create a new scenario and click the big + to place the first module on the canvas.

  2. 02

    Pick Watch Completed Forms

    Search for Copilot, choose Watch Completed Forms and select your connection with Create a connection or Add. Once connected, Make lists what it can read from your workspace.

  3. 03

    Add Create a Task

    Click the + on the right of the trigger and add Create a Task. Map data from the form bundle (one bundle is one item passed from a module to the next) into the task.

  4. 04

    Test with Run once

    Complete a test form in Copilot, then click Run once. Read the bundles each module received and check that the task shows up in Copilot.

  5. 05

    Schedule and switch it on

    Click the clock on the first module to set the schedule, every 15 minutes by default, then switch the scenario on. Each module run on one bundle counts as one operation on your Make plan.

Triggers

Copilot triggers in Make

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

Copilot1Watch Created Clients

Watch Created Clients

triggerIn the docs only

Every new client added to your Copilot workspace becomes the starting point of a scenario, with the client record handed to the next module as a bundle you can map anywhere.

How it fires
scheduled. Make checks Copilot on the scenario's schedule, every 15 minutes by default, so a new client arrives at the next check rather than the moment it is added.
When to use it
onboarding, when each newcomer should receive a welcome message and a first task without anyone clicking.
Copilot2Watch Activated Clients

Watch Activated Clients

triggerIn the docs only

This trigger waits for the moment a client moves to activated in Copilot and passes that client on, which is a better signal than creation when accounts are prepared ahead of time.

How it fires
scheduled; Make polls Copilot at the rhythm set on the clock badge of the first module, not on the spot.
When to use it
send the real kickoff (first invoice, first shared folder, a heads-up to the account manager) only once the client is actually in.
Copilot3Watch Updated Client Custom Fields

Watch Updated Client Custom Fields

triggerIn the docs only

Custom fields are where teams keep their own labels on a client. This trigger hands you the client whenever one of those custom fields changes, so your own classification can drive other tools.

How it fires
scheduled. Make looks at Copilot on the scenario's schedule and returns the changes it finds at that check.
When to use it
a tier or status you track in a custom field should update a CRM, a sheet or a Slack channel as soon as Make notices it.
Watch out
pair it with Retrieve Custom Field Options when you need the readable label of an option.
Copilot4Watch Updated Clients

Watch Updated Clients

triggerIn the docs only

Any edit to a client record in Copilot can restart your scenario with the fresh version of that client, which keeps copies of client data in other apps in step.

How it fires
scheduled; Make asks Copilot for recent edits each time the scenario runs on its clock.
When to use it
mirror client details into a CRM or a billing tool so your team stops fixing the same address in two places.
Watch out
if a later module updates the same client in Copilot, the scenario can see its own edit at the next check; add a filter to stop the echo.
Copilot5Watch Deleted Clients

Watch Deleted Clients

triggerIn the docs only

When a client is removed from Copilot, this trigger tells your scenario, so the cleanup in your other apps no longer depends on someone remembering it.

How it fires
scheduled. Make checks Copilot on the scenario's schedule and reports the removals it finds.
When to use it
archive the matching contact in a CRM, close a shared spreadsheet row or warn finance that a client left.
Watch out
the client no longer exists in Copilot at that point, so build the next modules on what the trigger hands over rather than on a Retrieve a Client call.
Copilot6Watch Created Companies

Watch Created Companies

triggerIn the docs only

Each company added to Copilot can open a scenario. This trigger picks it up and sends it down the scenario as a bundle ready to map.

How it fires
scheduled; the check happens at the interval set on the first module, 15 minutes by default on a fresh scenario.
When to use it
open an account in your CRM or accounting tool the day a new organization joins, before its first client is even invited.
Copilot7Watch Deleted Companies

Watch Deleted Companies

triggerIn the docs only

Removing a company in Copilot can ripple through the rest of your stack thanks to this trigger, which reports each deleted company to the scenario.

How it fires
scheduled. Make polls Copilot on the scenario's clock, never at the second the company disappears.
When to use it
close the related deal in a CRM, flag the account in a finance sheet or post a note in the team channel so nobody keeps working on it.
Watch out
the company is gone from Copilot, so a follow-up Retrieve a Company will not find it.
Copilot8Watch Updated Companies

Watch Updated Companies

triggerIn the docs only

Organization details change: a new name, a new owner, a new label. This trigger returns the updated company so the same change lands in every tool that holds a copy.

How it fires
scheduled; Make asks Copilot for edited companies each time the schedule ticks.
When to use it
keep the account record in your CRM or invoicing app aligned with Copilot without retyping.
Watch out
an Update a Company later in the same scenario creates a fresh edit; filter it out or the scenario keeps reacting to itself.
Copilot9Watch Created Folders

Watch Created Folders

triggerIn the docs only

Each new folder in Copilot's file area can open a scenario, which helps when folders mark the start of a project or a client file.

How it fires
scheduled. Make checks Copilot on the scenario's schedule, so the folder reaches Make at the next check.
When to use it
create the twin folder in a cloud drive, or warn the owner of the project that a space was opened for a client.
Copilot10Watch Updated Folders

Watch Updated Folders

triggerIn the docs only

This one hands you a folder whenever it changes in Copilot, which is handy when folder names or details carry meaning for your team, such as a stage or a year.

How it fires
scheduled; Make looks for edited folders on the scenario's clock badge.
When to use it
a renamed folder should rename its copy in another storage tool, or a status written on the folder should notify someone.
Watch out
test with Run once on a real rename to see exactly what the bundle carries before you map anything.
Copilot11Watch Deleted Folders

Watch Deleted Folders

triggerIn the docs only

A folder removed from Copilot shows up here, so storage elsewhere can follow and nobody keeps a stale copy of a client space.

How it fires
scheduled. Make checks Copilot on the rhythm of the scenario, not instantly.
When to use it
archive the mirrored folder in your drive, or log the removal in a sheet that tracks what was shared with each client.
Watch out
the folder and its content are no longer reachable in Copilot, so do not plan a download after this trigger.
Copilot12Watch Created Files

Watch Created Files

triggerIn the docs only

Whenever a file lands in Copilot, whether your team uploaded it or a client did, this trigger passes it to the scenario so the next steps happen without a manual check.

How it fires
scheduled; Make polls Copilot at the interval chosen on the first module, 15 minutes by default.
When to use it
copy client uploads into a drive, alert the account manager, or start a review task with Create a Task.
Watch out
on the Make Free plan files are capped at 5 MB, so large uploads need a paid plan to be moved.
Copilot13Watch Updated Files

Watch Updated Files

triggerIn the docs only

A file edited or replaced in Copilot comes back to you through this trigger, which keeps other copies of that document honest.

How it fires
scheduled. Make asks Copilot for changed files each time the scenario's schedule runs.
When to use it
push the new version of a deliverable into a shared drive, or tell the reviewer that the client sent a corrected document.
Watch out
several edits between two checks can arrive as several bundles, and each module run on each bundle is one operation.
Copilot14Watch Deleted Files

Watch Deleted Files

triggerIn the docs only

Here your scenario learns that a file was removed from Copilot, which matters when you keep an audit trail or mirrored storage.

How it fires
scheduled; Make reads Copilot at the scenario's pace, so the removal shows up at the next check.
When to use it
log who lost access to which document, or delete the mirrored copy in your drive to keep both sides equal.
Watch out
Download a File will not work on a file that no longer exists, so keep the next modules on the data the trigger returns.
Copilot18Watch Completed Forms

Watch Completed Forms

triggerIn the docs only

A form completed by a client is often the start of real work. This trigger catches each completed form and turns the answers into a bundle the rest of the scenario can use.

How it fires
scheduled; Make checks Copilot on the scenario's clock, 15 minutes by default on a new scenario.
When to use it
create a task for the team, copy the answers into a sheet or a CRM, or send the client a message confirming receipt.
Watch out
on the Free plan the shortest interval between two checks is 15 minutes.
Copilot19Watch Signed Contracts

Watch Signed Contracts

triggerIn the docs only

The signature on a contract usually unlocks the next step of an engagement. This trigger hands each newly signed contract to your scenario so that step runs by itself.

How it fires
scheduled. Make polls Copilot at the schedule set on the first module, so the signature appears at the next check.
When to use it
create the first invoice with Create an Invoice, open a project folder, or let sales know the deal is closed.
Copilot20Watch Requested Contracts

Watch Requested Contracts

triggerIn the docs only

This trigger picks up contracts that were sent out for signature, which lets you track what is waiting on the client side.

How it fires
scheduled; Make checks Copilot on the rhythm of the scenario and returns the requests found.
When to use it
log every request in a pipeline sheet, or create a reminder task for the account manager so pending signatures do not slip.
Watch out
combine it with Watch Signed Contracts in another scenario to see both ends of the signature process.
Copilot21Watch Created Message Channels

Watch Created Message Channels

triggerIn the docs only

Each new message channel opened in Copilot can start a scenario. This trigger reports the channel to your scenario the next time Make checks.

How it fires
scheduled. Make asks Copilot for new channels on the scenario's clock, 15 minutes by default.
When to use it
send a first automatic greeting with Send a Message, or record the new conversation in the account's CRM record.
Watch out
channels your own scenario opens with Create a Message Channel come back here too.
Copilot22Watch Deleted Message Chanels

Watch Deleted Message Chanels

triggerIn the docs only

When a conversation channel is removed in Copilot, this trigger lets your other tools know. The misspelled name is how Make displays the module, so search for it as written.

How it fires
scheduled; Make polls Copilot at the interval set on the first module.
When to use it
close the related ticket in a helpdesk, or note in a CRM that the client conversation ended.
Watch out
the channel is gone, so Retrieve a Message Channel will return nothing for it.
Copilot23Watch Sent Messages

Watch Sent Messages

triggerIn the docs only

Each message sent in a Copilot channel can feed a scenario through this trigger, which makes client conversations visible to tools your team already watches.

How it fires
scheduled. Make checks Copilot on the scenario's schedule, so messages arrive in batches at each check rather than one by one live.
When to use it
forward client messages to Slack or email for people who rarely open Copilot.
Watch out
a busy channel means many bundles, and every module run on each bundle counts as an operation.
Copilot24Watch Created Internal Users

Watch Created Internal Users

triggerIn the docs only

This trigger watches the internal users of your Copilot workspace, the accounts on your team's side, and reports every new teammate so the rest of your onboarding can follow.

How it fires
scheduled; Make reads Copilot at the scenario's pace, set on the clock badge of the first module.
When to use it
add the new colleague to an HR sheet, a project tool or a team channel once Make spots their new Copilot seat.
Copilot25Watch Deleted Internal Users

Watch Deleted Internal Users

triggerIn the docs only

Offboarding is easy to forget in half your tools. This trigger tells your scenario when a team member is removed from Copilot so the other accesses can be revoked too.

How it fires
scheduled. Make polls Copilot on the scenario's clock, not at the moment of removal.
When to use it
alert the admin in charge of accesses, or log the departure in the team roster.
Watch out
the user no longer exists in Copilot, so Retrieve an Internal User will not bring them back.
Copilot26Watch Paid Invoices

Watch Paid Invoices

triggerIn the docs only

A paid invoice is the signal accounting waits for. This trigger hands each invoice marked paid in Copilot to your scenario so bookkeeping and thank-you notes follow on their own.

How it fires
scheduled; Make checks Copilot on the scenario's schedule, 15 minutes by default.
When to use it
record the payment in an accounting sheet, thank the client with Send a Message, or unlock the next deliverable.
Watch out
each invoice is its own bundle, so a busy billing desk costs more operations.
Copilot27Watch Created Invoices

Watch Created Invoices

triggerIn the docs only

Every invoice drafted in Copilot can be copied, logged or announced through this trigger, before the client has even seen it.

How it fires
scheduled. Make asks Copilot for new invoices each time the schedule on the first module comes round.
When to use it
keep a live register of invoices in a spreadsheet, or ping finance so someone reviews the draft.
Watch out
created does not mean sent; use Watch Sent Invoices if the client must already have it.
Copilot28Watch Voided Invoices

Watch Voided Invoices

triggerIn the docs only

This trigger reports each invoice voided in Copilot, which is exactly what your books need to know to cancel the matching entry.

How it fires
scheduled; Make polls Copilot at the scenario's interval, so the void appears at the next check.
When to use it
mark the line as cancelled in an accounting sheet, or warn the account manager that a bill was withdrawn.
Watch out
a voided invoice still exists, unlike a deleted one; Watch Deleted Invoices covers the other case.
Copilot29Watch Deleted Invoices

Watch Deleted Invoices

triggerIn the docs only

Invoices removed from Copilot show up here, so a copy kept in another tool does not linger after the original is gone.

How it fires
scheduled. Make checks Copilot on the scenario's schedule and returns the deletions it finds.
When to use it
delete or flag the mirrored row in your finance sheet, and keep a log of who removed what.
Watch out
Retrieve an Invoice cannot fetch a deleted invoice, so use the data the trigger gives you.
Copilot30Watch Sent Invoices

Watch Sent Invoices

triggerIn the docs only

This trigger fires your scenario for each invoice sent to a client from Copilot, the point where a bill becomes something to chase.

How it fires
scheduled; Make asks Copilot for sent invoices on the rhythm of the scenario.
When to use it
start a follow-up task for unpaid bills, copy the invoice to your accounting tool, or notify the team channel.
Watch out
pair it with Watch Paid Invoices in a second scenario to close the loop once the money lands.
Copilot31Watch Updated Invoices

Watch Updated Invoices

triggerIn the docs only

Amounts, dates or lines on an invoice sometimes change after creation. This trigger returns the edited invoice so every copy stays right.

How it fires
scheduled. Make checks Copilot at the interval set on the first module, not the instant the invoice is edited.
When to use it
refresh the matching entry in a spreadsheet or accounting app, or tell finance that a figure moved.
Watch out
paid, voided and sent invoices have their own triggers, which are easier to filter than a generic update.
Copilot32Watch Created Subscriptions

Watch Created Subscriptions

triggerIn the docs only

Subscriptions bill a client on a recurring basis in Copilot. This trigger hands each new subscription to your scenario so revenue tracking starts with it.

How it fires
scheduled; Make polls Copilot on the scenario's clock, 15 minutes by default.
When to use it
add the subscription to a revenue sheet, alert the account owner, or send the client a welcome message about the plan.
Watch out
subscriptions your scenario creates with Create a Subscription also show up here.
Copilot33Watch Canceled Subscriptions

Watch Canceled Subscriptions

triggerIn the docs only

A canceled subscription is a moment worth reacting to. This trigger passes each cancellation from Copilot to your scenario so nobody learns about it late.

How it fires
scheduled. Make checks Copilot on the scenario's schedule and returns the cancellations found.
When to use it
create a retention task for the account manager, update the revenue sheet, or post the news in a sales channel.
Watch out
cancellations you trigger yourself with Cancel a Subscription will also come back here.
Copilot34Watch Successful Payments

Watch Successful Payments

triggerIn the docs only

Each payment that goes through in Copilot reaches your scenario here, one bundle per payment, ready for your books or a receipt.

How it fires
scheduled; Make reads Copilot at the interval chosen on the first module.
When to use it
write the payment into an accounting tool, or thank the client with a message in their Copilot channel.
Watch out
a payment and a paid invoice are separate events; pick the one that matches what your accountant tracks.
Copilot35Watch Failed Payments

Watch Failed Payments

triggerIn the docs only

A failed charge is money at risk, and this trigger surfaces each one from Copilot so someone acts before the client forgets.

How it fires
scheduled. Make polls Copilot on the scenario's schedule, so a failure shows up at the next check.
When to use it
send the client a polite message asking to update the payment method, and open a task for finance.
Watch out
the same client can fail more than once; add a filter or a note so they are not messaged twice for one issue.
Copilot36Watch Created Prices

Watch Created Prices

triggerIn the docs only

Prices attach an amount to a product in Copilot's billing. This trigger reports each new price so your catalog elsewhere stays in line.

How it fires
scheduled; Make asks Copilot for new prices each time the scenario's clock comes round.
When to use it
copy the new price into a sales sheet or quote tool, or tell the sales team a new rate is available.
Watch out
map the product along with the price, or the rate lands without context.
Copilot37Watch Created Products

Watch Created Products

triggerIn the docs only

Whenever a product is added to Copilot's billing catalog, this trigger hands it to the scenario, which is useful when the catalog lives in more than one tool.

How it fires
scheduled. Make checks Copilot on the scenario's schedule, 15 minutes by default.
When to use it
create the same product in an accounting or e-commerce app, or announce the new offer to the team.
Watch out
the price usually comes separately; Watch Created Prices covers it.
Copilot38Watch Updated Products

Watch Updated Products

triggerIn the docs only

This trigger returns products edited in Copilot, so a renamed or reworded offer does not stay outdated in your other systems.

How it fires
scheduled; Make polls Copilot on the rhythm of the scenario, not live.
When to use it
update the product in your accounting tool or website catalog, or log the change for the sales team.
Watch out
test on one real edit with Run once to see which details come through before you map them.
Copilot39Watch Created Notes

Watch Created Notes

triggerIn the docs only

Notes hold what your team learns about a client. This trigger carries each new note from Copilot into your scenario so the knowledge reaches other tools.

How it fires
scheduled. Make checks Copilot on the scenario's clock and returns notes added since.
When to use it
copy notes into the CRM record of the client, or post meeting notes into the account's team channel.
Watch out
notes written by Create a Note in another scenario will trigger this one as well.
Copilot40Watch Updated Notes

Watch Updated Notes

triggerIn the docs only

When a note in Copilot gets completed or corrected, this trigger brings the new text to your scenario so the copies stay current.

How it fires
scheduled; Make asks Copilot for edited notes at the interval on the first module.
When to use it
refresh the matching entry in a CRM or a shared document instead of piling up versions.
Watch out
if your scenario edits the note itself with Update a Note, filter out that change or it will loop back.
Copilot41Watch Deleted Notes

Watch Deleted Notes

triggerIn the docs only

Removed notes are reported here, which lets your records elsewhere drop what the team decided to erase in Copilot.

How it fires
scheduled. Make polls Copilot on the scenario's schedule and returns the deletions.
When to use it
delete the copied note from a CRM, or keep a log of removals for compliance.
Watch out
Retrieve a Note will find nothing once the note is gone, so use what the trigger returns.
Copilot42Watch Archived Tasks

Watch Archived Tasks

triggerIn the docs only

Archiving is how teams tidy the task list without deleting history. This trigger passes each archived task to your scenario so your reporting can follow.

How it fires
scheduled; Make checks Copilot on the scenario's clock, 15 minutes by default.
When to use it
move the task to a done column in a project tool, or record it in a sheet that tracks workload per client.
Watch out
Watch Completed Tasks is a separate trigger; archived does not mean done.
Copilot43Watch Completed Tasks

Watch Completed Tasks

triggerIn the docs only

A task ticked off in Copilot often means the next person can start. This trigger hands each completed task to the scenario so that handover happens without a message.

How it fires
scheduled. Make asks Copilot for completed tasks on the scenario's schedule.
When to use it
create the next task in a chain, tell the client that a step is done, or update a progress sheet.
Watch out
completed and archived are different states with separate triggers; choose the one your team really uses.
Copilot44Watch Created Tasks

Watch Created Tasks

triggerIn the docs only

Each new task in Copilot can start a scenario, useful when tasks also need to live in a project tool your team prefers.

How it fires
scheduled. Make looks for new tasks each time the scenario's clock comes round.
When to use it
copy the task into a project board, or alert the assignee in a chat app where they spend their day.
Watch out
tasks created by your own scenarios with Create a Task will also appear here; filter them if you only want human ones.
Copilot45Watch Updated Tasks

Watch Updated Tasks

triggerIn the docs only

This trigger hands you a task whenever it changes in Copilot, so a new due date or a new owner does not go unnoticed in other tools.

How it fires
scheduled. Make checks Copilot on the rhythm of the scenario, not the second the task is edited.
When to use it
keep a task mirrored in a project board aligned with Copilot.
Watch out
an Update a Task later in the same scenario creates another edit; add a filter so the scenario does not react to itself.
Copilot46Watch Deleted Tasks

Watch Deleted Tasks

triggerIn the docs only

When a task is removed from Copilot, this trigger reports it so copies in other tools can go too, and nobody works on a task that no longer exists.

How it fires
scheduled; Make polls Copilot on the scenario's schedule and returns what was deleted.
When to use it
delete the matching card in a project tool, or log the removal in a workload sheet.
Watch out
Retrieve a Task will not find a deleted task, so rely on the trigger's bundle.
Modules

What the Copilot modules can do

Copilot gives you 69 modules in 13 groups. For each one: what it does for you, when to reach for it, and what to watch out for.

Clients

6 modules
Copilot1

List Clients

SearchIn the docs only

Pulls your Copilot clients into the scenario, one bundle per client, so you can loop over the whole base or a filtered part of it.

When to use it
when you need to act on many clients at once, such as exporting them to a sheet or checking each one against a CRM.
Watch out
a search can return zero, one or many bundles, and every module after it runs once per client, which adds operations fast.
Copilot2

Create a Client

ActionIn the docs only

Adds a new client to Copilot from data gathered anywhere else, so a signup or a won deal becomes a client account without retyping.

When to use it
after a form in another app, a won deal in your CRM or a paid order in your store, to open the Copilot account right away.
Watch out
run a List Clients search first if the same person may already exist, to avoid duplicates.
Copilot3

Retrieve a Client

ActionIn the docs only

Fetches one specific client from Copilot with all the details the API returns, handy when an earlier module only gave you an ID.

When to use it
after a trigger on invoices, tasks or files, to get the full client record before writing to another tool.
Watch out
you need the client's identifier from a previous module; map it rather than typing it by hand.
Copilot4

Delete a Client

ActionIn the docs only

Removes a client from Copilot as part of a scenario, which lets offboarding in another tool clean up the Copilot side too.

When to use it
when a contract ends in your CRM and the client account should no longer exist in Copilot.
Watch out
the Copilot module list has no restore counterpart, so add a filter before this module and test it on a dummy client first.
Copilot5

Update a Client

ActionIn the docs only

Changes an existing client in Copilot with data mapped from earlier modules, keeping Copilot in line with your source of truth.

When to use it
when details change in your CRM or billing tool and Copilot should show the same thing to your team.
Watch out
if the same scenario is started by Watch Updated Clients, filter your own edits or the scenario will react to them.
Copilot6

Retrieve Custom Field Options

ActionIn the docs only

Returns the options defined for your Copilot custom fields, so the scenario can work with the labels your team chose rather than raw values.

When to use it
before writing a custom field on a client, or after Watch Updated Client Custom Fields, to turn a stored option into a readable label.
Watch out
run it once with Run once and read the bundle to see how the options are structured before mapping.

Companies

5 modules
Copilot7

List Companies

SearchIn the docs only

Brings every company from Copilot into the scenario, one bundle each, to report on your accounts or match them with another system.

When to use it
for a sync where you compare Copilot companies with your CRM accounts and fix the gaps.
Watch out
every module placed after it runs once per company returned, so filter early to save operations.
Copilot8

Create a Company

ActionIn the docs only

Opens a new company in Copilot so clients from the same organization can be grouped from the start, fed by data from another app.

When to use it
when a new account is created in your CRM and the matching organization should exist in Copilot before its people are invited.
Watch out
search with List Companies first if the organization may already be there.
Copilot9

Retrieve a Company

ActionIn the docs only

Gets the full record of one Copilot company by its identifier, giving later modules the details a trigger alone may not carry.

When to use it
after a client or invoice trigger, when you need the organization's details to write a document or a CRM entry.
Watch out
map the company ID from an earlier bundle; a typed ID breaks as soon as you test with another record.
Copilot10

Update a Company

ActionIn the docs only

Edits a company in Copilot from mapped data, so organization details stay consistent across your tools without manual copy.

When to use it
when an account changes name or owner in your CRM and Copilot should follow.
Watch out
a Watch Updated Companies scenario will see this edit too; a filter keeps the two from ping-ponging.
Copilot11

Delete a Company

ActionIn the docs only

Deletes a company from Copilot inside a scenario, useful when an organization is closed in the tool you treat as the reference.

When to use it
at the end of an offboarding flow, once invoices and files have been handled.
Watch out
nothing in the module list brings a company back, so test on a sample and guard the module with a filter.

FIles

11 modules
Copilot12

List Files

SearchIn the docs only

Returns the files stored in Copilot as separate bundles, which is the way to review or export many documents in one scenario.

When to use it
to back up client documents into a drive, or to check which files exist before creating a new one.
Watch out
each file becomes one bundle, and each later module runs on every bundle, so a download step multiplies operations.
Copilot13

List File Channels

SearchIn the docs only

Lists the file channels of your Copilot workspace, one bundle per channel, so the scenario can pick where a document should go.

When to use it
when you need to find the right channel before uploading, or to audit which clients have a file space.
Watch out
the result can be empty, so add a filter or a router for the case where no channel matches.
Copilot14

Create a File Channel

ActionIn the docs only

Creates a new file channel in Copilot, giving a client or company a dedicated place for documents straight from your scenario.

When to use it
right after Create a Client or Watch Signed Contracts, so the file space is ready when work starts.
Watch out
check with List File Channels first if the client may already have one, or you end up with two spaces.
Copilot15

Retrieve a File Channel

ActionIn the docs only

Loads one file channel by its identifier, so later modules know who it belongs to and can act on it.

When to use it
after a file trigger, to find out which client space the file sits in before notifying the right person.
Watch out
the channel ID has to come from an earlier bundle; test with Run once to see where it appears.
Copilot16

Retrieve a File

ActionIn the docs only

Gets the details of one file in Copilot, which tells the scenario what the file is before you decide to download, move or announce it.

When to use it
after Watch Created Files or List Files, when you need more about a document than the trigger gave.
Watch out
this reads the file's record; to get the content itself, use Download a File.
Copilot17

Download a File

ActionIn the docs only

Fetches the actual content of a Copilot file into the scenario, so another module can upload it to a drive, attach it to an email or archive it.

When to use it
to copy client uploads into cloud storage or send a document through another app.
Watch out
the Make Free plan handles files up to 5 MB and 512 MB of transfer; bigger documents need a paid plan.
Copilot18

Retrieve a Download URL

ActionIn the docs only

Returns a download address for a Copilot file instead of the file itself, which is lighter when the next tool only needs a link.

When to use it
when you post a document in a chat app or email and the recipient can fetch it from the link.
Watch out
prefer it over Download a File when the next app only needs a link, which also keeps large documents out of your Make transfer.
Copilot19

Create a File

ActionIn the docs only

Puts a new file into Copilot from content produced or fetched earlier in the scenario, so documents reach the client space without a manual upload.

When to use it
to push a generated report, a signed PDF from another tool or an export into a client's file channel.
Watch out
on the Make Free plan a file cannot exceed 5 MB.
Copilot20

Create a Folder

ActionIn the docs only

Makes a new folder in Copilot's file area, giving structure to a client space from the moment the scenario opens it.

When to use it
when a contract is signed or a project starts, to prepare the folders the client and team will fill.
Watch out
run List Files first if the folder might exist, since two folders with the same name confuse everyone.
Copilot22

Delete a File

ActionIn the docs only

Removes a file from Copilot during a scenario, which keeps client spaces tidy when a document is replaced or expires.

When to use it
after moving the file to an archive, or when a newer version was uploaded with Create a File.
Watch out
the module list offers no way back, so download or archive the file first and test on a sample.

Forms

4 modules
Copilot23

List Forms

SearchIn the docs only

Returns the forms defined in your Copilot workspace, one bundle per form, which is how the scenario finds the right questionnaire to send.

When to use it
before Request a Form Response, to pick the form by name instead of hard-coding an identifier.
Watch out
add a filter after it so only the form you want goes on to the next module.
Copilot24

List Form Responses

SearchIn the docs only

Brings back the responses submitted to your Copilot forms, each as its own bundle, so the answers can be analyzed or stored elsewhere.

When to use it
for a catch-up export of past answers into a sheet, where Watch Completed Forms only sees new ones.
Watch out
many responses mean many bundles, and each downstream module counts an operation per response.
Copilot25

Retrieve a Form

ActionIn the docs only

Loads one Copilot form with its details, giving the scenario what it needs to label answers or reuse the form's name in a message.

When to use it
after Watch Completed Forms, when you want the form's title in the task or notification you create.
Watch out
map the form ID from the trigger bundle instead of copying it by hand.
Copilot26

Request a Form Response

ActionIn the docs only

Asks a client to fill in a Copilot form, so questionnaires go out as part of a flow rather than by memory.

When to use it
when a new client is activated or a contract is signed and you need their intake answers before work starts.
Watch out
use List Forms first to choose the right form, and combine it with Watch Completed Forms to act on the reply.

Contracts

5 modules
Copilot27

List Contract Templates

SearchIn the docs only

Returns the contract templates stored in Copilot, one bundle each, so a scenario can choose which agreement to send.

When to use it
before Send a Contract, to select the template by its name when you offer more than one type of agreement.
Watch out
filter the result down to a single template, or the next module runs once per template.
Copilot28

Retrieve a Contract Template

ActionIn the docs only

Gets one contract template from Copilot, which lets the scenario read its details before a contract goes out.

When to use it
when the next module needs the template's name or settings, for instance to log which agreement a client received.
Watch out
run it once with Run once to see what the template bundle contains before you rely on it.
Copilot29

List Contracts

SearchIn the docs only

Pulls the contracts in Copilot into your scenario, one bundle per contract, for reporting or a sync with sales tools.

When to use it
to rebuild a pipeline sheet with every contract, or to check which ones are still waiting on a signature.
Watch out
it returns everything it finds, so place a filter right after it to keep only the contracts you care about.
Copilot30

Retrieve a Contract

ActionIn the docs only

Fetches a single contract with its details, turning an identifier from a trigger into something you can write into other apps.

When to use it
after Watch Signed Contracts, when your CRM or accounting tool needs more than the trigger delivered.
Watch out
map the contract ID from an earlier module; test with a real signed contract first.
Copilot31

Send a Contract

ActionIn the docs only

Sends a contract from Copilot to a client as a step of your scenario, so an agreement leaves the moment the deal is ready.

When to use it
when a deal is won in your CRM or an intake form is complete and the next move is a signature.
Watch out
test on your own client record first; a contract sent to a real client cannot be pulled back from the scenario.

Messages

5 modules
Copilot32

List Messages

SearchIn the docs only

Returns the messages of Copilot conversations as individual bundles, useful to archive or review exchanges with clients.

When to use it
for a one-off export of a conversation into a document or a CRM timeline.
Watch out
a long conversation means many bundles, and every following module runs on each one.
Copilot33

List Message Channels

SearchIn the docs only

Lists the message channels in Copilot, which is how the scenario finds the conversation of a given client before posting.

When to use it
ahead of Send a Message, when you know the client but not the channel.
Watch out
no match returns zero bundles and the scenario stops there; plan a Create a Message Channel branch if needed.
Copilot34

Retrieve a Message Channel

ActionIn the docs only

Opens one message channel by its identifier so the scenario knows who takes part before it posts or logs anything.

When to use it
after Watch Sent Messages, to find out which client a message belongs to before forwarding it.
Watch out
the channel must still exist; after a deletion trigger this module finds nothing.
Copilot35

Create a Message Channel

ActionIn the docs only

Opens a new conversation channel in Copilot, so a client has a place to talk with your team as soon as the scenario decides it.

When to use it
right after Create a Client, or when a project starts and needs its own thread.
Watch out
check with List Message Channels first so the same client does not end up with two conversations.
Copilot36

Send a Message

ActionIn the docs only

Posts a message into a Copilot channel from your scenario, so clients hear about invoices, files or next steps without anyone typing it.

When to use it
to confirm a received form, thank a client for a payment or warn them about a failed charge.
Watch out
run a test with Run once in a channel of your own before letting it write to real clients.

Internal users

2 modules
Copilot37

List Internal Users

SearchIn the docs only

Returns your team members in Copilot, one bundle per person, so the scenario can assign work or check who has a seat.

When to use it
to pick an owner for a new task, or to compare Copilot seats with your HR list.
Watch out
filter to the person you need, otherwise the next module runs once per teammate.
Copilot38

Retrieve an Internal User

ActionIn the docs only

Fetches one teammate's record from Copilot, which gives the scenario a name or contact detail to use in a notification.

When to use it
when a task or message carries only the user ID and you want to address that person in another app.
Watch out
after Watch Deleted Internal Users the person is gone and this module returns nothing.

Workspaces

1 module
Copilot39

Retrieve Workspace

ActionIn the docs only

Reads the details of your Copilot workspace itself, the one tied to the API key in your connection.

When to use it
to check which workspace a connection points to, or to put the workspace's details in a report or a message.
Watch out
it is a quick way to confirm, with Run once, that a new connection works before you build further.

Apps

3 modules
Copilot40

List App Installs

SearchIn the docs only

Lists the apps installed in your Copilot workspace, one bundle per app, so the scenario can see which extensions are active.

When to use it
for an admin audit of the workspace, or before List App Connections when you need the right app first.
Watch out
this reads settings rather than client data; keep such admin scenarios apart from client-facing flows.
Copilot41

List App Connections

SearchIn the docs only

Gives you the app connections recorded in your Copilot workspace, one bundle per connection, so a scenario can read them without opening Copilot's settings.

When to use it
pick it before Create an App Connection, to check what already exists and avoid a double.
Watch out
filter on the app you care about before Create an App Connection, or the next module runs once per connection returned.
Copilot42

Create an App Connection

ActionIn the docs only

Adds a new app connection in Copilot straight from your scenario, so setting up a client's access follows automatically from an event elsewhere.

When to use it
a new client arrives from another tool and should get the same app access every time, without anyone clicking through Copilot.
Watch out
run List App Connections first if the same event can fire twice, or you may end up with duplicates.

Billing

14 modules
Copilot43

List Invoices

SearchIn the docs only

Pulls the invoices of your Copilot workspace into Make as separate bundles, ready to be copied into a spreadsheet, an accounting tool or a report.

When to use it
you need a batch of invoices at once; for a single invoice whose ID you already hold, Retrieve an Invoice is lighter.
Watch out
if nothing matches, no bundle comes out and the scenario stops quietly; try Run once on an empty case so it does not surprise you later.
Copilot44

List Subscriptions

SearchIn the docs only

Brings back the subscriptions stored in Copilot, one bundle each, so recurring billing becomes visible outside Copilot.

When to use it
feeding a revenue sheet or a CRM with every active plan; to follow one subscription, Retrieve a Subscription does the job with fewer operations.
Watch out
a long list means many bundles, and each one triggers the next modules, so filter early to keep the operation count low.
Copilot45

List Payments

SearchIn the docs only

Returns the payments recorded in Copilot so a scenario can reconcile them with your bank export or your bookkeeping tool.

When to use it
checking a set of payments in one pass; to react when a payment lands, the trigger Watch Successful Payments fits better than a search.
Watch out
a search can return zero, one or several bundles (one item each), and every module placed after it runs once per bundle, so each one costs operations on your plan.
Copilot46

List Invoice Templates

SearchIn the docs only

Shows the invoice templates set up in Copilot, which helps you find the right template before an invoice is created by the scenario.

When to use it
building a scenario that picks a template depending on the client or the service sold.
Watch out
the result is a list of bundles; filter it before Create an Invoice so only one template reaches that module.
Copilot47

List Subscription Templates

SearchIn the docs only

Returns the subscription templates available in Copilot, so the scenario knows which recurring offers it can attach to a client.

When to use it
choosing a template on the fly before Create a Subscription, for example according to the plan a client picked in a form.
Watch out
keep a single template before Create a Subscription, or the client gets one subscription per template that comes through.
Copilot48

Create an Invoice

ActionIn the docs only

Issues an invoice in Copilot from data arriving in the scenario, so billing no longer waits for someone to copy amounts by hand.

When to use it
a job is marked as finished in another tool and the client should be billed through Copilot.
Watch out
test with Run once on a test client first: every run of this module creates a real invoice.
Copilot49

Create a Subscription

ActionIn the docs only

Starts a subscription for a client in Copilot from your scenario, which turns a signed deal elsewhere into recurring billing without a manual step.

When to use it
a contract is signed or a form is completed and the client should be put on a plan right away.
Watch out
make sure the client already exists in Copilot, or create it earlier in the scenario with Create a Client.
Copilot50

Retrieve an Invoice

ActionIn the docs only

Fetches one invoice from Copilot by its ID and hands its details to the next modules, for a reminder email or a line in a ledger.

When to use it
a trigger or a search already gave you the invoice ID and you need the full record behind it.
Watch out
the module works on one invoice only; for several, use List Invoices.
Copilot51

Retrieve a Subscription

ActionIn the docs only

Reads a single Copilot subscription and passes its details on, so the scenario can decide what to do next based on its current state.

When to use it
after Watch Canceled Subscriptions, to get the whole record before telling your team or updating a CRM.
Watch out
it needs the subscription ID, usually mapped from a previous module.
Copilot52

Cancel a Subscription

ActionIn the docs only

Stops a client's subscription in Copilot from Make, so an offboarding decided elsewhere also ends the billing.

When to use it
a client leaves in your CRM or support tool and the recurring plan in Copilot should stop as well.
Watch out
add a filter before this module; a wrong ID mapped here cancels the wrong client's plan.
Copilot53

List Products

SearchIn the docs only

Lists the products defined in Copilot, one bundle per product, which is handy to keep a catalogue in sync with another tool.

When to use it
mirroring your Copilot offer in a spreadsheet or a website; for one product only, Retrieve a Product is the lighter choice.
Watch out
filter before any module that creates something elsewhere, or each product returned creates its own copy there.
Copilot54

Retrieve a Product

ActionIn the docs only

Opens one Copilot product by its ID and makes its details available to the rest of the scenario, such as for a quote or a notification.

When to use it
right after Watch Updated Products, to read the full product before pushing the change to another tool.
Watch out
it reads a single product; the ID has to come from an earlier module.
Copilot55

List Prices

SearchIn the docs only

Returns the prices set in Copilot as separate bundles, so you can compare them, export them or check them against another price list.

When to use it
auditing or copying all prices at once; when only one matters, Retrieve a Price avoids the extra operations.
Watch out
each price is its own bundle; map the product with it so every exported line keeps its context.
Copilot56

Retrieve a Price

ActionIn the docs only

Reads one price from Copilot and hands it to the next module, useful when a quote or an invoice line elsewhere must match it.

When to use it
after Watch Created Prices, to get the complete price record before sending it to a sales or finance tool.
Watch out
the module needs the price ID; map it from the trigger or a search.

Notes

5 modules
Copilot57

Create a Note

ActionIn the docs only

Writes a note in Copilot from any event of your scenario, so the context of a call, a ticket or a form ends up where your team looks.

When to use it
a support ticket closes or a form answer arrives and the client's history in Copilot should record it.
Watch out
keep the text short and mapped from clear fields; a note full of raw data helps nobody.
Copilot58

Retrieve a Note

ActionIn the docs only

Gets one Copilot note by its ID with its content, so the scenario can copy it, summarise it or send it to someone.

When to use it
after Watch Updated Notes, to read the latest version before posting it to a team chat.
Watch out
it handles one note; for several, List Notes is the module to use.
Copilot59

List Notes

SearchIn the docs only

Brings back the notes saved in Copilot, one bundle each, to archive them or move them into another knowledge tool.

When to use it
exporting or reviewing many notes in one run rather than following them one by one.
Watch out
a large archive of notes means many bundles; run it once with Run once to see the volume before you switch the scenario on.
Copilot60

Update a Note

ActionIn the docs only

Changes an existing note in Copilot, so a note created earlier can be completed as new information comes in.

When to use it
a follow up happens in another tool and the related note in Copilot should reflect it instead of adding a second note.
Watch out
the note ID must be known; store it when the note is created, or find it with List Notes.
Copilot61

Delete a Note

ActionIn the docs only

Removes a note from Copilot through the scenario, handy to clean up notes that were only meant as temporary reminders.

When to use it
a matching item is closed elsewhere and its note in Copilot no longer serves any purpose.
Watch out
test on a note you do not need: once the module runs, the note is gone from Copilot.

Tasks

7 modules
Copilot62

List Tasks

SearchIn the docs only

Returns the tasks of your Copilot workspace, one bundle per task, so you can mirror them in a project tool or a shared sheet.

When to use it
reviewing or exporting a set of tasks; to follow each new one as it appears, the trigger Watch Created Tasks is the better fit.
Watch out
on a busy workspace this returns a lot of tasks; add a filter right after it so only the ones you need go on and cost operations.
Copilot63

Create a Task

ActionIn the docs only

Adds a task in Copilot when something happens elsewhere, so nobody has to remember to open Copilot and type it in.

When to use it
a client pays, signs or sends a form and a follow up action should land in Copilot at once.
Watch out
if the same event may reach the scenario twice, check with List Tasks first to avoid duplicate tasks.
Copilot64

Retrieve a Task

ActionIn the docs only

Pulls one Copilot task by its ID and gives its details to the following modules, for a reminder or a status update in another tool.

When to use it
after Watch Completed Tasks, to read the full task before notifying the client or your team.
Watch out
it works on one task at a time; the ID comes from a trigger or a search.
Copilot65

Delete a Task

ActionIn the docs only

Erases a task in Copilot from the scenario, which keeps the task list clean when the work was cancelled somewhere else.

When to use it
a project or a request is dropped in another tool and its task in Copilot should disappear too.
Watch out
put a filter before it and test with Run once on a dummy task; a deleted task does not come back.
Copilot66

Update a Task

ActionIn the docs only

Edits an existing Copilot task so its content follows what changes in your other tools, without a second task being created.

When to use it
a deadline or a detail moves in your project tool and the Copilot task should say the same.
Watch out
the task ID is required; keep it from Create a Task or find it with List Tasks.
Copilot67

List Task Templates

SearchIn the docs only

Shows the task templates saved in Copilot, which lets a scenario choose the right one before it creates work for a client.

When to use it
picking a template according to the service sold or the step a client reached.
Watch out
narrow it down to one template before Create a Task, or you get one task per template returned.
Copilot68

Retrieve a Task Template

ActionIn the docs only

Reads one Copilot task template by its ID and exposes its details, so the scenario can reuse them when it builds new tasks.

When to use it
you already know which template applies and need its content in the next modules.
Watch out
it needs the template ID, taken from List Task Templates or stored beforehand.

Other

1 module
Copilot69

Make an API call

ActionIn the docs only

Reaches any endpoint of the Copilot API with the same connection as the other modules, which covers what the ready made modules do not offer.

When to use it
a Copilot operation you need has no dedicated module in the list above.
Watch out
you write the request yourself, so keep the Copilot API documentation open while you set it up.
Need help

Need help automating Copilot with Make?

A person reads every message.

FAQ

Copilot and Make: frequent questions

01Is the Copilot Make integration free?
Yes, on the Make side. Copilot is a standard app, available from the Free plan, which allows 2 active scenarios, a minimum of 15 minutes between two scheduled runs, 5 minutes of execution per run and files up to 5 MB. Paid Make plans lower the interval to 1 minute and remove the cap on active scenarios. On the Copilot side, the connection needs a paid Copilot account with Admin access, so the integration is only free if you already have that Copilot plan.
02What do you need to connect Copilot to Make?
You need a paid Copilot account with Admin access and an API key. In Copilot, open Settings, then API, click Create key in the REST API section, name the key and copy it. In Make, add any Copilot module, click Create a connection, paste the value in the API Key field and click Save. If Copilot asks you to confirm access, accept. The same connection then serves every Copilot module in all your scenarios.
03Do Copilot triggers in Make fire instantly?
No, as far as their names tell. The 46 Copilot triggers are scheduled: Make checks Copilot at the interval set on the first module of the scenario, every 15 minutes by default. Look for the clock badge on the module to confirm. A change made just after a check waits for the next one. On a paid plan you can shorten the interval down to 1 minute. Plan your follow-ups with that gap in mind, and pick the interval that fits the work.
04What if a Copilot module is missing in Make?
It depends on what you need, but the Make an API call module covers most gaps. It calls any endpoint of the Copilot API with the connection you already set up, so you do not need a second key. Check first among the 115 existing modules, since list, retrieve, create, update and delete are covered for most objects. The Copilot documentation in Make gives no numbered limits, so the ones you know for sure are those of your Make plan.
05Should you use Make or n8n for Copilot?
It depends on the tool your team already runs. On Make, Copilot comes with 115 ready modules and a Make an API call module for the rest, all set up with a single API key. n8n often offers a node for the same app, so check whether one exists for Copilot and which objects it covers before choosing. Compare them on what matters to you: the modules you need, the way your team builds, and the plan each tool requires.
Same platform

Other docs you might need on this stack.

Browse all integrations