MenuClose
Integrations6 methods, 25 entries

Connect the tools you already use.

Through your own app or key. Review first. Every send gets a receipt.

  1. From Google Calendar: Meeting booked

    Prepare the meeting brief

    A brief on the account and its open items.

    AgentDone
    1. ReadyFrom Google Calendar
    2. WorkingThe agent works
    3. Needs inputYour review
    4. WaitingSlack, one pinned channel
    5. DoneSent
  2. ReviewDefault

    A person approves the exact content and recipient.

    Approved

    Scoped send

    Only after a board manager consents to this pattern.

  3. ReceiptExample

    Post the brief

    Source
    Google Calendar
    Channel
    Slack, one pinned channel
    Approved by
    You
    Done

    SentSlack message 1727690042

Capability index25 entries, by method
Services and generic paths, grouped by how they connect: what each can start, what it can do outward, and whether that is review only or can use scoped send.
ServiceMethodCan startCan do outwardOutward rule
Preset · Your OAuth appYou register an app with the service. BakedBrie signs in through it, with only the scopes you pick.06
Google WorkspaceGmail, Sheets, Calendar, Drive, YouTube
  • Preset · Your OAuth app
  • Watched changes
  • Scheduled check
Drive and Calendar changes. Sheet checks.Sheet row, calendar event, Gmail draft. Gmail send and invitations.Review or scoped send
Microsoft 365Outlook, Teams, Excel, OneDrive, Calendar
  • Preset · Your OAuth app
  • Watched changes
  • Scheduled check
Microsoft Graph changes. Mail and Excel checks.Excel cell, Outlook draft, Teams post. Outlook send and invitations.Review or scoped send
HubSpotContacts, companies, deals
  • Preset · Your OAuth app
  • Signed events
  • Scheduled check
Object events you choose in HubSpot.Create or update records. Notes and tasks. Never HubSpot email.Writes within your limits
NotionPages and data sources you share
  • Preset · Your OAuth app
  • Signed events
  • Scheduled check
Page events, after Notion’s handshake.Add a page. Append a paragraph.Writes within your limits
QuickBooks OnlineInvoices, payments, customers
  • Preset · Your OAuth app
  • Signed events
  • Scheduled check
Invoice and payment events. Unpaid invoice checks.Create or void an invoice. Record a payment. Never emails invoices.Writes within your limits
XeroInvoices, payments, contacts
  • Preset · Your OAuth app
  • Signed events
  • Scheduled check
Invoice and payment events. Unpaid invoice checks.Create or void an invoice. Record a payment. Never Xero invoice email.Writes within your limits
PresetA ready-made definition. You still bring your own app, account, or key.05
SlackYour Slack app, or Add to Slack
  • Preset
  • Signed events
Channel messages become cards. Buttons decide reviews.Post to one pinned channel. Mentions refused.Review or scoped send
Social postsYour WoopSocial account
  • Through WoopSocial
Nothing. Reads post status and stats.Schedules posts through WoopSocial.Review or scoped send
GitHubFine-grained token
  • Preset
Nothing.Opens a pull request. Never merges.After approval
S3 or R2Your bucket and keys
  • Preset
Nothing.Writes finished files to your bucket.After approval
Google Drive filesA folder you choose
  • Preset
Nothing.Saves the finished result as a Doc or file.After approval
Signed eventsThe service signs each event. An unverified event starts nothing.05
Any service that signsSigned JSON to a URL BakedBrie gives you
  • Signed events
A card, a step, or an already consented send.Nothing outward by itself.Starts work only
Stripe
  • Signed events
Signed events.None built in. Use Any HTTPS API.Starts work only
Typeform
  • Signed events
Signed form responses.None built in. Use Any HTTPS API.Starts work only
Calendly
  • Signed events
Signed booking events.None built in. Use Any HTTPS API.Starts work only
Shopify
  • Signed events
Signed store events.None built in. Use Any HTTPS API.Starts work only
Any HTTPS APIYou declare each permitted call. Nothing else can be called.06
Any HTTPS JSON APIA key, or your OAuth app
  • Any HTTPS API
  • Scheduled check
Changes in a declared read.Declared operations only. The host is pinned. A declared send operation needs scoped send.Writes within your limits
ResendYour key and sender profile
  • Any HTTPS API
Nothing.Sends email from your verified sender.Scoped send only
falYour key
  • Any HTTPS API
Nothing.Generates images or video on your key.Writes within your limits
ReplicateYour key
  • Any HTTPS API
