CONNECT PIPEDRIVE TO MUSE
Set up Pipedrive 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 Pipedrive in Adzviser
In Adzviser, sign in to Pipedrive 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 company. 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 PIPEDRIVE REPORT
Build a pipeline review with explicit status and dates
Build a report you can check
Choose a pipeline and summarize current open deals by stage with counts and value. Request won and lost outcomes in separate tables using the appropriate won or lost date. Keep deal currencies separate and retain pipeline and stage identifiers so similarly named stages in different pipelines are not combined.
Do not infer movement from a current snapshot
A large amount in one stage identifies a review priority but does not prove deals are stuck there. You need relevant stage-change timing or history to evaluate movement. Filtering today’s records by an earlier added date also does not recreate the pipeline as it existed then.
Ask a specific stage-review question
For a stage with high value, ask Muse for compatible deal detail and available stage-change dates. Prepare questions about the next action and expected close timing rather than treating a stage’s total value as a forecast.
Metrics for this report: Deals; Deal value; Deal probability.
Relevant breakdowns: Pipeline ID; Stage ID; Deal status; Deal currency.
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 Pipedrive 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 Pipedrive. List my workspaces and ask which connected company to use. Choose a pipeline and summarize current open deals by stage with counts and value. Request won and lost outcomes in separate tables using the appropriate won or lost date. Keep deal currencies separate and retain pipeline and stage identifiers so similarly named stages in different pipelines are not combined. Use these metrics in compatible reports: Deals, Deal value, Deal probability. Relevant breakdowns: Pipeline ID, Stage ID, Deal status, Deal currency. 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.
