How-to guides

Connect your marketing stack

Plainpaper doesn't plug into Brevo or Meta. Your agent does. This guide explains that split, how to tell your agent how your brand uses each platform, and how the approved work hands off to each one.

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.

Connect each platform to your agent

Each platform's own connector gives your agent the ability to work there. That connector lives in your agent client: Claude'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:

Some work needs more than a connector. Brevo's automations have no API at all, so our open-source Brevo automation builder skill drives the builder in your own browser instead, and stops short of switching anything on. Setup is on the Brevo page.

Write the handoff down once

A connector tells your agent what it can do on a platform. It doesn't say how your brand uses it: which list, which sender, what an approved card turns into there. Write that down once, as a text block in your workspace's Guidelines, and every board that applies the guidelines carries it. Your agent reads the guidelines before it writes anything, so you never explain your Brevo setup in chat again.

A handoff note reads best as a note to a new colleague. 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. Your agent can write it for you:

Copy-paste prompt
Add a text block to my Plainpaper guidelines called "Handoff to Brevo and Meta". Approved email cards become draft campaigns in Brevo with the sender "P&P Bookstore" and the newsletter list, never scheduled or sent. Approved ad cards go to Meta as paused ads in the Summer campaign. Ask me before creating any new list, audience, or campaign.

Per-board instructions

When one campaign ships differently, say so on its board. Board guidance, under Board settings, is the brief your agent reads every time it loads that board, and where it disagrees with the playbook, yours wins. A summer sale that only runs in Brevo can say exactly that, so your agent doesn't have to guess which of six email platforms this campaign belongs to. You can read both the guidelines and the board guidance in the board's Brief.

After the handoff

Images and files come from the board's stored copies: your agent retrieves each one from Plainpaper in whatever shape the platform expects. Nothing pushes before approval, and a send or an upload waits as a proposed action until you approve it.

Once the work is out, your agent records a live link on the card: the real address of the campaign in your email platform or the ad in Ads Manager. The board then points at the thing that went out, next to the draft and the approval that produced it.

Try it

Once the connectors are in and the handoff note is written, have your agent rehearse the handoff before anything real moves:

Copy-paste prompt
We use Brevo for email and Meta for paid social. Read my "Summer sale" board in Plainpaper and our guidelines, then 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 files come along, and which approvals stand between a draft and the door. If anything in that answer surprises you, edit the handoff note; that's where the fix belongs.