Integrations/Make

Control what your AI agents do in Make.

Let your team build AI agents for Make. Bollard AI controls what each one can do, scenario by scenario.

Request early accessSee how it works →
Make
Ops Agent
lead-sync ScenarioOffReadFull use
reporting ScenarioOffReadFull use
billing ScenarioOffReadFull use
Delete scenarios and connections
What agents can do

Set what each agent can do in every scenario.

Each scenario gets one of three levels: Off, Read, or Full use. Anything not allowed is denied.

Off
No access
The agent can't see the scenario or that it exists.
Read
Read-only
The agent can read the steps and run logs of that scenario. It can't change anything.
Full use
Build and update
The agent can build and update that scenario.

Some actions stay off until explicitly turned on

Each one removes automations or the connections behind them for good, so it could override the limits set on individual scenarios.

Deleting scenarios or connectionsDeleting data store recordsChanging hooks and triggers
Set up & manage

Connect once. Manage everyone from there.

Connect once, then control access person by person. No new keys to hand out.

Step 1 · Set up

Connect once, company-wide

An admin connects your company's Make a single time and chooses which scenarios it covers. Any scenario left out stays out of reach for every agent.

Step 2 · Manage

Control access per person and agent

From one dashboard, set what every person and their agents can reach. Change it any time, with no new keys for anyone.

OffNo access
ReadRead-only
Full useRead, build, and update a single scenario
Example

An automation agent.

An ops agent edits the lead-sync scenario and can read reporting, but it can't open billing or delete a connection.

lead-sync ScenarioOffReadFull use
reporting ScenarioOffReadFull use
billing ScenarioOffReadFull use

Manage access

ALLOWEDOps Agent updated the lead-sync scenario
ALLOWEDOps Agent read the reporting scenario
BLOCKEDOps Agent tried to open billing, denied by default

Monitor activity

The security model

Top-tier security.

Bollard AI is access control for AI agents. It sits between your agents and Make, so they never hold your Make keys and never reach Make directly.

Everything runs through Bollard AI

Agents send their requests to Bollard AI, not to Make. Bollard AI checks each one against your rules and passes only the allowed requests through.

Denied by default

Every scenario starts off-limits, and deleting connections is held back on top of that. An agent gets in only where you've allowed it, and anything Bollard AI doesn't recognise is refused and held for review, never waved through on a guess.

Your keys stay sealed

Your Make keys are sealed in a vault unique to your company and never shown again. Bollard AI unlocks them only for the instant an allowed request needs it.

Activity you can read

Every attempt is recorded in plain English: who or which agent, what they tried, which scenario or connection, and the decision. The record is readable and can't be edited after the fact.

Questions

Make, answered.

Does connecting Make hand Bollard AI all your scenarios?+
Only what's connected. An admin chooses which scenarios Bollard AI covers, and that sets the most any agent could reach. Bollard AI doesn't browse or copy your automations. It sits in front of them and checks every request the agents make, passing or blocking each one.
Can an agent delete our automations or connections?+
Not unless you turn it on. Deleting scenarios and connections, and deleting data store records, are held off by default, so an agent can build and read where you allow without ever removing your automations, until you explicitly allow it.
Can an agent see more than the person who owns it?+
No. An agent reaches only what its owner reaches. An explicit Off always overrides an inherited permission.
Where do our Make keys live?+
Sealed in an encrypted vault, behind a key unique to your company. It's never shown again once connected, and Bollard AI unseals it only for the instant an allowed request needs it.
What happens when an agent tries something it's not allowed to do?+
Bollard AI blocks the request before it reaches Make, and the blocked attempt lands in the activity record with the reason.
How do we connect Make?+
An admin connects the company's Make once. Bollard AI seals the connection and builds the list of scenarios to set rules for. From then on, all management happens in the Bollard AI dashboard.
Early access

Put your team's agents to work in Make, without the risk.

We're onboarding our first development partners now. Tell us about your setup and we'll be in touch.

Request early accessAll integrations →