Resources · Make integration

Capsule CRM Make integrationAutomate Capsule CRM with Make.

Stop copying contacts, deals and tasks into Capsule by hand. The Capsule CRM Make integration gives you 78 modules, including 8 triggers, 45 actions and 25 searches. This guide shows sales and ops teams how to connect the account and ship a first scenario.

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Capsule CRM Make integration do?

The Capsule CRM Make integration links your Capsule account to Make, a no-code tool where you build a scenario: an automation made of modules, each one a single brick that watches, creates, updates or looks up a record. Once connected, Make can react to new parties, opportunities, cases and tasks, and write back into Capsule for you.

Follow up on every new deal. Watch new Opportunities spots each opportunity added to the pipeline, and Create a Task puts a call on the owner's list. Nobody has to remember to set a reminder.

Keep the whole client team on the record. When a form tells you the buyer's finance lead is joining, Add an Additional Party in Opportunity attaches that person to the deal, and Add an Additional Party in Case does the same on a project.

Log what happened elsewhere. Create an Entry writes a note on a contact, so an event from another tool leaves a trace in Capsule's history.

Where the list stops, Make an API Call reaches any endpoint of the Capsule API with the same connection. Make's help page for this app says its content is AI-generated, so check anything critical against Capsule's own docs. The same app often has an n8n node too; the n8n vs Make comparison helps you pick. New to the editor? The Make training covers the basics, and Make troubleshooting helps when a run fails.

Connect

How do you connect Capsule CRM to Make?

  1. 01

    Add a Capsule CRM module

    Log in to Make, open your scenario, add any Capsule CRM module and click Create a connection. You need an active Capsule account; the connection is your Capsule login linked to Make once, then reused by every Capsule module.

  2. 02

    Name the connection

    The Connection name field is optional, but a clear label such as the account owner's name saves confusion later, when several people or several Capsule accounts share the same Make account.

  3. 03

    Authorize the access

    Either paste the credentials you copied from Capsule or follow the on-screen instructions. Capsule accepts OAuth or a personal access token. For your own OAuth app, register it in Capsule with the callback URI https://www.integromat.com/oauth/cb/capsule-crm, then copy the Client ID and Client secret.

First scenario

Build your first scenario with Capsule CRM

GoalWhen a new opportunity lands in Capsule CRM, Make creates a follow-up task for it.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the big +. Search for Capsule CRM and pick Watch new Opportunities as the first module.

  2. 02

    Link your account

    Click Create a connection and authorize Capsule. From then on, Make can read your Capsule data and list the options it finds in each field.

  3. 03

    Add the task

    Click the + to the right of the trigger and add Create a Task. Map the opportunity's name from the first module into the task so the rep knows which deal it is about.

  4. 04

    Test with Run once

    Add a test opportunity in Capsule, then click Run once. Open the bubble above each module to read the bundle it received: one bundle is one item, here one opportunity.

  5. 05

    Schedule and switch on

    Watch new Opportunities is a scheduled trigger, so set the clock on it: a new scenario checks every 15 minutes by default. Then switch the scenario on and let it run.

Triggers

Capsule CRM triggers in Make

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

Capsule CRM1Watch new Cases

Watch new Cases

Scheduled trigger

In MakeChecks if a new case was created.

Every newly created case can start a scenario, so the setup work around a fresh project happens without someone remembering it. The module checks Capsule for cases that did not exist before and passes each one along as a bundle.

How it fires
scheduled. Make checks Capsule on the scenario's schedule, every 15 minutes by default, and never more often than that on the Free plan.
When to use it
a case opens after a signed quote, and you want a kickoff task and a message to the delivery team.
Watch out
it only reports creations; for edits or deletions on a case, Watch Projects is the module to pick.
Capsule CRM2Watch new Opportunities

Watch new Opportunities

Scheduled trigger

In MakeChecks if a new opportunity was created.

A new deal in your pipeline becomes the starting point of an automation, which is the easiest way to make sure no lead sits untouched. Make looks for opportunities that were just created and hands each one to the next module.

How it fires
scheduled, so Make checks Capsule on the scenario's schedule instead of hearing about the deal right away.
When to use it
you want a follow-up task, a Slack alert or a row in a reporting sheet each time a rep logs a deal.
Watch out
moving an opportunity through milestones is not a creation; for those changes, Watch Opportunities reacts instead.
Capsule CRM3Watch new Parties

Watch new Parties

Scheduled trigger

In MakeChecks if a new party was created.

Each person or organisation added to Capsule can be copied, welcomed or enriched elsewhere without a manual export. In Capsule, a party is either a person or an organisation, and this module picks up the new ones.

