How to integrate Unify with Claude
To integrate Unify with Claude, find the official Unify connector in Claude’s connector directory and sign in to Unify. The connection exposes Unify’s Agent and supported tools within your authorized workspace. Use it to research accounts, inspect sales context, and develop an outreach plan with an explicit decision before execution.[1][3]
- Connection
- Official MCP
- AI assistants
- Tool
- Claude
- Unify-documented client setup
- Data flow
- Claude ↔ Unify
- Tool calls and returned results
At a glance
- Use the Unify-documented Claude setup
- Use tool calls and returned results instead of an outbound Play payload
- Check the final Agent result before treating the task as complete
When this workflow makes sense
Start with the decision your team needs to make, then choose the connection that supports it.
An account plan becomes stronger when research, the team’s ICP, and the proposed next action remain connected. Claude can organize the conversation while Unify performs the requested sales work. If other connectors supply call notes or documents, label their contribution separately from Unify’s records. A persuasive synthesis should still let a rep tell what was observed, what was inferred, and what needs checking.
A good fit when
Teams already working in Claude who want account research and authorized Unify actions alongside their other connected business context.
Reconsider the plan when
The official Claude connector and the Claude Code plugin have different setup paths. Team or Enterprise administrators may need to enable connector access first.
Design the handoff
Use this framework to agree on the input, the next action, and who owns the result.
Suggested workflow design, based on the documented capabilities below.
| Stage | Decision to make |
|---|---|
| Client and account | Claude web or Desktop access and permission to enable the official Unify connector |
| First task | Suggested prompt: “Use Unify to assess example.com against our ICP. Separate observed account facts from your interpretation, then propose questions for the rep. Do not launch a Sequence.” |
| Execution | Define whether the request is research-only or includes a specific authorized action. Keep the run ID for follow-up. |
| Result | Review the final output and unresolved questions before using the result in a sales decision. |
Explore the scenarios
Choose the situation that fits your team and work through the proposed plan.
Open a scenario to explore its plan. Checklists track your selections in this page only.
Prepare a focused account discussion
A rep wants a short brief before deciding whether an account deserves outreach.
Keep account facts, fit assessment, and suggested questions separate.
- Name a company and the relevant ICP criteria
- Ask Unify for research through Claude
- Review the evidence and choose the next human decision
Combine call context with account research
A connected call tool or document contains context that could improve a proposed sequence.
Use each source for what it actually establishes and review the outreach before enrollment.
- Identify the authorized call notes or document
- Compare that context with the Unify account research
- Request a draft that preserves the source distinctions
Illustrative workflow, not a preconfigured automation. Complete these checks in your own account.
Define success before launch
Inspect the data and the intended outcome separately. Connection status is only the first check.
Expected, not tested
After the connection is authorized, Claude can identify the intended Unify user and retrieve the completed output of the controlled research task.
Inspect get_me, the requested task, the final run status, and read_agent_results together. A discovered tool or a run ID confirms a different stage from a completed result. For any explicitly requested write, inspect the actual destination record as well.
Documentation-based reference. This workflow has not been tested end to end. Use a record or event you control before enabling live activity.
Questions answered
Common decisions when connecting Unify and Claude.
How do I connect Unify to Claude?
Unify’s guide names Settings → Extensions → Browse extensions. Anthropic’s current help uses Customize → Connectors and the + directory control. In the directory available to your account, search for the official Unify connector.[1][3]
Is the Claude connector the same installation as Claude Code?
No. Unify documents its connector for Claude Desktop and claude.ai, and a separate official plugin for Claude Code. Use the instructions for the client you actually run.[1][2][3]
How is MCP different from a Play webhook?
An MCP client can invoke Unify tools and retrieve their documented results. The Play Webhook action sends an external request and does not pass its response into downstream Play steps. They are separate connection mechanisms.[2][5]
Does a run ID mean the task succeeded?
No. run_agent starts background work. Check the run with poll_agent, handle any clarification, and call read_agent_results after the run reaches READY or ERROR.[2]
Limits & decisions
Check these boundaries before designing a live workflow around the connection.
- The official Claude connector and the Claude Code plugin have different setup paths. Team or Enterprise administrators may need to enable connector access first.[1][3]
- Unify permissions and Agent usage limits still apply[1][2]
- A completed research result does not itself authorize sending, enrollment, or CRM updates
- No authenticated end-to-end execution has been performed
What the connection supports
Understand the connection, the data involved, and the behavior that matters for a Unify + Claude workflow.
The assistant requests work from Unify and retrieves its result using the connected user’s permissions.
| Decision | What to know |
|---|---|
| Connection route | Unify explicitly documents Claude setup[1] |
| Client requirement | Claude web or Desktop access and permission to enable the official Unify connector[1][3] |
| Published server | https://mcp.unifygtm.com/mcp (authentication required)[4] |
| Identity | Calls are scoped to the authenticated Unify user and tenant[2] |
| Agent lifecycle | Start a run, poll status, answer clarification, and read the terminal result[2] |
| Usage | Unify MCP Agent work uses existing Unify Chat usage and credits[1] |
MCP exposes tool schemas to the client. For Agent work, provide a natural-language prompt and retain the returned runId for status and result calls. Direct API tools have their own required inputs. This connection is separate from a Play’s outbound Webhook action and does not make webhook responses available to later Play steps.
Technical setup reference
References and requirements for the Claude connection.
Connection requirements and setup checklist
Before connecting
- Claude web or Desktop access and permission to enable the official Unify connector
- A Unify user with access to the intended workspace and available Chat credits for Agent runs
- One controlled research task with a clear output and explicit boundaries on record changes
Enable Unify for the conversation
Use the conversation’s connector controls to enable Unify. Start with one company or a clearly bounded research question so you can inspect the returned context.[3]
Check the Agent result
For Agent work, run_agent returns a runId before the task finishes. Poll that run. Answer every returned question if its status is CLARIFICATION_NEEDED. On READY, read_agent_results returns the completed output; on ERROR, inspect the reported failure.[2]
Troubleshooting
Start with the stage where the expected data or action stops appearing.
The client cannot find or authorize Unify
Check the official installation path for this client, workspace policy, and required account connection. Restart clients where Unify’s setup calls for it, then repeat sign-in.[1][3]
A run starts but no result appears
Keep the original runId and poll its status. PENDING is still running; CLARIFICATION_NEEDED requires answers; READY permits reading the result. Use list_agent_runs to find a previous run rather than starting duplicate work.[2]
The tool reports missing access or unavailable credits
Verify the connected user and workspace. Unify scopes tools to that user, and Agent runs require available Chat funding and are subject to rate limits. A table owned by another user is not accessible through load_datatable.[2]
Sources & review
Official documentation reviewed on September 16, 2026.
Technical claims link to primary documentation from Unify and the destination tool. Scenarios, field choices, and recovery plans are editorial implementation examples. Documentation review is separate from execution testing.
Documentation reviewed; end-to-end execution not tested. No named technical reviewer has signed off on these articles yet.
Content updated: . Report a correction to Unify with the tool name, source URL, and behavior you observed.
Keep exploring
