Webhook

A webhook is a way for one service to tell another about an event on its own. The second service gives the first one its address (URL) in advance. When the event happens, the first service immediately sends an HTTP request with the event data to that address.

Without a webhook, the second service would have to ask the first one every few minutes: "Anything new?" With a webhook, there's no need to ask. Food delivery works the same way: you can open the app every five minutes to check the order status, or you can wait for the "Your courier is at the door" notification.

Where you'll find webhooks:

• A customer pays for an order, and the payment service tells the online store
• A customer fills in a form on a website, and the lead lands in the CRM
• A developer pushes code to a repository, and a build starts
• A server stops responding, and the monitoring system sends an alert

Webhooks and APIs complement each other. Through an API, a program requests data or performs an action itself. A webhook reports an event without anyone asking.

In Pachca, webhooks work through a bot. An incoming webhook receives events from other services and posts them in the chats the bot belongs to. An outgoing webhook sends events from Pachca to your server: new messages, reactions, button clicks. See how this works in practice in the Jira notifications, website leads and n8n and AI agents scenarios.