How it fires
scheduled. Make checks Capsule at the interval set on the scenario, 15 minutes by default, down to 1 minute on paid plans.
When to use it
a new contact should reach your mailing tool or your invoicing software, and a short wait is fine.
Watch out
the instant module Watch Parties has a near identical name. Check the badge before you build: a clock here, a lightning bolt there.
Capsule CRM4Watch new Tasks

Watch new Tasks

Scheduled trigger

In MakeChecks if a new task was created.

Tasks created in Capsule can travel to the tools your team really works in, so a to-do set by a salesperson never gets lost in the CRM. The trigger returns each newly created task as its own bundle.

How it fires
scheduled; Make asks Capsule for new tasks on the rhythm of the scenario.
When to use it
you mirror Capsule tasks as cards in a project board, or post them in a team channel.
Watch out
completing or rescheduling a task does not count as new, so pick Watch Tasks when those updates matter too. Each task found costs one operation per module it goes through.
Capsule CRM5Watch Opportunities

Watch Opportunities

Instant trigger

In MakeTriggers when an opportunity is created, updated or deleted.

Your scenario hears about any change to an opportunity, whether it was created, edited or deleted, which lets you react to the life of a deal and not just its birth.

How it fires
instant. Capsule calls Make through a webhook as soon as the change happens, shown by the lightning badge on the module.
When to use it
a deal moves to a new milestone and finance needs a heads-up, or a lost deal should update a forecast sheet.
Watch out
since three kinds of events arrive through the same module, add a filter after it so a deletion does not run the steps meant for an update. Set it up with Create a webhook before the connection.
Capsule CRM6Watch Parties

Watch Parties

Instant trigger

In MakeTriggers when a party is created, updated or deleted.

Any contact change in Capsule, on a person or an organisation, can reach your other tools the moment it is saved. Creations, updates and deletions all come through this one trigger.

How it fires
instant; Capsule notifies Make through a webhook as soon as it happens, with no polling schedule to set.
When to use it
a phone number corrected in Capsule should also be corrected in your helpdesk or your mailing list.
Watch out
the webhook comes first. Click Create a webhook, then Create a connection, otherwise the module has nowhere to receive events.
Capsule CRM7Watch Projects

Watch Projects

Instant trigger

In MakeTriggers when a case is created, updated or deleted.

Projects tracked as cases in Capsule can push their news to the rest of your stack: the module fires when a case is created, updated or deleted, so status changes follow the work.

How it fires
instant. Capsule calls Make through a webhook as soon as it happens, which is why the module carries a lightning badge.
When to use it
a closed case should archive a shared folder, or a new one should open a channel for the delivery team.
Watch out
the module is labelled Projects in Make while its descriptions talk about cases; both words point at the same records. Filter on the type of event before acting.
Capsule CRM8Watch Tasks

Watch Tasks

Instant trigger

In MakeTriggers when a task is created, updated or deleted.

This trigger follows every task in Capsule through its whole life, from creation to edit to deletion, so your other tools always show the same to-do list as your CRM.

How it fires
instant: Capsule sends the event to Make through a webhook as soon as it happens, without waiting for a schedule.
When to use it
you keep a task board or a calendar in sync with Capsule and want edits reflected, not just new entries.
Watch out
if the same scenario also writes tasks back into Capsule, it can trigger itself; add a filter so the loop stops at the first pass.
Modules

Everything Capsule CRM can do in Make

Capsule CRM gives you 70 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Capsule CRM1

Add an Additional Party in Case

Action

In MakeAdds an person or organisation as an additional contact to the case.

Attaches one more person or organisation to a case, so a project record shows everyone involved and not only the main client contact.

When to use it
a client brings in an outside accountant halfway through a project and a form tells you so; the scenario adds that contact to the case.
Watch out
the module links a contact, it does not create one. If the person might be new to Capsule, run Search Parties first.
Capsule CRM2

Add an Additional Party in Opportunity

Action

In MakeAdds an person or organisation as an additional contact to the opportunity

Puts an extra decision maker on a deal, which gives the rep the full buying group on one screen instead of scattered notes.

When to use it
a meeting booking or a signed NDA names a second contact at the prospect, and you want that person tied to the opportunity right away.
Watch out
pick the Case version for projects; this one only works on opportunities, and the two look alike in the module list.
Capsule CRM3

Create a Case

Action

In MakeCreates a new case.

Opens a new case in Capsule, the record where you follow a project or a support matter, without anyone filling in the form by hand.

When to use it
a deal is marked won, or an onboarding form comes in, and delivery needs its own record linked to that client.
Watch out
run Run once with test data first. Every test creates a real case, and you will have to clean it up with Delete a Case.
Capsule CRM4

Create a Custom Field

Action

In MakeCreates a new party, opportunity or case custom field.

