Claude Unify connectorWhat Claude can do in your Unify account.
The Claude Unify connector exposes 50 tools. 23 read your go-to-market data, 27 change it: records, Sequences, enrollments, tasks, and runs of Unify's own Agent. Below: what Claude can check, what it can launch or delete, and what limits it.
Verified Trustpilot reviews · AI, automation & growth agency
What it changes for an outbound team
Instead of switching to Unify Chat, you ask Claude. It can hand the task to Unify's own Agent, the one behind Unify Chat, or work directly on your records, Sequences and tasks. Unify states that anything you can ask Unify Chat, you can ask through the connector, with the same credits.
Qualify an account without leaving the chat. run_agent starts a research run on a company, poll_agent tells you when it is done or needs an answer, and read_agent_results brings the verdict back.
Keep cadences under control. list_sequence_enrollments shows who is in which Sequence, pause_sequence_enrollment holds one prospect who asked for a break, and create_sequence_enrollment adds a new contact after a good call.
Tidy the data. upsert_object_record creates or updates a record without duplicating it, and update_task hands a sick colleague's tasks to someone else.
What the sheet does not tell you. Twenty-seven of these tools change your workspace, including deleting objects, records and Sequences, and an Agent run keeps working in the background once started. Each run spends your Unify chat credits. Claude only reaches what your own Unify user can see. And nothing is triggered by an event: no tool wakes up when a reply lands. For event-driven flows, an automation tool does that job; the Integrations hub covers it.
The vocabulary in one minute
Five words you will run into while plugging Unify in.
- Connector
- The link you set up once between Claude and an account you already use, so Claude can work there while answering.
- Tool
- One named action a connector gives Claude. Claude decides which ones it needs; the directory sheet lists them by name.
- Authorization
- The service's own login screen, where you give Claude the access it will use. Granted once per person, and revocable.
- Approval
- The confirmation Claude waits for before completing something that changes your account, shown in the chat at the right time.
- MCP
- The shared standard connectors are built on; it is what lets an assistant such as Claude talk to an outside service.
Plug Unify into Claude in three steps
- 01
Find Unify in Claude
In Claude's settings, open Customize, then Connectors, and find Unify. Unify points to the verified official connector. On a Team or Enterprise workspace, an Owner or Primary Owner has to enable it first so each member can sign in.
- 02
Start the connection
Click Connect on its row, then log in with your Unify account in the window Unify opens. If the link breaks later, use Disconnect, then connect it again from the same row.
- 03
Read the authorization screen
Check Unify's authorization screen before accepting. It belongs to Unify, not to Claude, and it defines what the access covers. You can take it back later from your Unify account too.
The 50 tools, sorted by what they do
Unify gives Claude 50 tools: 23 that read your account, 27 that change something in it.
Two groups: what Claude reads, and what it changes or launches. Names stay as Claude shows them, in English.
- 23 read
- 27 write
What Claude reads (23)
23 toolsTwenty-three tools that consult records, Sequences, tasks, runs and your own context without changing them.
find_unique_object_record
Finds exactly one record from values that are unique in Unify, such as an identifier your team treats as one of a kind, instead of searching loosely.
get_me
Returns your own Unify profile and the workspace you are connected to.
get_object
Reads one object definition by its API name. In Unify, objects are the standard and custom record types your data lives in.
get_object_attribute
Reads one attribute of an object by its API name, the field-level detail behind a column: what it is called and what it expects.
get_object_attribute_option
Returns a single option of a select attribute, one of the values a dropdown field accepts.
get_object_record
Opens one record by its ID and returns what Unify holds on it, so you can read a company or a person without leaving the chat.
get_sequence_enrollment
Reads one enrollment, meaning one person's place in one Sequence, by its ID, with the state it is in.
list_agent_runs
Lists the Agent runs you started through run_agent, newest first.
list_object_attribute_options
Lists every option available on a select attribute, the full set of values a dropdown field accepts in your workspace.
list_object_attributes
Lists the attributes defined on an object, so you see which fields exist before reading or filling them.
list_objects
Lists the standard and custom objects of your Unify workspace, the record types everything else hangs from.
list_sequence_enrollments
Lists enrollments across your Sequences, meaning who is in which outbound cadence and where they stand.
list_sequence_steps
Lists the steps of a Sequence, in order, so you can read the cadence from start to finish.
list_sequences
Lists your Sequences, the multi-step outbound programs Unify runs, with enough detail to pick the one you need.
list_tasks
Lists outreach and action-item tasks, the work waiting on your team.
load_datatable
Loads one of your Unify DataTables with its columns and a page of rows, so Claude can work on a list you built earlier.
load_general_context
Loads a version of your business context: company description, ICP, products, pricing and similar details Unify's Agents use as grounding.
load_mailbox_voice_profile
Loads the voice profile of one of your connected mailboxes, the tone Unify uses to personalise outbound copy.
poll_agent
Checks where an Agent run stands: still running, waiting for your answers, finished or failed.
read_agent_results
Reads the final answer, or its error, once an Agent run has finished or failed.
retrieve_sequence
Opens one Sequence by its ID and returns how it is set up.
retrieve_sequence_step
Opens one step of a Sequence by its ID, so you can reread its content on its own.
retrieve_task
Opens one task by its ID and returns its details, such as who it is for, its priority and its due date.
What Claude changes (27)
27 toolsTwenty-seven tools that create, edit, pause, delete or launch things in Unify. No source describes a confirmation specific to any of them: the general rule below applies.
answer_question
Approval: see the ruleSends your answers to the questions a paused Agent run asked, then lets the run resume.
cancel_agent
Approval: see the ruleStops an Agent run that is still going.
complete_task
Approval: see the ruleMarks a task as completed.
create_object
Approval: see the ruleCreates a custom object in your workspace, a new type of record.
create_object_attribute
Approval: see the ruleAdds an attribute, a new field, to an object.
create_object_attribute_option
Approval: see the ruleAdds an option to a select attribute, a new value in a dropdown field.
create_object_record
Approval: see the ruleCreates a record, for example a new company or person.
create_sequence_enrollment
Approval: see the ruleEnrolls a person in a Sequence.
create_task
Approval: see the ruleCreates a task for a person.
delete_object
Approval: see the ruleDeletes an object from your workspace.
delete_object_attribute
Approval: see the ruleDeletes an attribute from an object, removing that field from the record type.
delete_object_attribute_option
Approval: see the ruleRemoves an option from a select attribute, so the value can no longer be picked.
delete_object_record
Approval: see the ruleDeletes a record by its ID.
delete_sequence
Approval: see the ruleDeletes a Sequence.
delete_sequence_enrollment
Approval: see the ruleCancels one person's enrollment in a Sequence, taking them out of that cadence.
delete_task
Approval: see the ruleDeletes a task outright rather than closing it.
pause_sequence
Approval: see the rulePauses a Sequence along with its enrollments.
pause_sequence_enrollment
Approval: see the rulePauses one person's enrollment without touching the rest of the Sequence.
resume_sequence
Approval: see the ruleResumes a paused Sequence, so its enrollments pick up again.
resume_sequence_enrollment
Approval: see the ruleResumes one person's paused enrollment, leaving the rest of the Sequence as it is.
run_agent
Approval: see the ruleStarts Unify's Agent, the one behind Unify Chat, on a plain-language task: research, list building, Sequence enrollments, a Play or CRM updates. It returns a run ID and keeps working in the background.
update_object
Approval: see the ruleChanges an object's display name or description, the labels your team sees for a record type.
update_object_attribute
Approval: see the ruleChanges the editable settings of an attribute, such as how a field is labelled or described.
update_object_attribute_option
Approval: see the ruleRenames an option of a select attribute, the label shown in a dropdown.
update_object_record
Approval: see the ruleUpdates a record by its ID, correcting or completing what Unify holds on a company or a person.
update_task
Approval: see the ruleChanges a task's assignee, priority or due date without recreating it.
upsert_object_record
Approval: see the ruleMatches on unique values: when a record already fits them it gets updated, otherwise a new one is made.
What Claude asks before acting
By default, Claude stops and asks for your go-ahead before each action it takes on an account for you. The prompt appears in the chat, right when it matters.
On a Team or Enterprise workspace, owners decide whether a member may let some actions through without being asked every time. They can also cap what a connector may do for the whole organization, keeping reading open and closing writing, for example. Nobody overrides that from their own account. On Unify's side, every call is scoped to the user and workspace that signed in: Claude reads or acts only on data that user can already see. One nuance matters here: once an Agent run starts, it works in the background inside Unify.
Which plans it is available on
Among the 819 sheets in the official directory, none shows availability per plan. The per-connector answer is not published anywhere: a real gap in the catalogue.
The general rule is public: remote connectors are open to every user on Claude, Cowork, Claude Desktop and mobile. On Team and Enterprise, an Owner or Primary Owner enables the connector for the organization before members can sign in. On Unify's side, the connector uses the same credits as Unify Chat, with no separate cost according to Unify. For the current Claude-side state, check the connector's sheet in the official directory.
Where this connector stops
A connector is not an automation. Claude calls these tools while it answers you: nothing starts when a prospect replies, a record changes or a Sequence step fails.
The tool list is an observed floor, not a promise: an administrator can open actions that appear on no public sheet. The partner badge is not a security audit, and Anthropic states on every sheet that it neither chooses a publisher's tools nor guarantees their behaviour. Unify is documented only by its publisher here. Unify's FAQ also mentions recurring scheduled chats; no tool on this sheet sets one up, so this page does not cover them. For a different sales tool, see the Claude activecampaign connector.
Need help connecting Unify to Claude?
A person reads every message.
