Integration · Analytics and data
AI agents for Domo
Find Domo DataSets and run SQL queries on them, read pages (dashboards), users and the activity log of a Domo instance, with a client ID and secret from the Domo developer portal.
- Actions
- 8
- Read
- 8
- Write
- 0
Actions
What your agents can do in Domo
8 actions. Each one is a tool your agents can call and a step your workflows can run.
Read 8
Look things up. Nothing changes.
List DataSets
Lists the DataSets the client may read, as result: each with id, name, description, rows, columns, owner (id, name), createdAt, updatedAt and dataCurrentAt.
Get a DataSet
Reads one DataSet: name, description, rows, columns, owner, dataCurrentAt, pdpEnabled and schema.columns (each column's name and type: STRING, LONG, DOUBLE, DECIMAL, DATE, DATETIME).
Query a DataSet with SQL
Runs a read-only SQL SELECT on one DataSet, which the query names table, like SELECT region, SUM(amount) AS total FROM table GROUP BY region ORDER BY total DESC LIMIT 20.
List pages
Lists the instance's pages (dashboards), as result: each with id, name, parentId, ownerId, locked and children (sub-pages).
Get a page
Reads one page: name, parentId, ownerId, locked, collectionIds, cardIds (the cards on it), and visibility (the user and group IDs that can see it).
List users
Lists the instance's people, as result: each with id, name, email, role (Admin, Privileged, Participant, Social …), title, phone, location, timezone, createdAt and updatedAt.
Get a user
Reads one person by user ID: name, email, role, title, phone, location, timezone, employeeNumber and groups.
Read the activity log
Reads the instance's activity log between two times, as result.
Write 0
Create, change or send.
This tool only reads, so nothing in it changes.
Read only
Every action here only reads, so an agent can look things up in Domo but cannot change anything there.
Connection
How it connects
Connect it once in the console, then give it to the agents and workflows that need it.
Paste the client ID and secret of an app your organization registered with Domo. The platform fetches its tokens itself (OAuth client credentials).
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 Domo data
Ask a question in plain words. The agent can list DataSets, get a DataSet or query a DataSet with SQL in Domo, then answers with what it found.
- 02
Share what it finds in Slack
Give one agent Domo and Slack: it can list DataSets in Domo and post a summary to a Slack channel in the same run.
- 03
Run it as a workflow step
Add "List DataSets" to a workflow, and it runs in Domo the same way every time, with or without an agent.
FAQ
Domo and MyDeepAgents
Can MyDeepAgents connect to Domo?
Yes. The Domo connector has 8 actions, all of which only read. Your agents can call them as tools, and your workflows can run them as steps.
How do I connect Domo?
Paste the client ID and secret of an app your organization registered with Domo. The platform fetches its tokens itself (OAuth client credentials). 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 Domo without asking?
No. Every Domo action only reads, so an agent can look things up there but cannot change anything.
Can I use Domo in workflows as well as agents?
Yes. Every Domo action also works as a step in a workflow, and the same connection serves your agents and your workflows.
Early access
Put Domo to work
Connect it in a few minutes, give an agent the actions it needs, and decide which changes wait for a person.