In preparation — the public API and MCP server are on their way: this page describes what will be possible; nothing can be activated yet.

Plumail in your application

Your product will write its own email.

The SDK and public API will wire Plumail into the heart of your application: sign-ups, transactional and campaigns triggered by your code — or by its agent.

Paste this into your project's agent
Read plumail.fr/app/install and connect Plumail for me.
Read plumail.fr/app/install and wire Plumail into my product. — SDK linked — test environment, dedicated key — On every sign-up, subscribe the contact to the Product list. — Sign-up route wired · double opt-in active — Campaign sending will remain subject to your approval

What you will be able to ask

Six examples to copy, from the first draft to domain health.

Campaigns

Send the welcome email on every confirmed sign-up.
Trigger the announcement campaign when I publish a new release.

Subscribers

Subscribe new customers to the Product list, with double opt-in.
Cleanly unsubscribe deleted accounts, everywhere.

Domain & deliverability

Use my dedicated sending subdomain for transactional email.
Surface bounces in my monitoring tool.

Connected in 3 steps

  1. Copy the prompt at the top of the page and hand it to the agent working on your code.

  2. It will read the guide, add the SDK and wire a test-environment key.

  3. You verify in the test environment, then switch to the production key: it's in place.

What the agent will be able to do

  • Send your transactional email: welcome, confirmation, reset.
  • Subscribe and unsubscribe contacts from your code, double opt-in included.
  • Trigger prepared, approved campaigns, on your rules.
  • Separate test and production with per-environment keys.
  • Surface statistics and bounces in your own tools.

What it will never do

  • Spend your sending credits without your explicit confirmation.
  • Trigger a real send without your approval in Plumail.
  • Read or modify any workspace other than the one you authorised.
  • Bypass double opt-in or unsubscribe lists.

Connection details

SurfaceSDK + REST API, in your code
ConnectionPer-environment API keys (test / production)
ScopeOne workspace per key, permissions chosen at creation
RevocationRotate or revoke the key, effective immediately

Useful access, clear limits

One workspace per authorisation

Each connection is tied to a single Plumail workspace: your other brands or clients stay invisible to the agent.

Sending stays a human act

The agent drafts, tests and schedules; the actual launch of a campaign will always be approved in your Plumail workspace.

Instant revocation

One click in your settings will cut the agent's access, remotely, without breaking anything else.

Frequently asked questions

The day your product speaks email, everything will be ready.

And when the day comes, one line will do:
Read plumail.fr/app/install and connect Plumail for me.