Adds a new field definition for parties, opportunities or cases, so Capsule starts storing a piece of information it did not track before.

When to use it
you roll out a new data point, like a lead source code, across several Capsule accounts and want the same field set up everywhere.
Watch out
this changes the structure of the account, not a single record. It rarely belongs in a scenario that runs on every new contact.
Capsule CRM5

Create a Milestone

Action

In MakeCreates a new opportunity milestone.

Adds a new stage to your opportunity pipeline, the steps a deal goes through from first contact to signature.

When to use it
you mirror a sales process defined in another tool and need Capsule to carry the same stages without retyping them.
Watch out
milestones are shared by every opportunity. Creating one from a scenario that fires often will fill the pipeline with duplicates, so guard it with a search first.
Capsule CRM6

Create an Entry

Action

In MakeCreates a new entry.

Writes an entry into Capsule's history, such as a note, so the timeline of a contact or a deal tells the full story, including what happened in other tools.

When to use it
a customer replies to a survey or signs a document elsewhere, and you want that fact logged on their record for the next person who opens it.
Watch out
keep the text short and readable. An entry is read by humans, so map clear words, not a raw dump of the previous bundle.
Capsule CRM7

Create an Opportunity

Action

In MakeCreates a new opportunity.

Drops a new deal into your Capsule pipeline, ready for a rep to work, straight from wherever the demand showed up.

When to use it
a pricing request on your website or a qualified lead in your ad tool should become a tracked opportunity without copy and paste.
Watch out
a deal is usually tied to a party. Look the contact up with Search Parties, or create it with Create a Party, before this module.
Capsule CRM8

Create a Party

Action

In MakeCreates a new party.

Adds a person or an organisation to Capsule, which turns a form submission, a signup or a business card scan into a real CRM contact.

When to use it
new newsletter subscribers or webinar attendees should land in Capsule so sales can see them.
Watch out
the module creates, it does not check. Put Search Parties in front of it, and add a filter so creation only runs when the search finds nothing.
Capsule CRM9

Create a Tag

Action

In MakeDefines a new party, opportunity or case tag.

Defines a new tag for parties, opportunities or cases, the labels you use in Capsule to group and filter records.

When to use it
each new campaign or event should get its own tag in Capsule, created at the moment the campaign starts in your marketing tool.
Watch out
this defines the tag; it does not stick it on a contact. Applying it to a record is a separate step, usually through the update module of that record.
Capsule CRM10

Create a Task

Action

In MakeCreates a new task.

Puts a to-do on someone's Capsule list, which is the simplest way to make sure a follow-up actually happens.

When to use it
a new opportunity, a missed call or a support ticket should give the account owner a clear next action inside the CRM they already check.
Watch out
give each task a precise title built from the incoming bundle, like the deal name. Ten tasks all called "Follow up" help nobody.
Capsule CRM11

Create a Task Category

Action

In MakeCreates a new task category.

Adds a new category for Capsule tasks, so calls, emails or demos can be told apart at a glance on the task list.

When to use it
you are setting up a fresh Capsule account from a template, or adding a new kind of activity for the team.
Watch out
categories are account settings. This module fits a one-time setup scenario far better than a flow that runs on every record.
Capsule CRM12

Create a Track

Action

In MakeApplies a track definition to a case or opportunity to create a track.

Applies a track definition to a case or an opportunity, which sets up the sequence of work you designed for that kind of record in one step.

When to use it
a deal is won and the onboarding track should start on it automatically, instead of someone applying it from the Capsule screen.
Watch out
you need to know which track definition to apply. List Track Definitions shows the ones that exist in the account.
Capsule CRM13

Delete a Case

Action

In MakeDeletes a specific case.

Removes a specific case from Capsule, which keeps the project list clean when records were created by mistake or by a test.

When to use it
a cancelled order in your shop should also clear the delivery case the scenario opened for it earlier.
Watch out
a deletion does not come back through Make. Place a filter before this module, and test on a dummy case with Run once.
Capsule CRM14

Delete a Custom Field

Action

In MakeRemoves a custom field from your capsule account

Takes a custom field out of your Capsule account, handy when you retire a data point that nobody fills in anymore.

When to use it
you clean up several Capsule accounts at once and want the same obsolete field gone from each.
Watch out
the field disappears for the whole account, not for one contact. Export or copy what it holds before you run the scenario.
Capsule CRM15

Delete a Milestone

Action

In MakeRemoves a Milestone from the capsule account. You cannot delete a Milestone while it is still being used on an Opportunity. First you need to update the Milestone on all such Opportunities.

Removes a stage from the opportunity pipeline, which trims a sales process that has grown too many steps.