Nothing.Generates images or video on your key.Writes within your limits
LinkedInYour LinkedIn app
  • Any HTTPS API · Your OAuth app
Nothing.The operations you declare.Review, within your limits
Sprout SocialYour app, Advanced plan
  • Any HTTPS API · Your OAuth app
Nothing.The operations you declare.Review, within your limits
Scheduled check and scheduleBakedBrie reads on an interval you set. Changes are not instant.02
Scheduled checkAny declared read
  • Scheduled check
A card, a step, or a consented send, when an item changes.Nothing outward by itself.Starts work only
ScheduleDays and times you set
  • Schedule
A card on the days you set.Nothing outward by itself.Starts work only
MCPYour agent sets it up over MCP. You finish sign-in and consent on the web.01
Claude Code and CodexYour plan, on your computer
  • MCP
Nothing. It sets up the sources above.Runs cards with your Claude or ChatGPT plan.Cannot turn on sending
Review and scoped sendAutomatic sending

Review first. Send on consent.

Review
The default. You approve each outside action.
Scoped send
A board manager consents on the web: one automation, its account, target, recipients, message, limits.
Not by token
API tokens and MCP can read the setting. They cannot turn it on.
Stops and caps
Stop one automation, or the whole board. Each automation caps at no more than 100 a day, 1,000 a month, and 3 per recipient in 30 days. A manager can set lower.
ReceiptExample

Invoice reminder

Automation
Unpaid invoice reminder
Account
Gmail send
Recipient
From the customer’s email field
Message
Saved template
Consent
Revision 4
Outcome
Accepted by provider
An example receipt. Accepted by provider is not proof of delivery.
Setup05 steps

Five steps to a receipt.

  1. Choose a source.A service, or any HTTPS API, and what should start work.Human steps by source
  2. Connect an account, or define an operation.Sign in through your own OAuth app, or add a key and declare each permitted call.In the app Settings, ConnectionsYour OAuth appAny HTTPS API
  3. Choose review, or consent to sending.Review is the default. A board manager consents on the web to scoped send.In the app Board, Automate, Sending settingsAutomatic sending
  4. Test it.Preview the exact request, or run one card in review first.Preview and test call
  5. See the receipt.The exact message, recipient, source, account, and provider outcome.In the app Board, Automate, View receiptsReceipts and stops

Or let your agent do it.

Connect Claude Code or Codex to BakedBrie with a Full control token first. Then paste this.

Connect Claude CodeConnect CodexTokens and the runner
Setup promptSelect to copy
Help me connect {{SERVICE}} to BakedBrie for {{GOAL}} on board {{BOARD}}. Call whoami, then read /docs/recipes/agent-service-setup and the matching service page with read_docs. Check what is already connected before creating anything. Ask me for missing non-secret details only when the next step needs them. Credentials go through prepare_secret from my own environment; never ask me to paste a secret into this chat. Use a preset if one exists. For another API, declare only the operations I approve. Tell me exactly what to register at the service: redirect URL, scopes, callback or webhook. Give me each BakedBrie web link where I sign in, choose an account, set limits or enter a signing secret. For triggers, use only a verified event, managed subscription or scheduled read this service supports. You cannot turn on automatic sending: explain the account, target, recipient field, message and limits, then send me to Board, Automate, Sending settings on the web. Finally read list_send_modes, list_trigger_sources and list_send_receipts and tell me what is live, paused or waiting on me. Never send a test without my approval.

Caveats06

Caveats

  1. Some services need setup on their side: your own app, scopes, admin approval, or a registered callback.
  2. Your Claude or ChatGPT plan runs on your computer. Keep the runner open, or the card shows “Waiting for your computer.”
  3. A connection that uses an API key follows that service’s terms and bills your account there.
  4. A name here is not a claim of a built-in or two-way integration. Each one says how it connects.
  5. “Accepted by provider” means the service took the request. It is not proof of delivery.
  6. Outlook reply checks are best effort. A delayed or deleted reply can be missed, so a follow-up may still send.
Questions04

Questions

  • Is this a built-in integration?

    It is a connection you set up with your own app, account, or key. Each row says how it connects and what it can do.

  • What if my service is not listed?

    Use Any HTTPS API for a JSON API, Signed events if it signs webhooks, or a scheduled check over a declared read.

  • Can my agent turn on sending?

    No. Only a board manager, signed in on the web, can consent. API tokens and MCP can read the setting, never change it.

  • Who pays for the service?

    You do, on your own account there, under its terms. BakedBrie adds nothing.

StartFree

Start with one service.