How Plainpaper thinks about integrations
Plainpaper is deliberately not the integration layer. Your agent connects to Brevo, Mailchimp, Meta, Canva, and the rest through their own connectors, with their own logins, the same way you would. Plainpaper never holds those credentials, so it can never send an email in your name, post an ad, or spend your budget.
What Plainpaper holds instead is the part that needs holding: the work itself, and the approval that releases it. Your agent drafts on the board, you approve on the board, and then the agent carries the approved work out through each platform's own connection.
The boundary, in one line. Plainpaper gates and records; your agent executes elsewhere. If a platform login exists anywhere, it exists in your agent's setup, never in Plainpaper.
The Tools palette
On the workspace Tools page you curate which external tools exist for this brand. Built-ins like Brevo and ActiveCampaign come from a gallery; add one in a click. For anything else your stack uses, add a custom entry: just a name, a description, and guidance for your agent. A tool entry never contains a login or an API key. It describes a platform and doesn't connect to it.
A custom entry is enough for anything, whether that's a niche ESP, an internal tool, or a client's house CMS. If you can describe how work should land there, your agent can be briefed on it. And curating the palette is your job, on purpose: your agent reads the palette, but only a human edits it.
Per-board toggles
Each board then switches on only the tools that campaign actually uses. A summer sale that ships through Brevo and Meta enables those two and nothing else. So when your agent reads the board, it doesn't have to guess which of six email platforms this campaign belongs to; the board says so.
The split is per campaign for a reason: the same workspace might run email-only campaigns next to paid-social pushes, and each board should carry only its own hand-offs.
Guidance is the payload
The real cargo of a tool entry is its guidance: a short brief that teaches your agent how board content maps onto that platform. The approved email card becomes a draft campaign in your ESP. Images come from the board's stored assets; your agent retrieves each one from Plainpaper in whatever shape the platform expects. And nothing pushes before approval: the guidance points the agent at approved work, and the approval gate decides what counts.
Guidance reads best as a handover note. For Brevo, something like: "Approved email cards become draft campaigns in Brevo. Never schedule or send them. Use our sender 'P&P Bookstore' and the newsletter list. Ask before creating anything new." Keep it short and specific, in your own conventions. Because it travels with the board, your agent knows how to hand off to your stack in every session, and you never have to explain your Brevo setup in chat again.
Setting up the other half
A tool entry tells your agent how to use a platform; the platform's own connector gives it the ability to. That connector lives in your agent client: claude.ai's connector directory, Claude Desktop, or wherever your agent runs. Plainpaper plays no part in that setup. Pick marketer-ready connectors from our tools gallery, or follow the step-by-step setup for the common pairings:
- Claude + Brevo: email campaigns and contacts.
- Claude + Mailchimp: email for Mailchimp shops.
- Claude + Meta Ads: ad creative into Meta.
- Claude + Klaviyo + Shopify: the ecommerce stack.
Try it
Once the palette is set and the board's tools are toggled on, have your agent rehearse the hand-off before anything real moves:
We use Brevo for email and Meta for paid social. Look at the tools enabled on my "Summer sale" board in Plainpaper and tell me, step by step, how you'd hand off the approved work, and what you'd need me to approve first.
The answer should read back your own stack: which cards go where, which assets come along, and which approvals stand between a draft and the door. If anything in that answer surprises you, go back and edit the guidance; that's where the fix belongs.