When to use it
you merge two stages into one and want the retired one gone after the deals have moved.
Watch out
Capsule refuses to delete a milestone that an opportunity still uses. Move those deals first, for example with List Opportunities and Update an Opportunity, then delete.
Capsule CRM16

Delete an Entry

Action

In MakeRemoves an entry from the capsule account and any associated attachments.

Erases an entry from a record's history, together with any attachments it carries, for when a note should never have been logged.

When to use it
a scenario logged duplicate notes on a batch of contacts and you need a cleanup pass driven by List Entries.
Watch out
attached files go with the entry. If a document must be kept, save it somewhere else before this module runs.
Capsule CRM17

Delete an Opportunity

Action

In MakeDeletes a specific opportunity.

Removes a specific deal from Capsule, so spam leads or test opportunities stop polluting your pipeline and your forecast.

When to use it
a form flagged as spam by your anti-bot tool had already created an opportunity, and the scenario takes it back out.
Watch out
the deal goes away for good through Make. List Deleted Opportunities can show what was removed, but nothing here restores it.
Capsule CRM18

Delete a Party

Action

In MakeDeletes a specific party.

Deletes a person or an organisation from Capsule, useful when a contact asks to be erased or when duplicates pile up.

When to use it
a deletion request received through your privacy form should remove the matching contact from the CRM as well.
Watch out
find the exact party with Search Parties before this step, and stop the scenario if the search returns more than one match.
Capsule CRM19

Delete a Tag

Action

In MakeRemoves a tag from the capsule account. NOTE that this will remove the tag from any parties, opportunities and cases it was assigned to.

Removes a tag from your Capsule account, which clears out labels left over from old campaigns.

When to use it
an event is over and its tag has no reason to stay in the filter list.
Watch out
the tag is also stripped from every party, opportunity and case that carried it. If you still need that grouping, export the tagged records first.
Capsule CRM20

Delete a Task

Action

In MakeDeletes a specific task.

Removes a specific task from Capsule, so a to-do that no longer makes sense stops cluttering the rep's list.

When to use it
a meeting was cancelled in your calendar tool and the preparation task created for it should disappear too.
Watch out
deleting is not completing. If you want a trace that the work was done, use Update a Task instead.
Capsule CRM21

Delete a Task Category

Action

In MakeRemoves a category from your capsule account. Any tasks under this category will be retained but will become uncategorized.

Removes a task category from your Capsule account while keeping the tasks that used it.

When to use it
you simplify the way the team sorts its activities and fold an old category into a broader one.
Watch out
the tasks stay, but they lose their category and show up uncategorized. Reassign them with Update a Task if you still want them sorted.
Capsule CRM22

Delete a Track

Action

In MakeRemoves a track and related tasks from case or opportunity.

Takes a track off a case or an opportunity, along with the tasks that came with it, for when a workflow was applied to the wrong record.

When to use it
a deal is lost after its onboarding track had already started, and the pending steps should vanish.
Watch out
the related tasks leave with the track. Test it on a dummy deal with Run once before pointing it at live opportunities.
Capsule CRM23

Make an API Call

Action

In MakePerforms an arbitrary authorized API call.

Calls any endpoint of the Capsule CRM API with the connection you already set up, which covers what the listed modules do not.

When to use it
you need a Capsule feature none of the 78 modules exposes, and you are comfortable reading the Capsule API documentation.
Watch out
you write the request yourself: path, method and body. The connection handles authentication, nothing else, so test every call with Run once.
Capsule CRM24

Remove an Additional Party in Case

Action

In MakeRemoves that person or organisation as an additional contact of the case.

Detaches a person or organisation from a case without deleting the contact itself, so the project record stays accurate when people change.

When to use it
a supplier leaves a project, or a client contact changes jobs, and they should no longer appear on the case.
Watch out
List Additional Parties in a Case tells you who is attached; use it to pick the right contact before removing.
Capsule CRM25

Remove an Additional Party in Opportunity

Action

In MakeRemoves a party or organisation as an additional contact of the opportunity.

Unlinks an extra contact from a deal while the contact stays in Capsule, which keeps the buying group current.

When to use it
your prospect's champion leaves the company and your enrichment tool reports it, so the opportunity should drop that name.
Watch out
it does not touch the main contact of the opportunity, only the additional ones. For a case, pick the Case version.
Capsule CRM26

Show a Case

Action

In MakeShows a specific case

Fetches the full details of one case, so later modules can use its data in a message or in another tool.

When to use it
a trigger hands you only a case reference, and you need the whole record to write a clear message or update another tool.
Watch out
it returns a single case. To load several at once from a list of IDs, Show Multiple Cases saves operations.
Capsule CRM27

Show a Custom Field

Action

In MakeShows a specific custom field.

Reads the definition of one custom field, useful for checking how a field is set up before a scenario writes into it.

