Proposal 1
Auto discovery
Actions that create themselves. One link connects every endpoint at once: less time, less work, better experience.
Today
One wizard per endpoint. Around 10 fields each, typed by hand, repeated for every endpoint.
Proposed
One link imports every endpoint at once. Review and enable. About 2 minutes total.
The problem
Today, every action is typed by hand: name, when to use, data inputs, method, URL, parameters, headers, body, test, data access. One full wizard per endpoint. Three endpoints means the whole thing three times.
Meanwhile, the customer's API is usually already described somewhere: an OpenAPI spec, a Postman collection, or their docs. None of that information is used.
The proposal
- Point. Paste a spec URL, upload a file, or paste docs. Given a base URL, well known paths like
/openapi.jsonare probed automatically. - Review. Every generated action appears with its inputs, descriptions, and when to use, all editable.
- Test. One click fires a real test call per action and validates the response.
- Enable. Approved actions go live. The outcome is identical to the manual flow, minus the typing.
Discovery is not enablement. Nothing is callable until a human approves it. Read only endpoints import by default, write actions require explicit opt in.
What it improves
- Setup effort goes from per endpoint to per API.
- Auth moves from keys pasted into header fields to stored credentials, injected at call time.
- When the API changes, a re sync re reads the spec and flags breaking changes instead of failing silently.
