Integration · Other
AI agents for Unified.to
Reach your customers' CRM, HR, recruiting, accounting, ticketing, commerce, calendar, messaging, file and task tools through Unified.to's unified API, with the same fields whichever tool each customer uses.
- Actions
- 6
- Read
- 3
- Write
- 3
Actions
What your agents can do in Unified.to
Reach your customers' CRM, HR, recruiting, accounting, ticketing, commerce, calendar, messaging, file and task tools through Unified.to's unified API, with the same fields whichever tool each customer uses (Salesforce, HubSpot, BambooHR, Workday, Greenhouse, QuickBooks, Xero, Zendesk, Jira, Shopify, Google Calendar, Slack and hundreds more). List the workspace's connections, then list, read, create, update and delete records in any of them.
Read 3
Look things up. Nothing changes.
List connections
Lists the workspace's connections, one per customer account linked through Unified.to.
List records
Lists one kind of record from a connection, in Unified.to's common fields; the answer's result is the list (up to 100).
Get a record
Reads one record of a connection by its id, in Unified.to's common fields (like a contact's name, emails, telephones, company and deals, or an employee's title, manager, employment status and dates).
Write 3
Create, change or send.
Create a record
Creates a record in a connection's tool, with Unified.to's field names in fields.
Update a record
Changes a record in a connection's tool: only the fields you give in fields change.
Delete a recordDeletes data
Deletes a record in the connection's tool (a contact, deal, ticket, event and so on), where that tool allows it.
A person can approve first
Any write action can be set to wait for a person's approval before it runs, so an agent asks before it changes anything. Actions that delete data ask first by default.
Connection
How it connects
Connect it once in the console, then give it to the agents and workflows that need it.
Paste an API key from your Unified.to account.
What you enter
- Workspace API token
Settings
- Data region
Kept safe
- Credentials are stored encrypted with your organization's own keys.
- They are opened only by the process that makes the call, at the moment it runs, and never go into a prompt or the browser.
- Calls go only to the tool's own servers.
Ideas
Ideas to start with
Starting points made only from the actions above. Mix them with any other tool your agents can use.
- 01
Ask about your Unified.to data
Ask a question in plain words. The agent can list connections, list records or get a record in Unified.to, then answers with what it found.
- 02
Let an agent update Unified.to
Have the agent create a record or update a record in Unified.to as part of a larger task. Turn on approval and a person signs off on each change first.
- 03
Share what it finds in Slack
Give one agent Unified.to and Slack: it can list connections in Unified.to and post a summary to a Slack channel in the same run.
FAQ
Unified.to and MyDeepAgents
Can MyDeepAgents connect to Unified.to?
Yes. The Unified.to connector has 6 actions: 3 read and 3 make changes. Your agents can call them as tools, and your workflows can run them as steps.
How do I connect Unified.to?
Paste an API key from your Unified.to account. You'll need: Workspace API token. The connection also asks for: Data region. Credentials are stored encrypted with your organization's own keys and are opened only at the moment of a call.
Can an agent change data in Unified.to without asking?
Only if you let it. Each of the 3 actions that change data can be set to wait for a person's approval before it runs, and the one that deletes data asks first by default.
Can I use Unified.to in workflows as well as agents?
Yes. Every Unified.to action also works as a step in a workflow, and the same connection serves your agents and your workflows.
Early access
Put Unified.to to work
Connect it in a few minutes, give an agent the actions it needs, and decide which changes wait for a person.