Integration
Run Salesforce Marketing Cloud from Claude.
Orbit connects Claude to SFMC over its REST API. Claude reads and builds your Content Builder email templates, reads your journeys, and fires transactional proofs — from the same chat where you plan the work. Here's exactly what that covers in v1, and what it doesn't.
You ask Claude to tighten the copy on a welcome email. Normally that's a round trip: describe the asset, copy the HTML out of Content Builder, paste it into a chat, paste the result back. With SFMC connected, Claude reads the asset straight from Content Builder, rewrites it, and writes the new version back — no clipboard tennis. It's the difference between an assistant that describes your SFMC and one that operates it.
What Orbit does with SFMC today.
SFMC v1 is REST-only. That's a deliberate line: everything below runs against Salesforce's public REST endpoints. The two rows marked Not in v1aren't missing because the platform can't do them — they're missing because they live behind SOAP, and a SOAP client is its own project. We'd rather tell you that than fake it.
Connect & authenticate
Live in v1Minting an OAuth2 token is the auth check — it also validates your subdomain and business unit.
List email templates
Live in v1Reads your Content Builder assets, filtered to email (the htmlemail asset type).
Get a template
Live in v1Pulls a single Content Builder asset by ID, HTML included.
Create / update templates
Live in v1Builds a new htmlemail asset or updates an existing one in Content Builder.
Read journeys
Live in v1Lists and reads Journey Builder interactions. Needs the Automation | Journeys | Read scope on the package.
Transactional test send
PartialSends a proof through the Transactional Messaging API — but it needs a send definition set up first, so it's not a one-call proof the way it is on other ESPs.
Query data extensions & subscriber lists
Not in v1SFMC exposes these through SOAP, not clean REST. Orbit v1 is REST-only, so this is deferred — not faked. Read journey entry sources for related metadata in the meantime.
Send-level performance metrics
Not in v1Send stats live in SOAP Tracking Events and extracts — no simple REST aggregate. Deferred with the SOAP client; use SFMC's in-app reports until then.
How to connect it.
SFMC uses server-to-server OAuth. In SFMC, create an installed package with API integration, then hand Orbit four things — three required, one optional. You'll find them under Setup → Installed Packages.
sfmc_client_idRequiredThe Client Id from your installed package's API Integration component.
sfmc_client_secretRequiredThe Client Secret from the same component. Stored encrypted; it never leaves your machine in plain text.
sfmc_subdomainRequiredThe tenant string from your Authentication Base URI — the https://<subdomain>.auth.marketingcloudapis.com part. Orbit uses it to mint tokens and read the correct REST instance URL back.
sfmc_account_idOptionalA business-unit MID, if you want Orbit to operate inside a specific business unit rather than the package's default.
One scope note that saves a support ticket: give the package Content Builder read/write and Automation | Journeys | Read. Miss the journeys scope and journey reads come back as an opaque 403 rather than data. Orbit names the missing scope when that happens, but it's faster to grant it up front.
Works with every ESP. Deepest on Braze.
Orbit's template, journey, and proof-send tools are ESP-neutral — SFMC is one of six platforms they speak to. But some tools are built around Braze-only concepts and stay Braze-only, honestly labelled: Content Blocks, Canvas creation, the media library, and the deliverability export shapes don't have SFMC equivalents, so they don't pretend to.
If Braze is your primary platform, that's where Orbit goes deepest. If SFMC is, you get the REST surface above — real, scoped, and growing. The full platform-by-platform breakdown is on the compare page →.
The rest of Orbit comes too.
The SFMC connection is one part of the box. The portable layer works regardless of which ESP you're on: 66 skills carrying production-tested lifecycle protocol, 99 tools, an MJML-to-HTML pipeline, a render-and-QA gate that catches the dark-mode and clipping bugs before you send, and the segmentation and sample-size calculators. Claude reaches for whichever the task needs.
None of it is SFMC-specific, and none of it is behind a subscription — it's the same operator's toolkit whether you build in Content Builder or anywhere else.
Try it.
Orbit is a one-off purchase — $124.50 during the launch window, $249 after. One payment, every skill and tool included, no seats and no subscription. Connect your SFMC installed package and Claude starts operating Content Builder the same afternoon.
Frequently asked.
What can Orbit actually do with Salesforce Marketing Cloud today?
Over SFMC's REST API, Orbit lets Claude read and build Content Builder email templates (the htmlemail asset type), read your journeys, and send a transactional test through the Transactional Messaging API. It does not query data extensions or pull send-level performance in v1 — those live behind SOAP, which Orbit's SFMC client doesn't speak yet.
Why can't Orbit read my data extensions or send performance?
Because SFMC exposes those through its SOAP API, not clean REST endpoints — data extensions, subscriber lists, and Tracking Events are all SOAP-first. Orbit v1 is REST-only by design; a SOAP client is a project, not a small addition. It's deferred to a later version rather than shipped half-working, so you always know what a result means.
What credentials do I need to connect SFMC?
An installed package in SFMC with server-to-server OAuth: a client ID, a client secret, and your authentication subdomain (the string in your Authentication Base URI). Optionally a business-unit MID. Grant the package Content Builder read/write and Automation | Journeys | Read so template and journey calls don't come back as permission errors.
Is SFMC the right ESP for running lifecycle from Claude?
If your team lives in Content Builder and Journey Builder and you want Claude to build and revise email assets in place, yes — that's exactly the REST surface Orbit covers. If your program leans on data-extension segmentation and pulling send stats programmatically, wait for the SOAP work or run those legs in the SFMC UI. Orbit is deepest on Braze; SFMC is a real, scoped integration, not a checkbox.
Do I need to be technical to use it?
No. You talk to Claude the way you already do. The one setup step is pasting your installed-package client ID, secret, and subdomain — a few minutes in SFMC's Setup, once. After that Claude reaches for the SFMC tools when the work calls for them.