Automation
API and webhook: system integration explained for managers
Two words show up in every conversation about automation: API and webhook. The person who decides on the investment is usually not technical and cannot tell whether what is being proposed is simple or complicated, cheap or expensive. This article explains both without code, from the point of view of someone who has to decide.
Why integrate systems
Most manual work in an office exists because systems do not talk to each other. A sale is recorded in one place and someone copies it to another. A payment lands in the bank and someone marks it as paid in finance. Every copy costs time and opens the door to errors.
Asana estimated, in its 2021 Anatomy of Work Index, that about 60% of time in office work goes to activities around the task, such as searching for information and moving data from one place to another. Integrating systems goes straight at that slice. The principle is simple: data goes in once and reaches every place that needs it on its own.
What an API is
An API is a system's service entrance. Through the screen, the user is a person: they click, type and read. Through the API, the user is another system: it asks for a piece of information or sends an instruction, in an agreed format, and gets the answer back.
One comparison that helps: the screen is the restaurant's dining room, and the API is the counter for delivery orders. The dish is the same, but the counter was built to handle orders in volume, without conversation.
When a vendor says the system "has an API", they are saying other systems can read and write data there without anyone opening the screen. It is worth asking what exactly the API allows, because some only let you read data and others cover almost everything.
What a webhook is
With an API, a system has to ask: "has a new payment arrived?". To find out quickly, it would have to ask all the time. A webhook reverses the direction. It is an automatic notice: when something happens, the source system sends a message to an agreed address. "Payment confirmed, order 1048."
Back to the restaurant: the API is you calling to ask whether the order has left. The webhook is the restaurant letting you know when it does.
In practice, the two work together. The webhook says something happened, and the API is then used to fetch the details and write the result somewhere else.
When to use each
| Situation | Usual path |
|---|---|
| React right away to an event (payment, incoming message, submitted form) | Webhook |
| Fetch or write data on demand | API |
| Routine at a set time (daily report, overnight check) | API in a scheduled task |
| Old system with no API and no webhook | File export or replacing the system |
The last row is the one that weighs most in a buying decision. A cheap system with no integration door ends up expensive, because it condemns someone to copying data forever.
What an integration looks like in practice
Imagine a store that sells through its website and serves customers on WhatsApp. Today, when an order is paid, a person checks the bank, marks the order as paid, tells the warehouse and messages the customer. With integration, the flow looks like this:
- The payment provider sends a webhook: payment confirmed.
- The automation receives the notice and, through the store's API, marks the order as paid.
- Through the inventory system's API, it reserves the items.
- Through the official WhatsApp API, it sends the confirmation to the customer.
- It records everything in a log and alerts a person if any step fails.
Nobody touched anything, and the customer got the confirmation within seconds. The fifth step is what separates a serious integration from an improvisation.
Questions to ask the vendor or whoever will build it
You do not need to understand the code. You need to ask the right questions.
- What happens when it fails? Systems go down. The integration has to retry and alert someone, not lose the data silently.
- Where do I see what ran? There should be a record of what came in, what went out and what failed.
- Who receives the alert? A named person, not "the team".
- How are passwords and keys stored? An API key is like the company's key. It does not live in a spreadsheet or a chat message.
- Is the API official? An integration through an unofficial route tends to break when the system changes and can violate the terms of use. On WhatsApp this matters especially, as we explain in AI agents on WhatsApp.
- Is there a usage limit? Many APIs cap the number of calls per minute or charge by volume.
A good integration is one nobody notices until the day it fails. And on that day, it tells you.
Ready-made platform or custom code
There are two ways to build it, and neither is always better.
Automation platforms connect well-known systems with visual blocks. They are quick to start and good for simple flows. The cost grows with volume, and complex flows become hard to maintain.
Custom code gives more control over rules, security, cost per volume and failure handling. It requires someone to maintain it.
The criterion is the same as in any process decision: choose the smallest system that solves the problem. Many operations do fine with both, using a platform for what is simple and code for what is critical.
Where to start
List the systems the company uses and, for each pair, answer: what data does someone copy from one to the other today? That list is your integration map. Rank it by time spent and risk of error, as we show in What to automate first, and start with the first item.
Automating routines and integrations is one of delpra™'s services. If you want to know where your operation stands before investing, the free assessment shows you.
Written by the delpra™ teamProcesses, automation and AI so operations scale efficiently.