Data Actions: your own API as a tool
Turn an endpoint you already have into something the assistant can call.
Data Actions is for the thing your customers ask that no document can answer: "where is my order?", "how many are left in the warehouse?", "is my membership still active?". The answer lives in your own system, behind an API. A Data Action is that endpoint, described once, so the assistant can call it mid-conversation and answer with the real number.
Tip: No API of your own? Skip this page. The assistant is complete without it — this is for teams whose systems already speak HTTP.
How this differs from API Connections#
Both give the assistant tools; they differ in who runs the server. API Connections connects an MCP server that already exists and exposes its own tools. Data Actions is for when there is no such server: you describe your endpoints here and Pommy presents them to the assistant as tools. If your API has an OpenAPI document, you do not describe anything by hand — import it and the endpoints arrive as a group.
Groups and actions#
Actions live in groups. A group is one system — "Order API", "Warehouse" — with its own base address and, if it needs one, its own authentication. Inside it, each action is a single endpoint: a name the assistant sees, a description of when to use it, the method and path, and the parameters. Write the description for the assistant, not for a developer: it is the only thing telling it *when* this action is the right one.
Adding one#
- Create a group
Open Data Actions in the left menu and create a group for the system you are connecting. Give it the base address and, if the API needs credentials, add them here — they are stored with the group, not repeated per action.
- Add actions, or import them
Add endpoints one by one, or use Import from OpenAPI and let Pommy read the document. Imported actions arrive switched off so you can review them before anything goes live.
- Turn on what the assistant may use
Each action has its own switch, and so does the group. Enable only what this assistant genuinely needs — an action that is off is invisible to it.
Actions that need to know who is asking#
Some answers are personal — an order belongs to one customer. A group can be marked as requiring identity, and then its actions only run when the conversation has a verified visitor. This is what stops a stranger from asking about someone else's order.
Warning: A Data Action runs against your live system with whatever credentials you gave the group. Start with read-only endpoints; add anything that writes only once you have watched the read ones behave.
Testing it#
After enabling an action, ask the question a customer would ask — in the widget, in their words, not the endpoint's name. If the assistant answers from your system, the description is doing its job. If it ignores the action, the description is usually the reason: say plainly what the action answers and when to reach for it.