Resources · Make integration

Capri Make integrationAutomate Capri with Make.

Can Make manage your Capri agents for you? The Capri Make integration gives you 16 action modules, all built around agents. This guide is for teams who run Capri and want to drive it from their other apps, and it walks you from connection to a first working scenario.

Try the Capri integration on MakeSee the 16 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Capri Make integration do for you?

The Capri Make integration links your Capri account to Make so your agents can be created, fed and adjusted by a scenario, the automation you build in Make, instead of by hand. Every one of its 16 modules is an action: it does something in Capri when an earlier step of the scenario asks it to.

Feed an agent from the rest of your stack. A lead fills a form in another app, and Send Plain Text to Capri Agent hands the answer to your agent. When the material arrives as mail, Send Emails to your Capri Agent is the module to pick.

Spin up agents from a proven model. Duplicate an Agent copies one that already works, then Add a knowledge source and Add Prompt to an agent give the copy its own material. Capri Create Agent starts from a blank one when no model fits.

Keep live agents in step with your business. Update FAQ, Switch an Agent's active prompt and Toggle agent's activation status let a scenario change what an agent says, or pause it, when something changes elsewhere.

Two limits matter. Capri has no trigger module in Make, so another app or the scenario's schedule has to start things. Make also marks its Capri documentation as limited, which means field details are best read in the module itself. If you weigh the same job in n8n, the n8n vs Make comparison lays out the differences, the Make training covers the editor basics, and Make troubleshooting helps when a run fails.

Connect

How do you connect Capri to Make?

  1. 01

    Open the connection window

    Add any Capri module to a scenario and click Create a connection. A connection is your Capri account linked to Make once, then reused by all 16 Capri modules, so you only do this step one time.

  2. 02

    Give the connection a name

    The name is optional, but it pays off when you run more than one Capri workspace or share scenarios with a teammate. Something like the client or team name is enough to tell connections apart later.

  3. 03

    Authorize and save

    Depending on what Capri offers, Make either sends you to Capri's page to approve access or asks you to paste the key Capri gives you. Finish that step, then click Save and the module is ready to fill.

First scenario

Build your first scenario with Capri

GoalWhen a new form entry arrives in another app, Make sends its text to your Capri agent.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the big +. The first module you place is the one that starts every run.

  2. 02

    Start from the app that holds the text

    Capri has no trigger, so the first module comes from another app, such as your form tool. Search it by name, pick its trigger and click Create a connection to link that account.

  3. 03

    Add the Capri module

    Click the + on the right of the first module, search Capri and pick Send Plain Text to Capri Agent. Connect Capri, then map the answer from the form into the text the module sends.

  4. 04

    Test with Run once

    Click Run once. Make runs the scenario a single time and shows the bundle, one item passed from module to module, that each step received. Check the text reached Capri as expected.

  5. 05

    Schedule and switch on

    Open the clock on the first module. A new scenario checks every 15 minutes by default, which is also the shortest interval on the Free plan. Keep it or change it, then switch the scenario on.

Modules

The 16 Capri modules, one by one

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

Capri1

Add Prompt to an agent

ActionIn the docs only

Gives an existing agent one more prompt, so it has another set of instructions ready without anyone opening Capri. Each run is one operation, a single execution Make counts on your plan.

When to use it
after Duplicate an Agent, to hand the copy instructions written for its new audience.
Watch out
adding a prompt is not the same as making it the live one; that is the job of Switch an Agent's active prompt.
Capri2

Add a knowledge source

ActionIn the docs only

Hands an agent new reference material, so its answers can draw on what your team just published elsewhere. It sits right after the module that produced the material in your scenario.

When to use it
a product sheet or policy is finalized in another app and the agent should know about it too.
Watch out
Make's Capri documentation is limited, so check in the module which kinds of source it accepts before you map anything.
Capri3

Add a trigger to an agent

ActionIn the docs only

Sets up, from Make, something that makes a Capri agent spring into action on Capri's side. Handy when every new agent needs the same wiring and you would rather not repeat it by hand.

When to use it
as the last step of a scenario that creates or duplicates agents.
Watch out
as the name says, this is a Capri trigger attached to the agent, not a Make trigger; your scenario still needs another app or a schedule to start.
Capri4

Assign a Leadconnector location to an agent

ActionIn the docs only

Links an agent to a LeadConnector location, so the right agent is attached to the right place without a manual step in Capri. It only makes sense if you use LeadConnector alongside Capri.

When to use it
when a new location is opened and an agent is created or copied for it in the same scenario.
Watch out
map the location from an earlier module rather than typing it, or every run will point to the same one.
Capri5

Capri Create Agent

ActionIn the docs only

Creates a brand new agent in Capri from a scenario, so a new client or project gets its agent the moment it exists elsewhere. Check in Run once what it hands to the next module.

When to use it
when no existing agent is a good starting point; otherwise Duplicate an Agent saves setup.
Watch out
a scenario that runs twice on the same record creates two agents, so test with Run once first.
Capri6

Delete a Capri Agent

ActionIn the docs only

Removes an agent from Capri, which keeps your account clean when a client leaves or a test agent has served its purpose. It pairs well with a filter so only the intended agent goes.

When to use it
when an offboarding or cancellation in another app should retire the matching agent.
Watch out
a deletion does not come back; if you only want the agent quiet for a while, Toggle agent's activation status is the safer choice.
Capri7

Duplicate an Agent

ActionIn the docs only

Copies an agent that already works, so a new team or client starts from something tested instead of an empty shell. The modules that follow can then adjust it.

