The work is larger than one question: research every signup, prepare every meeting brief, or review the accounts that went quiet. Cowork handles the sequence; Pathbound supplies a current, identity-resolved profile for each customer it touches.
Cowork is the handoff layer for operational work. Connect Pathbound once, then give Cowork an outcome that requires customer profiles, timelines, files, and several tool calls.
A shared customer record underneath a multi-step task, so Cowork does not rebuild the join between CRM, support, email, and website data for every account.
Background work that can continue while you do something else, with results returned as documents, spreadsheets, or updates through allowed tools.
The same remote Pathbound connector used in Claude chat, enabled inside Cowork without another customer-data integration.
A path from a proven prompt to a reusable Cowork skill or plugin for the rest of the team.
Cowork uses remote connectors configured through your Claude account. If Pathbound is already connected in Claude, enable it in Cowork. Otherwise, add the same remote endpoint from Customize and complete OAuth.
Open Cowork and start the task or project where you want to use customer data.
Open Customize → Connectors and enable Pathbound for the task.
Give Cowork the outcome and name the evidence it should read from Pathbound before it acts.
Review any requested write actions before approval.
Open Customize → Connectors and select + → Add custom connector.
Enter https://mcp.pathbound.ai/mcp and add the connector.
Select Connect, sign in to Pathbound, and approve the OAuth request.
Enable Pathbound for the task, then start with a reviewed one-off run before scheduling or packaging the workflow.
Once connected, these are real jobs Claude Cowork runs against your customer data. Each recipe is one tested prompt—paste it and go.
Run our weekly churn diagnostic. Compare every account’s activity this week against last week and list the accounts that dropped the most, went fully quiet, or spiked. For each account that cooled, pull its details and read its recent conversations—support threads, failure alerts, email that went cold—and give me a one-line reason why. Leave a note on each flagged account with the read and the suggested next step, then give me the digest: what moved, why, and the three accounts I should call today.See the full recipe—Weekly churn diagnostic
More jobs in use cases, each with a tested prompt.
No. Remote connectors are configured through your Claude account. Enable Pathbound for the Cowork task from Customize → Connectors.
Use Cowork when the job has several steps, many customers, files to produce, or a cadence you expect to repeat. Use Claude chat for an answer you need in the current conversation.
Yes. The setup is a remote connector and OAuth; the task itself can be written in plain language. An operations owner should define the first workflow and review its reads and writes before sharing it more broadly.
Yes, where scheduled tasks are available in your Cowork account. Test the prompt as a one-off task first, keep the initial run read-only where possible, and review the output before moving it onto a schedule.
Only the Pathbound write tools allowed by the connected sources and credential. A workflow can create a note or update a permitted field when those tools are available. Versioning and rollback are not live yet.
Cowork is for operational work expressed as an outcome. Claude Code is for engineers working from a terminal, repository, or IDE with its own MCP configuration.
Sign up, connect one CRM or drop the events snippet, and point your MCP client at mcp.pathbound.ai/mcp.
