n8n Webhooks & APIs
Webhooks and triggers in n8n.
Articles in n8n Webhooks & APIs
- Webhook Security for AI Automations: Signatures, Replay Protection and Safe Payloads — A webhook is a public door into your automation, and most tutorials leave it unlocked. This guide maps threats to controls: authentication options and their strength, correct HMAC verification, replay protection, secrets, and what changes when the payload feeds a language model.
- Idempotent AI Automation: How to Stop Duplicates, Retries and Replays from Doing Damage — A retry creates two CRM records and two welcome emails, and nothing was technically a bug. Idempotency is the design idea that prevents it. This guide covers where duplicates come from and the concrete patterns, code and tests that make workflows safe to repeat.
- n8n Stripe Node: Automating Payment Events Without Custom Webhook Code — Stripe fires a webhook for nearly everything that happens to a payment -- succeeded, failed, disputed, refunded. The n8n Stripe node and Stripe Trigger turn those events into automation without you writing and securing a custom webhook endpoint by hand.
- n8n's REST API: Automating Your Automation Platform Itself — The HTTP Request node calls other services' APIs. n8n also has its own REST API for managing n8n itself -- creating, updating, activating, and monitoring workflows programmatically, which matters the moment you're managing more than a handful of workflows by hand in the editor.
- Shopify AI Automation: Connecting Your Store to n8n, Chatbots, and AI Agents — Shopify Magic handles a handful of built-in AI features inside the admin. Everything past that -- an order-status chatbot, AI-written product descriptions at scale, inventory alerts that actually think -- has to be wired up yourself, through Shopify's webhooks and Admin API rather than a settings toggle.
- n8n Rate Limiting: Avoiding 429 Errors and API Throttling in Workflows — A workflow that works fine at 10 items falls over at 10,000 -- not from a bug, but from the third-party API pushing back. Here is how to build n8n workflows that respect rate limits instead of hoping they never get hit.
- n8n Respond to Webhook vs the Webhook Node: Building Synchronous APIs Without Silent 200s — The Webhook node decides when to answer; the Respond to Webhook node decides what to answer. The four response modes, the node's options, why a forgotten branch returns 200 rather than silence, and how to reply early for slow work.
- Polling vs Webhooks: Getting Results Back From a Long-Running AI Automation Step — A step that takes ninety seconds needs a different result-retrieval design than one that takes ninety milliseconds. Polling and webhooks solve that differently, at different costs.
- n8n Webhook Signature Verification: Trusting Requests From Third-Party Services — A webhook URL alone doesn't prove a request actually came from the service you're expecting — anyone who finds or guesses it can send a fake payload. Signature verification is what actually proves it.
- n8n Wait Node: Resume a Paused Workflow via Webhook (resumeUrl) — Building an approval step that might not get a response for hours or days means the workflow can't just sit there blocking. The Wait node's webhook-resume mode is built exactly for this.
- Debugging an n8n Workflow That Works Manually but Fails on Trigger — It's one of the most disorienting n8n bugs: click "Execute Workflow" and everything works, but the live trigger fails silently. It's almost always one of four specific causes.
- Why Your Webhook-Triggered AI Automation Duplicates Actions on Retries — A slow Claude call plus a webhook provider's retry policy is a near-guaranteed way to send the same email twice. Here's the fix.
- Run n8n Locally for Free with Docker (Part 7 of 10): Testing Webhooks Locally with a Free Tunnel — Part 7 of the local n8n Docker series: giving your local n8n instance a public URL with a free tunnel, so real webhooks from a CRM, form tool, or API can actually reach it.
- n8n HTTP Request Node: Credentials, Pagination, Responses and Errors — How to make n8n's HTTP Request node reliable: predefined and generic credentials (Header, Bearer, OAuth2 and more), built-in pagination and batching, response options (headers, Never Error, formats), retry versus error-output handling, and a Retry-After pattern built from documented nodes.
- n8n Webhook Node Explained: Test vs Production URLs, Auth, Responses and Debugging — Configure n8n's Webhook node deliberately: test vs production URLs, path parameters, authentication, when to respond, reverse-proxy setup, and a fix for every common failure.