Give ChatGPT or Claude the Momo Business access required for a defined task, then verify the result before widening that access. Momo's connection approval separates business areas from additional actions such as sending, publishing and deleting. Your own Momo permissions remain the limit on what the connection can do.
This guide covers personal connections approved through Momo's sign-in screen. It also explains how those differ from workspace credentials issued under AI connections.
Prepare a specific task and your own account
Start with a task such as “Summarize yesterday's missed calls” or “Read our published message flow and suggest improvements.” Decide which business information the assistant needs and whether it needs to change anything.
Use your own Momo account and check that you are in the intended workspace. You need the relevant Momo role permissions and an assistant account that allows custom connections. Follow the connection setup guide to add your workspace's public HTTPS MCP endpoint. Complete sign-in on Momo; keep passwords and connection credentials out of chat messages.
OpenAI currently documents Developer mode under Settings → Security and login, followed by adding the MCP connection in Plugins. Availability depends on account and workspace policy. Consult OpenAI's current connection guide if your interface differs.
Claude documents custom connections under Customize → Connectors. For Team and Enterprise, an owner first adds the connector for the organization, then members connect individually. See Claude's custom connector guide.
Choose business areas on Momo's approval screen
At Connect [app name]?, check the signed-in person and workspace before reviewing What should it be able to help with? Remove business areas that are unnecessary for your task.
For missed-call analysis, Calls gives access to relevant call information within your existing permissions. Inbox is a separate area for customer conversations. Messaging, Inbox, Comments and WhatsApp groups begin unticked on the consent screen, so access to those customer conversations is an explicit choice.
Read each area's description. A business-area grant is not always read-only: Contacts, for example, can include creating or editing contacts when your role permits it. Leaving the additional action boxes unticked does not turn every selected area into a strict read-only connection.
Select at least one intended business area. If you do not want to grant access, choose Cancel; do not treat unticking every box and pressing Connect as a way to create a connection with no access.
Review the additional action permissions
Under Allow it to go further?, leave actions disabled until your workflow needs them. These permissions work across the relevant business areas you selected.
| Action | What to consider before enabling it |
|---|---|
| Publish things | Changes that affect live flows, routing or agent behavior |
| Send messages and place calls | Replies, outbound messages or calls to real people |
| Start purchases and ask customers to pay | Purchase or payment-request tasks |
| Delete things | Removal of records or configuration |
| Save and change records | Data-row changes and saved reports |
| Change tables and fields | Changes to the structure used by screens and flows |
Other actions may be offered, including automation setup and answering approvals. Read their descriptions independently. Granting a business area and an action still cannot give the assistant a permission your Momo account lacks.
Worked example: review calls before allowing callbacks
Connect with Calls selected and the additional sending permission disabled. Ask:
“Using Momo Business, summarize yesterday's missed calls. Give the call references and any visible follow-up information. Do not place calls or send messages.”
Check several returned references in Momo's Call History. Confirm the date range and whether the records actually support the stated outcomes. A summary in the assistant's answer is not proof that a callback occurred.
If you later want help placing a specific callback, review the necessary permission separately, identify the exact number and task, and inspect the assistant's proposed action. OpenAI's Developer mode documentation describes write-action confirmation and reviewing tool inputs. Assistant-side confirmations complement Momo's access controls.
Review, narrow or disconnect access
Open Credentials & connections and select Connected apps. Review the app name and displayed grants. These connections belong to you; a colleague's personal connections do not appear here.
Select Disconnect to revoke that app's access for your account. Momo revokes both access and refresh tokens, preventing the app from renewing the same grant. Disconnecting yours does not disconnect a colleague's connection. To establish a narrower grant, disconnect the old one and complete the connection process again with the intended selections.
Removing a connector in Claude's own settings is also documented in its connector guide. Removing access does not undo messages sent or records changed earlier.
Check the right credentials tab
AI connections contains workspace-issued MCP credentials with server selections and presets such as Read only and Builder. Its Revoke action affects that credential, which may be shared by a workspace integration. It is separate from your personal OAuth connection under Connected apps.
If a lookup fails, check the connected person, business-area grant, role permission and whether the connector is enabled in the current chat. If a change fails, inspect the required action permission before widening access. Use the MCP handbook for exact tool requirements.