It shows its sources
Every call is traced to the documentation page it came from, so you can check it before anything runs.
Custom API integration
Integrate any API, even one with no connector
Name the service and say what should happen. Whenever reads its API documentation, tells you which pages it took the calls from, and writes them into a workflow that runs the same way every time. No connector to wait for, and no request-building by hand.
From a service name to working calls
The same steps for a CRM from 2009, a warehouse system or an internal tool.
- DescribeName the service and the job
Whenever a new order lands, push it into the system you name. Plain words, no endpoint list.
- ResearchIt reads the documentation
The base URL, the paths, the authentication and the paging, with the pages each came from. Nothing published? Paste what you have into the chat.
- ConnectAdd the credential in setup
The key goes into secure setup, masked, never into the chat. From there it is ordinary code.
What it will and will not do
The rules the builder follows when there is no ready-made connector.
It never guesses an endpoint
When there is no documentation to find and none to give it, Whenever says so and changes nothing.
It runs like any other workflow
On a schedule, on a webhook or on demand, billed per run. Free AI building and editing have weekly usage limits.
A custom integration, or a catalogue one?
Describe a custom integration when
- The service is not among the 1,400+ in the catalogue.
- It is an internal tool, or an old system with a documented API.
- You would otherwise be building HTTP requests step by step.
Use a catalogue integration when
- The app is already in the directory: its connection is managed for you.
- The provider publishes an MCP server Whenever connects through.
- You need a trigger the provider sends as an event.
A few useful answers
Can Whenever connect to an app that has no integration?
Yes, if the app has an API with documentation. Whenever reads the documentation, shows which pages it used, and writes the calls. If nothing is published, paste the documentation you have into the chat.
Where does my API key go?
Into secure setup, where it is masked and stored as a secret. It never goes into the chat, and the workflow reads it at run time.
What happens if the API is not documented anywhere?
Whenever tells you it has nothing to work from and changes nothing. It never writes an endpoint from memory.
Do I need to know how the API works?
No. Say what should happen in plain words. The code it writes is there to read, and you test it against real inputs before it goes live.
Sources & further reading
Sources reviewed September 30, 2026.
Name the tool nobody else supports
Say what should happen. Whenever reads the documentation and writes the integration.