Webhook Trigger

The Webhook Trigger starts your workflow when someone or something sends data to your special URL, enabling real-time integrations with external services.

Key Features

• Unique URL Generation: Each workflow gets its own dedicated webhook URL
• Test and Production Modes: Separate URLs for development and live environments
• Flexible Data Handling: Accept JSON, form data, or raw payloads
• Built-in Security: Optional API key or Bearer token authentication
• Instant Execution: Workflows trigger immediately upon receiving data
• Request Logging: View incoming requests for debugging

Configuration

When to Use This

Use webhooks to connect external tools to your workflow:

• When a form is submitted on your website
• When someone makes a purchase
• When another app wants to trigger your workflow
• When you need to receive data from external services

Example: When someone fills out a contact form, the form sends data to your webhook, and your workflow automatically sends them an email.

Setup Guide

Step 1: Add the Block

Drag the "Webhook" block to your canvas as the first block.

Step 2: Get Your URL

The block automatically creates a unique URL for you. It looks like:

https://yourapp.com/webhook/abc123xyz

Step 3: Copy and Use

Copy this URL and paste it wherever you need:

• In your form settings
• In another app's webhook configuration
• In your website code

Step 4: Test It

Click "Test" button to see if data is coming through correctly.

Understanding the Settings

Webhook URL

• Test URL: Use this while building (data won't affect real users)
• Production URL: Use this when your workflow is ready for real use

Receiving Data

When data arrives, you can use it in your workflow:

• If form sends name and email, you can access them as {{name}} and {{email}}
• All received data is automatically available to use in next blocks

Security Options

Example Usage

Form Submission Handler

Webhook → Validate Data → Save to Database → Send Confirmation Email

Process form submissions from your website in real-time.

E-commerce Order Processing

Webhook → Parse Order Data → Update Inventory → Notify Fulfillment Team

Receive order notifications from your e-commerce platform.

Third-Party App Integration

Webhook → Transform Data → Update CRM → Log Activity

Connect any service that supports webhooks to your workflow.

Email Subscriber Signup

1. Add Webhook trigger to your workflow
2. Copy the webhook URL
3. Configure your signup form to send data to this URL
4. When someone signs up, your workflow receives their email
5. Next blocks in your workflow can save to database or send welcome email

Testing Your Webhook

1. Click the Test button in webhook settings
2. Send sample data from your form or app
3. Check if the workflow receives it correctly
4. View received data in the test results

Node Display

The Webhook Trigger block displays:

• Webhook URL: Your unique endpoint (click to copy)
• Environment: Test or Production mode indicator
• Authentication: Security status (enabled/disabled)
• Last Request: Timestamp of the most recent incoming request
• Request Count: Total number of requests received

Error Handling

Common Questions

Q: Can I use the same webhook for multiple workflows? A: No, each workflow gets its own unique webhook URL.

Q: What if my webhook stops working? A: Check if the workflow is published and the URL hasn't changed.

Q: How do I know what data my webhook received? A: Check the workflow logs or test results to see all received data.

Best Practices

1. Use Test Mode First: Always develop and debug using the Test URL before going to production

2. Enable Authentication: Secure production webhooks with API keys or Bearer tokens

3. Validate Incoming Data: Add validation logic to ensure data meets expected formats

4. Handle Errors Gracefully: Return meaningful responses to help diagnose issues

5. Monitor Request Logs: Regularly check incoming requests for anomalies

6. Document Your Endpoint: Keep records of expected payload structure for team reference

7. Set Up Retry Logic: Configure calling services to retry on temporary failures

8. Use HTTPS Only: Always use secure HTTPS URLs for production webhooks