When to use it
you copy a field setup from one Capsule account to another and need the original definition as a model.
Watch out
this shows the field itself, not the values stored on contacts. Those come with the record, through Show a Party or Show an Opportunity.
Capsule CRM28

Show a Milestone

Action

In MakeShows a specific milestone.

Returns the details of one pipeline stage, such as its name and description, to reuse in the rest of the scenario.

When to use it
an opportunity changed stage and your Slack alert should say the stage name in words, not an internal reference.
Watch out
for the whole pipeline in one go, List Milestones is a better fit than calling this module once per stage.
Capsule CRM29

Show an Entry

Action

In MakeShows a specified note, email or the details of a completed party task.

Pulls one entry from a record's history: a note, an email, or the details of a completed party task.

When to use it
a manager wants the text of the last note on a key account posted in a team channel, or copied into a document.
Watch out
the module needs to know which entry. It usually follows List Entries or List Entries by Date, which give you the entries of a record.
Capsule CRM30

Show an Opportunity

Action

In MakeReturns a specific opportunity.

Loads one deal with its details, which gives the next modules everything they need to report on it or copy it elsewhere.

When to use it
an instant trigger fires on a deal change, and you want the up-to-date record before writing it into your forecast sheet.
Watch out
one opportunity per call. For a list of known IDs, Show Multiple Opportunities avoids a long chain of calls.
Capsule CRM31

Show a Party

Action

In MakeShows a specific person or organisation.

Reads one person or organisation from Capsule, so the scenario can use contact details kept in your CRM.

When to use it
a new task mentions a party, and your reminder email should greet that contact by name with the right company.
Watch out
if you only know an email or a name, Search Parties is the module to start with; this one expects a specific party.
Capsule CRM32

Show a Tag

Action

In MakeShows a specific tag.

Returns the details of one tag defined in Capsule, handy for checking a label before the scenario relies on it.

When to use it
a scenario routes contacts by tag and needs to confirm what a given tag is before sending them down a branch.
Watch out
this reads the tag definition only. To see every tag of the account, List Tags does it in a single module.
Capsule CRM33

Show a Task

Action

In MakeShows a specific task.

Fetches one task with its details, so a later module can post it, copy it or check its state.

When to use it
Watch Tasks tells you a task changed, and your project board needs the latest version of that task to stay aligned.
Watch out
a task can be deleted between the trigger and this step; a Watch Tasks event about a deletion should skip this step, so filter on the event first.
Capsule CRM34

Show a Task Category

Action

In MakeShows a specific task category.

Reads one task category, which gives you its name and color to reuse elsewhere in the flow.

When to use it
tasks copied to another tool should keep the same category label so the team recognizes them.
Watch out
when you need every category at once, for a mapping table, List Task Categories is quicker than one call per category.
Capsule CRM35

Show a Track

Action

In MakeShows a specific track.

Returns one track applied to a case or an opportunity, so you can see where a structured workflow stands.

When to use it
a status message about a client's onboarding needs the details of the track running on a client project.
Watch out
to find the tracks of a record in the first place, List Tracks comes before this module.
Capsule CRM36

Update a Case

Action

In MakeUpdates an existing case

Changes an existing case, so a project record in Capsule follows what happens in your other tools.

When to use it
a delivery marked done in your project tool should close or update the matching case in Capsule.
Watch out
the scenario needs the right case first. Search Cases returns the same results as the Capsule search bar, so it can return more than one.
Capsule CRM37

Update a Custom Field

Action

In MakeUpdates the details of a party, opportunity or case field definition.

Edits the definition of a party, opportunity or case field, for example to rename it, without touching the values already stored.

When to use it
you keep several Capsule accounts aligned and a field was renamed in the main one.
Watch out
this is an account setting. Tell the people who use the field before a scenario renames it in their account.
Capsule CRM38

Update a Milestone

Action

In MakeUpdates the name, description or probability of a milestone.

Changes the name, the description or the probability of a pipeline stage, which keeps your forecast in line with how deals really close.

When to use it
sales management revises the win probability of each stage in a planning sheet, and Capsule should follow.
Watch out
the change applies to the stage itself, which every deal at that stage shares, so check the forecast after a run.
Capsule CRM39

Update an Entry

Action

In MakeUpdates the content of notes and emails.

Rewrites the content of an existing note or email in Capsule, for when a logged entry needs a correction or an addition.

When to use it
a scenario logs a call note, then a transcription tool delivers the full summary and you replace the draft text.
Watch out
the module covers notes and emails. It does not reopen a completed task, which is handled by Update a Task.
Capsule CRM40

Update an Opportunity

Action

In MakeUpdates an existing opportunity

Edits an existing deal, which lets events outside Capsule move your pipeline forward without a rep updating it by hand.

