Webhook
Deliver a signed payload to an endpoint - reach any system that accepts a webhook.
Connect one webhook endpoint by its URL and deliver payloads to it from an automation or an agent: a JSON object (or a raw body, for a receiver that wants form-encoded, XML or CSV) is POSTed verbatim and signed so the receiver can verify it came from yekar. Works with anything that accepts a webhook - Slack and Discord incoming webhooks, n8n, Make, a Zap, or a service the customer wrote. Delivery is one-way: a 2xx means the endpoint took the payload, not that it processed it. This SENDS webhooks. To start an automation from another system, use its API trigger: the request must carry one of your Yekar.AI API keys and the trigger's id, so a service that can only post its own fixed webhook needs something in between that adds them - unless Yekar.AI offers an event trigger for that service, which receives its webhooks directly.
How you connect it
Credentials
Paste the credentials Webhook gives you, such as an API key or token, into the connection form. They are stored encrypted and never shown again.
The setup guide in the manual covers every step, and each tool in full.
What agents can do with it
3 tools for your agents to use.
Reads 1
Read-only: these look things up.
- Describe endpoint
Changes 2
These can create, update, send or delete.
- Send webhook
- Send webhook with a raw body
Any of these can be set to wait for a person’s approval before it runs.
Put it to work
See what an agent could do in Webhook for you.
Bring the job, the systems it touches, and the decisions that need a person.