Skip to main content
OrbitForms is available as a connector for Claude. Once connected, Claude can search and update your contacts, read your forms and their latest submissions, check a host’s availability and book meetings, review and run email sequences, and manage webhook subscriptions. Every connection is scoped to one team and the permissions you approve, and Claude asks before running any tool that sends email, books or cancels a meeting, or delivers data to an external endpoint.

​
Before you connect

  • An OrbitForms account on an active plan or trial. Start a trial if you do not have one.
  • At least one form, contact, or scheduling page in the team, so there is something to work with.
  • Sequence tools require a plan that includes sequences; booking tools work best when the host has a connected calendar in Settings → Email & Calendar.

​
Connect from the Connectors directory

  1. In Claude, open Customize → Connectors and search for OrbitForms.
  2. Choose Connect. Claude opens the OrbitForms consent screen in a new window.
  3. Sign in to OrbitForms if asked, then pick the team Claude may access and review the permissions.
  4. Choose Authorize. Claude returns to the conversation with OrbitForms connected.
Tokens refresh automatically. You can revoke access at any time by removing the connector in Claude or revoking the connected application in OrbitForms.

​
Connect as a custom connector

If your organization installs connectors by URL, use:
In Claude: Customize → Connectors → Add custom connector, paste the URL, choose Sign in now, and follow the same consent flow. No client ID or secret is needed: OrbitForms supports Client ID Metadata Documents and Dynamic Client Registration, so Claude registers itself.

​
Connect from Claude Code

Run /mcp inside Claude Code to complete sign-in and check the connection status. Claude Code redirects to a local address during sign-in; the consent screen tells you so.

​
What you can ask

“Who submitted the Demo Request form this week, and which companies are they from?”
“Find the contact for [email protected], tag her as a customer, and add her job title.”
“Is Marcus free for a 30-minute intro call on Thursday afternoon? Book the first open slot with [email protected].”
“How is the Demo follow-up sequence performing, and who is still active in it?”
“Enroll every contact tagged webinar-2026 in the Demo follow-up sequence.”
“Send new qualified submissions to https://hooks.example.com/orbit.”

​
What the connector can do

Read tools run without a confirmation. Tools that change data are annotated so Claude confirms before, for example, booking a meeting (sends invites), enrolling contacts in a sequence (starts email sends), or cancelling a meeting (notifies the attendee).

​
Not included in the Claude connector

Deleting forms, submissions, contacts, meetings, or sequences, and managing team members or billing, are not available through Claude by design. Use the OrbitForms app or the REST API for those.

​
Permissions

The consent screen lists every permission Claude asks for and names the host you will be returned to. Permissions cover a single team; connect again to grant another team. See MCP Server for the scope list and revocation options.

​
Troubleshooting

  • “Couldn’t reach the MCP server”: confirm you used https://orbitforms.ai/api/mcp/claude with no trailing path or query string.
  • A tool says a permission is missing: Claude will prompt you to re-authorize with the extra permission. Accept it, and Claude retries the same call.
  • No submissions or meetings appear: tools only see the team you picked on the consent screen. Remove the connector and connect again to switch teams.
  • Booking returns 409: the slot was taken between lookup and booking. Ask Claude to fetch slots again and pick another.
  • Still stuck? Email [email protected] or use the contact form.