When to use it
a quote gets signed in your e-signature tool, and the matching opportunity should move to the next milestone.
Watch out
Search Opportunities behaves like the Capsule global search and can return several deals; add a filter so only the right one is updated.
Capsule CRM41

Update a Party

Action

In MakeUpdates an existing party. Fields that are not included in the request will remain unchanged.

Keeps a contact or company record current in Capsule without rewriting it: you send only the values that changed, and every field you leave out stays exactly as it was.

When to use it
a form or another app hands you a new detail for someone who already lives in Capsule.
Watch out
the module needs the party's ID, so place Search Parties before it when the scenario does not carry that ID yet.
Capsule CRM42

Update a Tag

Action

In MakeUpdates the details of a party, opportunity or case tag.

Edits the details of one tag definition, whether it labels parties, opportunities or cases, so your naming stays consistent without starting again from scratch.

When to use it
your team agrees on clearer labels and the old ones need tidying rather than deleting.
Watch out
this changes the definition shared by the whole account; removing a label is the job of Delete a Tag, which also strips it from every record.
Capsule CRM43

Update a Task

Action

In MakeUpdates an existing task.

Moves a follow-up forward: the module rewrites a task that already exists in Capsule, so a reminder created earlier reflects what actually happened next.

When to use it
a step in another app changes the context of a follow-up your sales rep had planned in Capsule.
Watch out
it works on one task identified by its ID; the Watch Tasks trigger or List Tasks upstream gives you that ID.
Capsule CRM44

Update a Task Category

Action

In MakeAllows to rename or change the colour of the task category.

Gives a task category a new name or a new colour, the two things this module can change, so the team's to-do list reads clearly at a glance.

When to use it
categories were created in a hurry and now need labels everyone on the team understands.
Watch out
nothing else about the category moves here; renaming and recolouring are the whole job, so keep your expectations to that.
Capsule CRM45

Update a Track

Action

In MakeUpdates basic details about a track.

Adjusts the basic details of a track, the set of tasks Capsule attaches to a case or an opportunity, without removing it and applying it again.

When to use it
a track applied earlier with Create a Track needs a correction after the fact.
Watch out
the doc only promises basic details; taking the track off a record, together with its related tasks, belongs to Delete a Track.
Capsule CRM46

List Additional Parties in a Case

Search

In MakeLists additional parties related to specific case.

Returns every extra contact linked to one case, one bundle per person or organisation, so later modules can reach everyone involved and not only the main contact.

When to use it
a case closes and all its stakeholders should receive the same update from your email tool.
Watch out
it works case by case, so the scenario must already hold the case's ID, from Watch Projects for instance.
Capsule CRM47

List Additional Parties in Opportunity

Search

In MakeLists additional parties related to specific opportunity.

Pulls the secondary contacts attached to a given opportunity, each one arriving as a separate bundle you can map into the next step of the scenario.

When to use it
before a proposal goes out, the scenario needs the decision makers beyond the primary contact.
Watch out
this one covers opportunities only; for a case, pick List Additional Parties in a Case instead.
Capsule CRM48

List Cases

Search

In MakeLists all cases.

Brings back the cases of your Capsule account as a stream of bundles, handy when a scenario must go through them one after another.

When to use it
a first sync pushes existing cases into a spreadsheet or a reporting tool.
Watch out
every bundle that reaches the next module costs an operation there, so narrow things down with Search Cases when you only need a few.
Capsule CRM49

List Custom Fields

Search

In MakeLists all custom fields.

Shows which custom fields exist in the account, so a scenario can discover their definitions before it writes anything into them.

When to use it
you map data coming from another app and want to check which custom fields Capsule already holds.
Watch out
when a field is missing, create it with Create a Custom Field rather than typing an invented name into the mapping.
Capsule CRM50

List Deleted Opportunities

Search

In MakeLists all deleted opportunities.

Recovers the trail of opportunities removed from Capsule, one bundle each, so another system can clean up its own copy of the pipeline.

When to use it
your reporting sheet still shows deals that someone deleted in the CRM.
Watch out
it tells you what disappeared and nothing more; it does not bring any opportunity back to life.
Capsule CRM51

List Deleted Parties

Search

In MakeLists all parties that have been deleted from capsule since the date specified in the since parameter.

Tells your scenario which contacts and organisations were deleted from Capsule since a date you choose in the since parameter.

When to use it
a mailing list or a billing tool must drop people who no longer exist in the CRM.
Watch out
pick that date carefully; set it too far back and the scenario reprocesses old deletions, spending operations for nothing.
Capsule CRM52

List Deleted Projects

Search

In MakeLists all deleted cases.

