Custom apps: connect any tool
No built-in app for your tool? If it can send a web request, a custom app receives it and starts your agents. With an HTTP request an agent sends data back out.
What starts an agent
A custom app is an app you create yourself. Each trigger is a web address your tool sends data to.
- WhenA request to your trigger address
HireData stores it as an event and starts every agent connected to that trigger.
- WhenPOST or GET
POSTreads the body, as JSON or form data.GETreads the query parameters. Other methods are rejected. - WhenFields you describe
Each field has a label, a key and a type. Paste a JSON sample and HireData creates the fields, and detects emails, phone numbers, dates and URLs.
- WhenTest without risk
Try It in test mode runs your agents in a sandbox. Nothing is created, changed or sent.
What an agent can do
A custom app receives data. To send data out, an agent uses the HTTP Request step.
| Step | Kind | What it does |
|---|---|---|
| HTTP Request | Add | Calls any external API. Methods GET, POST, PUT, PATCH, DELETE and HEAD. |
| Import | Setting | Paste, upload or fetch an OpenAPI 3.x, Swagger 2.0 or Postman 2.1 document, or a cURL command. HireData fills in the request. |
| Body | Setting | Form fields, multipart or URL encoded. Or raw JSON, XML, text or GraphQL. |
| Sign-in | Setting | None, API key, Bearer token, Basic auth or OAuth2 with client credentials. |
| Response | Returned | Describe the response and its values become fields for later steps. Status code, body and success are always there. |
| Failures | Logic | Timeout, retries and backoff. Choose whether a 4xx or 5xx fails the step, and whether the run continues. |
What is read and written
What comes in through a trigger and what goes out with a request.
| Part | Direction | Notes |
|---|---|---|
| Trigger fields | In | Usable in agents and as variables in emails, messages and forms. |
| People | In | Can be synced automatically from incoming data. |
| Events | In | Every request a trigger received is shown under Events. |
| URL, parameters, headers and body | Out | Any part can hold a field from the run, so each run sends its own data. |
| Response Status, Body and Success | Back | Plus every value you described in the response. |
Good to know. Sign-in details for an HTTP request are stored in the step. Anyone who can edit the agent can read them. Requests shown in a run mask them.
How to connect
- Create the appUnder Settings, Apps, click Create New App. Give it a name, and an icon if you like.
- Add a triggerClick Create Trigger. Copy the address into the tool that sends the data.
- Describe the fieldsPaste a sample, send a first request, or add fields by hand.
- Try itSend a test request from HireData and follow each step of the run.
- ActivateThe app and the trigger each have an active state. Agents run when both are active.
For your developer
- A tool that supports webhooks, or a developer who can add a web request
- Request examples to hand over: cURL, JSON, OpenAPI and a copy for AI assistants
- The header
X-HireData-Test: truemarks any request as a test
See it run on your own vacancies.
Answer four short questions and watch the agent for your problem. Then book 30 minutes with us.

