An automated message one application sends to another via an HTTP request when a specific event happens.
Instead of repeatedly asking a service whether anything has changed, a process called polling, a webhook lets the service notify you immediately. You give the provider a URL, and when an event occurs, it sends a POST request to that URL with details, usually in JSON.
For example, when a customer completes a payment, a payment gateway might send a webhook to an online store's server, which then marks the order as paid and sends a confirmation email. Webhooks also connect code repositories to CI/CD pipelines and chat tools to project trackers. Because anyone could send requests to a webhook URL, receivers should verify signatures, handle duplicate deliveries, and respond quickly while processing in the background.
Application Programming Interface: a defined set of rules that lets one piece of software request data or services from another.
Payment GatewayA service that securely captures and transmits payment details from a customer to the banks and networks that approve the transaction.
ServerlessA cloud model where developers run code without managing servers, and the provider automatically handles scaling and charges per use.
A practical, step-by-step guide to automating lead capture, invoice reminders and other repetitive tasks with no-code tools, plus what each tool type costs and where automation goes wrong.
REST vs GraphQL compared at the code level: how queries, caching, errors, security and tooling differ, and a clear framework for choosing on your next project.
How AI phone receptionists handle calls, connect to booking and CRM tools, and where disclosure, recording consent and privacy rules apply before you switch one on.