Captures the cases that were removed from Capsule, so a mirror elsewhere stops showing work that no longer exists.

When to use it
a project board in another tool keeps cards for cases already deleted in Capsule.
Watch out
the module name says Projects while the doc says cases; both words point to the same records, so do not look for a second module.
Capsule CRM53

List Employees

Search

In MakeLists all employees linked to specific organisation.

Turns a company record into a list of real people: the module returns the contacts linked to one organisation in Capsule.

When to use it
a new deal with a company should notify everyone you know there, not just one name.
Watch out
start from the organisation, not from a person; the scenario needs that organisation's record before this module can answer.
Capsule CRM54

List Entries

Search

In MakeLists notes, emails and completed tasks for parties, cases and opportunities.

Gathers the history behind a record: notes, emails and completed tasks tied to parties, cases and opportunities.

When to use it
a client moves to a new account manager who needs the full context before the first call.
Watch out
each entry becomes its own bundle, so add an aggregator when the next app expects one single block of text.
Capsule CRM55

List Entries by Date

Search

In MakeLists notes, emails and the details of completed party tasks in descending order starting with the most recent entry date first.

Reads the activity timeline newest first: notes, emails and the details of completed party tasks, sorted by entry date in descending order.

When to use it
a digest sent to the team should open with what happened most recently.
Watch out
compared with List Entries, the ordering is the whole point; choose this one when recency matters more than a specific record.
Capsule CRM56

List Milestones

Search

In MakeLists all milestones.

Lays out the milestones of your sales pipeline, the stages an opportunity goes through, so a scenario can pick the right one instead of guessing.

When to use it
another tool sends a stage name and you need the matching milestone before updating an opportunity.
Watch out
map the milestone from this list rather than typing it by hand, or a renamed stage will quietly break the scenario.
Capsule CRM57

List Opportunities

Search

In MakeLists all opportunities.

Walks through the deals stored in Capsule, each one delivered as a bundle ready to be mapped into another app.

When to use it
a first export fills a dashboard or a spreadsheet with the pipeline as it stands.
Watch out
on a busy account that means many bundles and many operations downstream; Search Opportunities keeps the batch smaller.
Capsule CRM58

List Opportunities by Party

Search

In MakeLists all opportunities associated with the specific party.

Starts from one contact or company and returns only the opportunities attached to it, which is exactly what a sales rep wants to know before a call.

When to use it
a support ticket or an incoming email should show which deals exist with that customer.
Watch out
the scenario needs the party first; place Search Parties before it when only a name arrives.
Capsule CRM59

List Parties

Search

In MakeLists all parties.

Loads your contacts and organisations one bundle at a time, the widest net this app offers when you work with people.

When to use it
an initial import copies the whole address book into a newsletter tool or a data warehouse.
Watch out
every bundle counts operations on the modules that follow, so switch to Search Parties or Show Multiple Parties when a subset is enough.
Capsule CRM60

List Tags

Search

In MakeLists all tags for either party, opportunity or case.

Collects the tags defined for one kind of record, parties, opportunities or cases, so a scenario can reuse existing labels instead of creating duplicates.

When to use it
before tagging a record, you check that the tag exists and pick it from the list.
Watch out
the module lists one record type at a time; choose parties, opportunities or cases in its settings.
Capsule CRM61

List Task Categories

Search

In MakeLists all task categories.

Hands the scenario the set of task categories your team uses, so new tasks land in the right bucket rather than in an uncategorized pile.

When to use it
an automation creates tasks and must attach a category that matches your own naming.
Watch out
a category that is missing comes from Create a Task Category; never assume it exists because it did in another account.
Capsule CRM62

List Tasks

Search

In MakeLists all tasks.

Delivers the tasks stored in Capsule as individual bundles, useful to push follow-ups into another task manager or a reminder channel.

When to use it
a sales team wants its Capsule to-dos mirrored on a shared board.
Watch out
this is a one-off read; to react each time a task changes, the Watch Tasks trigger is the better fit.
Capsule CRM63

List Track Definitions

Search

In MakeLists track definitions with the option to filter for only the track definitions for cases or opportunities.

Displays the track definitions available in Capsule, with an option to keep only those meant for cases or only those meant for opportunities.

When to use it
a scenario must apply the right track with Create a Track and first needs to know which definitions exist.
Watch out
a definition is the model, not a running track; the tracks already applied to a record come from List Tracks.
Capsule CRM64

List Tracks

Search

In MakeLists tracks for a specific case or opportunity.

Reveals the tracks applied to one case or one opportunity, so you know which task sequences that record already carries.

When to use it
before applying a new track, the scenario checks that the record does not have it yet.
Watch out
it needs the case or the opportunity first; the catalogue of available models is List Track Definitions.
Capsule CRM65

