Integrations/Iterable
I

Control what your AI agents do in Iterable.

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

Request early accessSee how it works →
IIterable
Lifecycle Agent
Users Marketing areaOffReadFull use
Lists Marketing areaOffReadFull use
Campaigns Marketing areaOffReadFull use
Send campaigns
What agents can do

Set what each agent can do across your marketing.

Each area of Iterable, like users, lists, or campaigns, gets one of three levels: Off, Read, or Full use. Anything not allowed is denied, and sending is a separate switch.

Off
No access
The agent can't see that part of your marketing.
Read
Read-only
The agent can read users and lists in that area. It can't change or send anything.
Full use
Create and update
The agent can add and update users in that area.

Some actions stay off until explicitly turned on

Each one emails your audience or removes users for good, so it could override the limits set elsewhere.

Sending email and campaignsDeleting usersChanging subscriptions in bulk
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 Iterable a single time. Bollard AI lays out the areas of your account, and anything you don't allow 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, add, and update in a single area
Example

A lifecycle marketing agent.

A lifecycle agent updates users and can read your lists, but it can't send a campaign or delete a user.

Users Marketing areaOffReadFull use
Lists Marketing areaOffReadFull use
Campaigns Marketing areaOffReadFull use

Manage access

ALLOWEDLifecycle Agent updated a record in Users
ALLOWEDLifecycle Agent read a List
BLOCKEDLifecycle Agent tried to open Campaigns, 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 Iterable, so they never hold your Iterable keys and never reach Iterable directly.

Everything runs through Bollard AI

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

Denied by default

Every area starts off-limits, and sending campaigns 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 Iterable 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 user or list, and the decision. The record is readable and can't be edited after the fact.

Questions

Iterable, answered.

Does connecting Iterable hand Bollard AI your whole account?+
Only the areas you allow. An admin connects your Iterable, and you decide which areas, like users or lists, each agent can reach. Bollard AI doesn't browse or copy your account. It sits in front of it and checks every request the agents make, passing or blocking each one.
Can an agent email our audience on its own?+
Not unless you turn it on. Sending email and campaigns is held off by default, so an agent can manage users and read lists without ever emailing your audience, 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 Iterable 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 Iterable, and the blocked attempt lands in the activity record with the reason.
How do we connect Iterable?+
An admin connects the company's Iterable once. Bollard AI seals the connection and lays out the areas of your account 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 Iterable, 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 →