Claude + Revenue Force
Add Revenue Force as a custom connector in Claude and work your workspace conversationally, scoped to your workspace.
Works the motion through your AI, on your permissions
Bring your AI into the workflow with scoped, permissioned access. Through the gateway, Claude can read your workspace, propose actions, and carry out the ones your permissions allow: import an audience, enroll contacts, review and approve drafts, always inside the same guardrails as the console. It works your motion; it does not run your business.
Claude in, execution under your rules, outcomes back to you.
Reads your workspace
Proposed first, carried out only on your permissions.
What flows in
Into Claude through the gateway MCP: a read-only view of your campaigns, approvals, and contacts, scoped to your workspace.
- Claude reads your campaigns, approvals, and contacts through the gateway MCP
- Ask it to import contacts, check performance, or review pending approvals
What flows back
From Claude back into Revenue Force: permissioned actions, proposed first and governed by the same permissions as the console.
- Claude proposes first, then carries out permissioned actions: import an audience, enroll contacts, approve a pending draft
- Every action is governed by the same permissions as the console
Connected in a couple of minutes.
Your AI already knows your business. Now bring it into the workflow. The gateway MCP is scoped to your workspace and governed by the same permissions as the console.
Open Claude and add Revenue Force as a custom connector
Sign in to authorize your workspace via OAuth
Ask Claude to work your pipeline: it is scoped to your workspace only
Your account. Your workspace. Your call.
Claude connects over OAuth and operates strictly inside your console permissions: it reads what you allow, proposes actions, and carries out only what you have permitted. The connection is scoped to your workspace and revocable in one click.
It acts only on your permissions
Your AI reads what you allow and proposes actions first. It carries out only what your console permissions permit, nothing more, and every action is logged.
Scoped to your workspace only
Your account, your token, your data. A connection lives in one workspace and is never shared across tenants.
Disconnect in one click
Change your mind anytime. Disconnect and the stored credential is cleared immediately. No email, no waiting.
Human approval is the default starting point. Revenue Force proposes, you review, and autonomy increases only when you choose, connection by connection. You set the pace.
Everything a careful buyer should ask.
How does Claude connect?
Add Revenue Force as a custom connector in Claude and authorize your workspace over OAuth. Claude then operates through the gateway MCP.
What can Claude do?
Check campaigns, import contacts, review and approve pending drafts, and enroll contacts: anything the console permissions allow, conversationally.
Is it limited to my workspace?
Yes. The connection is scoped to your workspace and governed by the same permissions as the console. Disconnect any time.
Ready to run Revenue Force on Claude?
Book a revenue audit to see how Claude works your motion through the gateway: what it can read, what it can propose, and which actions stay behind approval.