Skip to content
Automation

Webhook

A webhook is a notification method in which one system automatically sends a message to another system at a set web address when something happens.

A webhook is one system telling another, on its own, that something happened. When an order is paid, the payment system sends a small package of data to a web address at the shipping program. The package says what happened and carries details such as the order number and amount. The receiver takes it and starts its own job.

The difference is in how you get the information. Without one, the shipping program would have to ask the payment system every few minutes whether there is a new payment. With a webhook the news arrives at the moment of the event. In return, the receiver has to be ready, check the incoming data and know what to do if something fails.

Why It Matters

  • Information moves between systems without delay. The shipping process can start the moment payment arrives.
  • No constant polling is needed, which cuts both waiting time and unnecessary load.
  • An automatic flow replaces manual copy and paste, so details are not typed in wrong.

How It Works

  1. The receiver prepares an addressThe receiving system defines a web address that accepts incoming data, and you give it to the sending system.
  2. You choose which event to listen forIn the sending system you pick an event such as "order paid". The message goes out only when it happens.
  3. Data is sent when the event occursThe sending system makes a request to that address with the event's details.
  4. The receiver verifies and processesThe receiver checks with a shared secret that the request came from the expected system, uses the data and replies.
  5. Failures are retriedIf the receiver cannot answer, most systems retry a few times. Still, check the records for events that slipped through.

Example

At Liva Butik, Mert K. pays for order #1042, worth ₺1.240. Burak Demir had earlier set the shipping program's address as a webhook in the payment system. The moment payment goes through, the order number, amount and delivery address reach the shipping program and a shipment record opens by itself. Selin Kaya no longer retypes the details. One day the shipping program is down for a short while. The payment system retries a few times and the record is finally created. Burak still compares the order count with the shipment count at month end.

Webhook, API call and scheduled polling compared
WebhookAPI callScheduled polling
Who starts itWhere the event happenedThe asking systemThe asking system
WhenAt the moment of the eventWhen it is neededAt fixed intervals
StrengthNo delay, no needless queriesExactly the data you ask forEasy to set up
WeaknessThe receiver must be readyYou must ask to hear anythingExtra load and delay

Not to Be Confused With

A webhook is not the same as an [API](/glossary/api). With an API you ask for the data. With a webhook the data comes to you when the event happens. The two are often used together. A webhook is also not an email or push notification; it is for systems, not people.

In Creato

In Creato, a webhook is one way to link an AI employee to your own system, and that link is set up together with the team.

  • Business-specific tools are connected to an AI employee through webhooks and APIs.
  • For programmatic use, custom integration or API access, you talk to the Creato team.
  • The scope and timeline of a custom integration are set in conversation.
Explore AI Employees

Frequently Asked Questions

Is a webhook secure?

When set up properly, yes, but it is not secure by default. The address is public, so you need to verify that a request came from the expected system. A shared secret and a signature are used for that. Rejecting unexpected requests is also good practice.

If a webhook fails, is the data lost?

Not always. Most systems retry for a while when they get no answer. But if the receiver stays down for long, an event can slip through, so important flows compare the sender's records with the receiver's at set intervals, for example with an API call.

Do I need a developer to use a webhook?

Usually yes. Preparing the address, reading the incoming data and verifying it all take technical skill. Some automation tools offer ready-made steps. As a store owner, write down clearly what should follow when an event happens; that is the most important part of any automation.

Related Terms