When to use it
you keep one reference agent and roll it out for each new account.
Watch out
the copy starts with what the original has; follow it with Update Agent Name so the two are easy to tell apart.
Capri8

Get an Agent

ActionIn the docs only

Reads one agent and returns its details as a bundle, so later modules can reuse them without you copying anything across. Judging by its name, it only reads, which makes it a safe first test.

When to use it
before an update, to check what the agent looks like, or to send its details to a sheet or a message.
Watch out
you need to point it at a specific agent, so map the reference from an earlier step.
Capri9

Make an API Call

ActionIn the docs only

Reaches any part of Capri's API from your scenario, using the same connection as the other modules. It covers what the 15 listed modules do not, for example a request the Make app has no module for.

When to use it
only once you have checked that no ready-made Capri module already does the job.
Watch out
you write the request yourself, so keep Capri's own API reference open while you build it.
Capri10

Send Emails to your Capri Agent

ActionIn the docs only

Passes email content to your agent, so messages landing in another inbox reach Capri without anyone forwarding them. Each email that flows through is one bundle and one operation.

When to use it
when the information your agent needs arrives by mail rather than through a form or a chat.
Watch out
if the content is plain text with no email around it, Send Plain Text to Capri Agent is the simpler fit.
Capri11

Send Plain Text to Capri Agent

ActionIn the docs only

Delivers a piece of text to your agent, whatever app it came from, so a form answer or a note ends up in Capri without copy and paste. This is the module used in the first scenario above.

When to use it
the source is a form, a sheet row or a chat message rather than an email.
Watch out
map only the text field you need; sending the whole bundle can hand the agent noise.
Capri12

Switch an Agent's active prompt

ActionIn the docs only

Changes which prompt an agent currently works with, so its behavior follows what is happening in your business without a trip to Capri. Your other prompts are there to switch back to.

When to use it
a campaign starts or ends in another app and the agent should change its script to match.
Watch out
the prompt has to exist first; add it with Add Prompt to an agent in an earlier module or scenario.
Capri13

Toggle agent's activation status

ActionIn the docs only

Turns an agent on or off from Make, so you can pause it without deleting anything and bring it back later. It is the reversible answer to Delete a Capri Agent.

When to use it
a subscription is paused or resumed in your billing tool and the agent should follow.
Watch out
the module name alone does not say whether a second run undoes the first, so read the agent with Get an Agent before you rely on it.
Capri14

Update Agent Name

ActionIn the docs only

Renames an agent, which keeps your Capri list readable when agents are created or copied by scenarios instead of by people. As its name says, it targets the name.

When to use it
right after Duplicate an Agent, to give the copy the client's or team's name.
Watch out
for changes beyond the name, Update an Agent is the module to reach for.
Capri15

Update FAQ

ActionIn the docs only

Refreshes the FAQ an agent relies on, so the answers it gives stay in line with what your team has just decided. Nobody has to edit it by hand in Capri.

When to use it
your support or sales team keeps its reference answers in another app and wants the agent to follow them.
Watch out
Make's Capri documentation is limited, so run it once on a test agent to see how the new content is applied.
Capri16

Update an Agent

ActionIn the docs only

Edits an existing agent in one step, so a change decided elsewhere lands in Capri without anyone logging in. It is the broad counterpart to the single-purpose update modules.

When to use it
several settings of the agent change together and a dedicated module like Update Agent Name would not cover them.
Watch out
the documentation does not detail which settings it touches, so try it on a test agent and read the result with Get an Agent.
Need help

Need help automating Capri with Make?

A person reads every message.

FAQ

Capri and Make: common questions

01Is the Capri Make integration free?
Yes, Capri is a standard app in Make, so it is available from the Free plan. That plan keeps 2 active scenarios, runs scheduled scenarios at most every 15 minutes, stops a run after 5 minutes and caps transfer at 512 MB. Paid plans (Core, Pro, Teams and Enterprise) lower the interval to 1 minute, remove the cap on active scenarios and allow 40 minutes per run. Usage is counted in operations each month. Capri's own subscription is a separate matter and depends on your Capri account.
02What do you need to connect Capri to Make?
A Capri account and a Make account. Make's documentation lists no special prerequisites for Capri. You add a Capri module, click Create a connection, optionally name it, then either authorize Make on Capri's page or paste the key Capri gives you, and click Save. The connection is then reused by all 16 modules. Make marks its Capri documentation as limited, so if a step looks different, follow what the connection window asks for.
03Does the Capri Make integration react in real time?
No, because Capri has no trigger module in Make: it cannot start a scenario by itself. You have two ways to launch it. The first is an instant trigger from another app, which calls Make through a webhook as soon as something happens there, and then Capri modules follow. The second is the scenario's own schedule on its first module, every 15 minutes by default, with 1 minute as the shortest interval on paid plans.
04What if a Capri module is missing in Make?
Use Make an API Call. It reaches any endpoint of Capri's API from your scenario with the same connection as the other modules, so an operation none of the 15 dedicated modules offers is still within reach. You write the request yourself, so keep Capri's API reference nearby. Make also flags its Capri documentation as limited, which means the module screens are the most reliable guide to what each one expects.
05Should you use Make or n8n for Capri?
It depends on the tool your automations already live in. On the Make side, the facts are clear: a Capri app with 16 action modules, no trigger, and Make an API Call for the rest, available from the Free plan. n8n often has a node for the same app, so check its catalog for Capri before you decide. Compare what each one covers for your exact use case rather than picking by habit, and test the key step with a real agent.
Same platform

Other docs you might need on this stack.

Browse all integrations