Current flow: manual Custom Actions
Recreated from the official docs and their screenshots (July 2026)
Fields filled: 0
Steps: 0 / 12
Actions live: 0 / 3
Time: 0:00
Click Autofill this step, then Save and continue. 4 steps per action, 3 actions.
1 General
A descriptive name for this action. This will help the AI Agent know when to use it.
Include a description of what this action does and example queries that should trigger it.
2 API
Collect data inputs for action (optional)
List any information the AI Agent needs to perform the action. The agent can find the data in chat history, request it from the user, or retrieve it from the user's metadata.
NameTypeDescriptionArray
API request
The endpoint the AI Agent should call. You can include data inputs (variables) collected from the user in the URL or the request body.
API keys are typed directly into a header field. No managed auth or secret storage in this flow.
3 Test response
TokenValue
email
Responses must be JSON, max 20 KB.
4 Data access
3 actions created, eventually
If the API changes, each action must be found and re-edited by hand.
Proposed: Actions auto-discovery
Point it at the API you already have. Tools generate themselves.
Fields filled: 0
Steps: 0 / 4
Actions live: 0 / 3
Time: 0:00
Click Discover endpoints, then review, test, and enable.
Given a base URL, well-known spec paths (/openapi.json, /swagger.json, /api-docs) are probed automatically.
Drop an OpenAPI YAML/JSON file or a Postman collection export here.
Extraction feeds the same review screen.
Extraction feeds the same review screen.
API behind a firewall? A lightweight connector runs inside your network, no public exposure needed.
3 tools generated
Nothing is live yet. Expand each card to review it, and toggle off anything the agent shouldn't have.
Authentication
Stored encrypted in a credential vault, injected at call time, never shown again.
3 actions live
API changed? Re-sync re-reads the spec and updates the tools automatically.