CONNECT ZOHO CRM TO MUSE
Set up Zoho CRM reporting in Muse
Adzviser retrieves the source data through its MCP reporting tools. Muse uses those results to answer your questions. Connect the source in Adzviser, then authorize Muse to use that connection.
Connect Zoho CRM in Adzviser
Select your Zoho CRM region, sign in to Zoho, and allow Adzviser to read its reporting data. Add the source to the workspace you want to use in Muse.
Open Adzviser setup →Authorize Adzviser in Muse
Open Muse.ai and send: “Can you connect to custom Adzviser MCP at https://mcp.adzviser.com/http?” Select Connect on the Adzviser card, sign in to Adzviser, and select Complete Authorization via MCP. Return to Muse.
https://mcp.adzviser.com/httpVerify the first result
Ask Muse to list your Adzviser workspaces and their sources. Choose the workspace and confirm the organization. Request a small report for a known period before expanding the analysis.
The Adzviser reporting connection is read-only. It can retrieve data for analysis; it cannot edit source records or campaigns.
A USEFUL FIRST ZOHO CRM REPORT
Review pipeline amount and expected revenue separately
Build a report you can check
Choose the connected organization and request current deal counts and amounts by stage. In a separate compatible view, include probability and expected revenue for the deals you want to inspect. Use closing date when discussing the expected closing period and creation date when discussing newly added pipeline.
Make the probability assumption visible
Expected revenue depends on the probability attached to a deal or stage. It is a weighted estimate, not booked sales. Ask Muse to show the relevant amounts and probabilities before interpreting a change, and avoid averaging probabilities across deals without considering their different values.
Build a closing-period review
Ask Muse which open deals are assigned to the period you select and identify the largest amounts. Return the available stage and next-step context so the sales team can verify timing. Label any missing closing date or probability rather than supplying a guessed value.
Metrics for this report: Deals; Deal amount; Deal probability (%); Deal expected revenue.
Relevant breakdowns: Deal stage; Closing date; Deal name.
These are starting fields, not a promise that every combination belongs in one report. Use separate requests for different reporting levels and check the full field catalog for additional coverage.
COPY INTO MUSE
Run your first Zoho CRM analysis
Paste this after connecting. Change the period or research subject to match your question, and let Muse confirm the selection before retrieving results.
Use Adzviser to analyze Zoho CRM. List my workspaces and ask which connected organization to use. Choose the connected organization and request current deal counts and amounts by stage. In a separate compatible view, include probability and expected revenue for the deals you want to inspect. Use closing date when discussing the expected closing period and creation date when discussing newly added pipeline. Use these metrics in compatible reports: Deals, Deal amount, Deal probability (%), Deal expected revenue. Relevant breakdowns: Deal stage, Closing date, Deal name. Check field compatibility and use separate tables for different reporting levels. State the actual reporting dates or observation window. Show the supporting rows, then give a short conclusion and one next investigation. Label missing data and separate observed changes from possible explanations.
