Zoho Bigin + Muse
Connect Zoho Bigin to Muse
Prepare a grounded pipeline briefing
Read deals with Muse and Agent200. Prepare a pipeline briefing using the connected user’s own Zoho Bigin account.
On this page
Overview
Use Muse to prepare a short pipeline briefing for review. Put the Agent200 key in Muse’s secure credential interface, then inspect the source before sharing the result.
Start with one identified deal. Preserve returned deal stage, contact and company fields; report missing data and keep the workflow read-only.
Provider reference: Zoho Bigin API.
- Connector
- Zoho Bigin
- Works with
- Muse · Agent app, through MCP
- Authentication
- Managed OAuth, per end user
- You need
- An Agent200 API key
- Tools
- 5 tools
- MCP server
https://api.agent200.com/mcp/
Before you start
- An Agent200 API key. Create one on the API keys page of the dashboard.
- Zoho Bigin enabled for your project. In the dashboard's Connectors settings, with the endpoints and scopes your agent needs.
- An end user with a Zoho Bigin account. They approve access once, on Zoho Bigin's own page.
- Muse, with custom MCP servers allowed. Muse creates custom connectors from a chat, and your key goes into its secure credentials sheet, never into the chat. Muse Code reads servers from its settings file.
Connect Zoho Bigin to Muse
-
1
Step 1: Create your Agent200 API key
Create a key on the API keys page and store it securely.
.envConceptual exampleStore the Agent200 API key as an environment variable # Keep the key out of your code, prompts and chats. export AGENT200_API_KEY="paste-your-key-here" -
2
Step 2: Create the custom connector
Connect to
https://api.agent200.com/mcp/over Streamable HTTP with an Authorization: Bearer header. Enter the key in Muse’s secure credential interface.Muse chatMCP: message that asks Muse to create the custom connector Create a Custom Connector for the Agent200 remote MCP server and connect to it: Name: Agent200 Transport: remote streamable HTTP URL: https://api.agent200.com/mcp/ Auth: API key sent in the Authorization header as "Bearer <key>" Open the secure credentials store so I can enter the API key there, not in this chat. Then list its tools to confirm the connection works. -
3
Step 3: Inspect read tools
Confirm the Zoho Bigin operations and schemas advertised by the connection.
-
4
Step 4: Authorize Zoho Bigin
Connect the intended user and test one accessible deal.
Test your connection
Run one request to check everything is wired up.
Ask
Read the Zoho Bigin deal I identify and prepare a pipeline briefing. Name the source and use only deal stage, contact and company fields. State access gaps; do not change records.
What should come back
- The selected deal is identified.
- Only the returned deal stage, contact and company fields are reported.
- Access gaps and missing context are explicit; no source data is changed.
Check the selected deal ID, account scope, read permission and pagination. Bigin modules can be renamed and fields customized. Check the organization and module before interpreting a stage.
Get your API key
Create a key in the Agent200 dashboard. It reaches Zoho Bigin and every other connector enabled for your project.
Instructions for AI agents
Using a coding agent? Paste this brief into it, or give it the address of this page. It lists what to do, in order, to connect Zoho Bigin to Muse.
Goal: connect Zoho Bigin to Muse with Agent200, through its MCP server. Guide: https://www.agent200.com/connectors/zoho-bigin/framework/muse/ 1. The user needs an Agent200 API key. If they have none, send them to https://agent200.com/platform/apikeys/ to choose "Create an API key". They paste it into Muse's settings themselves: never ask for it in chat and never write it into files you share. 2. Make sure Zoho Bigin is enabled for their project in the Agent200 dashboard (Connectors), with the tools the task needs. 3. Add Agent200's MCP server to Muse: URL https://api.agent200.com/mcp/, transport streamable HTTP, header "Authorization: Bearer <the user's Agent200 API key>". Follow the setup steps on the guide page for Muse's exact menus or commands. 4. The first Zoho Bigin request returns an authorization link if the user has not connected Zoho Bigin yet: show it to them and continue once they have approved access on Zoho Bigin's own page. 5. Check it works with this request: "Read the Zoho Bigin deal I identify and prepare a pipeline briefing. Name the source and use only deal stage, contact and company fields. State access gaps; do not change records." What should come back: - The selected deal is identified. - Only the returned deal stage, contact and company fields are reported. - Access gaps and missing context are explicit; no source data is changed. 6. If a tool is missing or a call is refused, check the project's Connectors settings in the dashboard and the access the user granted in Zoho Bigin, then retry.
The whole guide is also available as Markdown, for agents and LLMs: /connectors/zoho-bigin/framework/muse.md
Zoho Bigin tools Muse can call
-
List contacts
Readzoho_bigin_list_contactsFind contacts in the authorized Bigin organization.
-
Read a contact
Readzoho_bigin_get_contactRetrieve one contact by its record ID.
-
List deals
Readzoho_bigin_list_dealsFind deals in an accessible pipeline.
-
Read a deal
Readzoho_bigin_get_dealRetrieve one identified deal and its returned stage.
-
List companies
Readzoho_bigin_list_companiesFind associated company records.
No tool matches that search.
How it works
-
01
You ask Muse
In your own words, for something in Zoho Bigin.
-
02
Muse picks a tool
It sees the Zoho Bigin tools on the Agent200 MCP server and calls the one the request needs.
-
03
Agent200 runs the call
With your own Zoho Bigin connection, within the tools and scopes your project allows.
-
04
Muse answers
It gets the result back from the MCP server and uses it in its reply or its next step.
Each user's own connection. Connections belong to individual end users. A request for one user never reaches another user's Zoho Bigin account.
Permissions at every level. Your project settings decide what the agent may request, the end user decides what they authorize, and Zoho Bigin enforces what its API grants.
Troubleshooting
The source cannot be read
Check the selected deal ID, account scope, read permission and pagination. Bigin modules can be renamed and fields customized. Check the organization and module before interpreting a stage.
FAQ
How do I verify this result?
Compare the named deal and returned deal stage, contact and company fields with the source. Treat missing information as missing, not as a fact.