Search Cases

Search

In MakeSearches for cases. This will return the same results as the global search inside Capsule.

Finds cases the way the search bar inside Capsule does, so the results match what your team sees when typing the same words.

When to use it
a message arrives with a project name and the scenario must locate the matching case.
Watch out
zero, one or several cases can come back; add a filter before any module that expects exactly one.
Capsule CRM66

Search Opportunities

Search

In MakeSearches for opportunities. This will return the same results as the global search inside Capsule.

Locates deals through Capsule's global search, returning the same hits a user would get inside the app.

When to use it
a signed quote in another tool names a deal and you need its Capsule record.
Watch out
a broad term returns several opportunities, and each one runs the rest of the scenario; make the query as precise as your data allows.
Capsule CRM67

Search Parties

Search

In MakeSearches for parties. This will return the same results as the global search inside Capsule.

Looks up people and organisations exactly as the global search in Capsule would, the usual first step before updating or linking a contact.

When to use it
a web form submits a lead and the scenario checks whether that person already exists before creating a duplicate.
Watch out
when nothing matches, the module returns zero bundles, so plan the path that creates the party.
Capsule CRM68

Show Multiple Cases

Search

In MakeAllows to load a list of cases by providing their unique ids.

Fetches several cases in one go from their unique IDs, tidier than chaining one Show a Case per record.

When to use it
an earlier step already collected a batch of case IDs, from a sheet or from a webhook.
Watch out
it only works with IDs; to find cases from words, Search Cases is the right module.
Capsule CRM69

Show Multiple Opportunities

Search

In MakeReturns a list of opportunities, specified by the opportunityIds provided.

Refreshes a set of deals at once from the list of opportunityIds you provide, handy when another system stores those references.

When to use it
a spreadsheet keeps Capsule deal IDs and you want up-to-date details for all of them.
Watch out
no ID, no result; pair it with Search Opportunities when the scenario only knows names.
Capsule CRM70

Show Multiple Parties

Search

In MakeAllows to load a list of parties by providing their unique ids.

Retrieves several contacts or organisations at once from their unique IDs, keeping the scenario short when you already know exactly who you need.

When to use it
an earlier step stored Capsule party IDs and the next app needs the full record of each person.
Watch out
the IDs must be Capsule's own; references from another CRM will not match anything.
Need help

Need help automating Capsule CRM with Make?

A person reads every message.

FAQ

Capsule CRM and Make: common questions

01Is the Capsule CRM Make integration free?
Yes, Capsule CRM is a standard app in Make, so you can use it on the Free plan. That plan has its own limits: 2 active scenarios, at least 15 minutes between two scheduled runs, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Make counts usage in operations, one operation being one module handling one bundle. Paid plans lower the minimum interval to 1 minute, remove the cap on active scenarios and allow 40 minutes of execution. You still need an active Capsule account, which is billed by Capsule, not by Make.
02What do you need to connect Capsule CRM to Make?
An active Capsule account and a Make account. In a scenario, add any Capsule CRM module, click Create a connection, give it a name if you like, and sign in with OAuth or paste a personal access token. For your own OAuth app, register it in Capsule with the callback URI shown in the Make docs, then copy the Client ID and Client secret into Make. Instant triggers need one extra step: click Create a webhook before creating the connection. After that, every Capsule module in your scenarios reuses the same connection.
03Do Capsule CRM triggers fire instantly in Make?
It depends on the trigger. Four of them are instant: Watch Opportunities, Watch Parties, Watch Projects and Watch Tasks. Capsule calls Make through a webhook as soon as a record is created, updated or deleted. The other four, Watch new Cases, Watch new Opportunities, Watch new Parties and Watch new Tasks, are scheduled: Make checks Capsule on the scenario's schedule, every 15 minutes by default, and never more often than that on the Free plan. On a paid plan, you can set the schedule down to 1 minute.
04What if a Capsule CRM module is missing in Make?
Use Make an API Call. It reaches any endpoint of the Capsule CRM API with the connection you already have, so you are not limited to the 78 listed modules. You write the request yourself, following the Capsule API documentation, and Make takes care of authentication. Before you get there, check the searches: Capsule has 25 of them, including the deleted records lists. Also note that Make's help page for Capsule CRM says its content is AI-generated, so confirm important behavior in Capsule's own docs.
05Should you use Make or n8n for Capsule CRM?
It depends on the tool your team already uses. On Make, Capsule CRM comes with 78 ready-made modules, 8 triggers of which 4 are instant, plus Make an API Call for anything else, and it works from the Free plan. The same app often has an n8n node as well, so check its coverage there against the modules you need. If Capsule is your only need, the Free plan lets you try the Make side before deciding. The comparison page linked above goes through the differences between both platforms.