Quick Answer: What is the Webhook Trigger Node?

[!NOTE] The Webhook Trigger Node creates a unique, public URL for your workflow. When an external application (like Stripe, Typeform, or your custom Backend) sends an HTTP POST request to this URL, the ConvertUniverse workflow launches automatically, using the request's JSON body as input data.

Core Capabilities

1. Zero-Code API Endpoints

Instantly create an API endpoint without spawning servers. The Webhook Trigger acts as your document automation gateway.

2. External Integration

Connect directly with 5,000+ apps via Zapier or directly from services like GitHub or Shopify. Each incoming event kicks off a fresh AI Agent or PDF generation run.

3. File Injection (Base64)

In addition to JSON data, you can send files to the Webhook Trigger via Base64 encoding. The platform decodes the file and passes it to downstream PDF Tools.

Configuration Guide

Setting	Description	Recommended
Endpoint Slug	The unique part of your webhook URL.	Use descriptive names like `invoice-receiver`.
CORS Mode	Allow cross-origin requests from browsers.	Enable if triggering from a front-end client.
Headers	List of expected headers for validation.	Required for secure integrations.

Best Practices

Schema Mapping: Use a Wait Node if the external app sends data faster than your processing nodes can handle.
Debugging: Use the Workflow History dashboard to view the exact raw payload received by your webhook if the execution fails.

[!TIP] Processing periodic tasks? Use the Schedule Trigger Node if you want your workflow to run at specific times instead of reacting to events.