How to integrate Unify with Perplexity
The proposed Unify and Perplexity integration uses a custom remote MCP connector. Perplexity documents remote connector support, and Unify publishes its MCP server address, but Unify’s getting-started guide does not list Perplexity as a supported setup. Confirm OAuth compatibility with Unify before using this path for account research or sales actions.[1][3][4]
- Connection
- Custom MCP
- AI assistants
- Tool
- Perplexity
- Model Context Protocol
- Data flow
- Perplexity ↔ Unify
- Tool calls and returned results
At a glance
- Confirm this custom client with Unify before connecting
- 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.
Public research and private account context answer different questions. Perplexity can provide a research conversation, while an authorized Unify connection could supply the business context behind an account. The first decision is whether that connection can authenticate in your account. After that, keep web evidence separate from Unify records so a public mention does not become an invented CRM fact.
A good fit when
Teams that use Perplexity for account research and can first validate the custom connector with their Unify account team.
Reconsider the plan when
Remote MCP support in Perplexity does not establish a tested Unify connector. Unify-specific OAuth registration, tool access, and the complete run lifecycle remain to be confirmed.
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 | An eligible Perplexity account with custom remote connectors enabled, plus confirmation from Unify of the client authentication setup |
| First task | Suggested prompt: “After confirming the Unify connection, research example.com. Separate public web evidence from Unify account facts and identify what remains unknown. Do not modify records.” |
| 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.
Separate public evidence from private account context
A researcher wants to compare a company’s public positioning with authorized Unify context.
Validate access first, then label each source of information in the resulting brief.
- Confirm the custom connector can authenticate and discover tools
- Request a narrow account review
- Compare public sources and Unify findings without merging uncertain facts
Check an incomplete research request
The assistant has started a Unify run but has not produced its final findings.
Keep the run ID and retrieve the final result instead of inferring success from a connected status.
- Inspect the run status through the available tools
- Answer any clarification using the returned questions
- Read the terminal result and note any error
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, Perplexity 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 Perplexity.
How do I connect Unify to Perplexity?
First confirm the custom client and authentication setup with Unify. Then follow the client’s documented MCP configuration and verify identity and tool access before requesting work.[1][3]
Is Perplexity listed in Unify’s official client setup?
No. The reviewed Unify guide lists Claude, Claude Code, Cursor, ChatGPT, and Codex, and directs other clients to the Unify account team. This page describes a conditional custom connector path.[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.
- Remote MCP support in Perplexity does not establish a tested Unify connector. Unify-specific OAuth registration, tool access, and the complete run lifecycle remain to be confirmed.[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 + Perplexity workflow.
The assistant requests work from Unify and retrieves its result using the connected user’s permissions.
| Decision | What to know |
|---|---|
| Connection route | Custom client support must be confirmed with the Unify account team[1] |
| Client requirement | An eligible Perplexity account with custom remote connectors enabled, plus confirmation from Unify of the client authentication setup[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 Perplexity connection.
Connection requirements and setup checklist
Before connecting
- An eligible Perplexity account with custom remote connectors enabled, plus confirmation from Unify of the client authentication setup
- 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
Configure the custom remote connector
Open Account settings → Connectors → + Custom connector → Remote. Enter the confirmed Unify MCP URL, choose Streamable HTTP, and use the OAuth configuration approved for this client. Click Add, then open the connector to authenticate. Organization policy may restrict this setup.[3][4]
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 custom connector availability and the OAuth client requirements with Unify. Do not substitute another client’s OAuth identifiers, disable authentication, or assume a public server URL grants access.[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
