Webhooks

Overview

The Webhook destination lets you send feedback data to any HTTP endpoint whenever someone submits a response through your forms. Whether you're piping feedback into Zapier, n8n, Microsoft Power Automate, or your own custom API—webhooks give you full flexibility to route feedback wherever you need it.

This guide walks you through the setup, from creating your first webhook destination to configuring the URL, HTTP method, and optional headers. We'll keep things straightforward so you can get up and running without any guesswork.

---

What You'll Need

Before you start, make sure you have:

• A feedback configuration — The form or feedback stream you want to send to your webhook
• A webhook URL — The endpoint that will receive the feedback (e.g., https://api.yourservice.com/webhook)
• Optional: HTTP headers — Any custom headers your endpoint expects (e.g., for authentication)

If you're using a no-code tool like Zapier or n8n, they'll provide you with a webhook URL when you add a "Webhook" trigger. Just copy that URL and paste it into encatch.

---

Step 1: Open the Destinations Page

Head to the Destinations section in your encatch dashboard. This is where you manage all your integration endpoints—Slack, Email, Jira, GitLab, and Webhooks.

On the Destinations page, you'll see a table showing any destinations you've already set up (or an empty table if you're starting fresh). In the top-right corner, look for the Add Destination button—that's your starting point.

Click Add Destination to open the configuration flow.

---

Step 2: Add a New Destination

A modal titled Add Destination will appear. You'll notice a field at the top for describing what this destination is for.

Destination Description

Enter a brief description of what this destination does—something like "Send feedback to Zapier" or "Webhook for internal API". This helps you and your team understand the purpose of this integration at a glance.

Select from Available Destination Connectors

Scroll down to the section Select from available destination connectors. You'll see a table listing the available connectors: Email, GitLab, Jira, Slack, and Webhook.

Find the Webhook Notification row:

• TYPE: Webhook
• NAME: Webhook Notification
• DESCRIPTION: Send Notifications to webhook as multipart http
• VERSION: v1

Click the Select button next to Webhook Notification to choose it as your connector. Once selected, the button will turn purple and show Selected.

Then click Create Destination at the bottom of the modal to proceed.

---

Step 3: Configure Your Webhook Destination

After creating the destination, you'll land on the Edit Destination page. This is where you set up all the details that control how and where your webhook requests are sent.

Destination Details (Left Column)

On the left, you'll see cards for:

• Destination Details — Confirm the type (e.g., Realtime) and any high-level settings
• Feedback Configuration — The feedback form you linked in the previous step
• Connector Configuration — Shows "Webhook Notification" and its description
• Destination Name — Edit the name you gave earlier if needed (e.g., "Webhook")
• Destination Description — Edit the description if needed

Click Save Details when you're done with these fields.

Webhook Configuration (Right Column)

The right side is where the webhook-specific settings live. These are the settings encatch needs to send feedback to your endpoint.

Webhook URL

Enter the full URL of the endpoint that will receive the feedback. For example: https://api.yourservice.com/webhook. This is the address encatch will POST (or send via your chosen HTTP method) whenever feedback is submitted. This field is required.

The description below the field explains: "The endpoint to which the webhook will be sent."

HTTP Method

Choose the HTTP method for the webhook request. POST is the most common choice—it's typically used when sending data to an endpoint. Select the method that matches what your receiving service expects.

The description explains: "HTTP method for the webhook request."

HTTP Headers

If your endpoint requires custom headers (for example, an API key or authorization token), use the Add Item button to add key-value pairs. This section is optional—only add headers if your integration needs them.

Common use cases include:

• Authorization — Authorization: Bearer your-api-key
• Content-Type — If your endpoint expects a specific content type
• Custom headers — Any headers your Zapier, n8n, or custom API requires

Click Save Configuration when you're done.

---

Step 4: Enable the AI Filter (Optional)

If you want to filter which feedback triggers a webhook, you can enable the AI Filter.

The AI Filter uses natural language prompts to decide which feedback should be forwarded. For example, you might only want to send webhooks for negative feedback, or for feedback that mentions specific keywords like "bug" or "urgent."

To enable it:

1. In the AI Filter section, click Test and Enable AI Filter
2. Configure your prompt to define the criteria
3. Test the filter with sample feedback to ensure it behaves as expected

If you prefer to send every feedback response to your webhook without filtering, you can leave the AI Filter disabled.

---

Step 5: Test and Enable

Before going live, test your setup. On the Destination Status card, click Test & Enable Destination to verify your webhook URL works and that encatch can successfully send a test request. Once the test passes, the destination will be enabled and will start sending real webhooks for every new feedback response that matches your configuration (and any AI filter you've set up).

Test Template Output

To preview exactly what data will be sent to your webhook, use the Test Template Output feature. This lets you:

1. Load sample feedback data (or use the most recent record from the last 7 days)
2. See the payload structure that will be sent
3. Click Execute Process to run a test
4. Adjust your configuration if needed

This is especially useful for making sure your receiving service can handle the payload format.

---

Summary

Here's a quick recap of the flow:

---

Tips and Best Practices

• Use a descriptive destination name — Names like "Zapier Feedback" or "n8n Webhook" make it easy to identify integrations later.
• Verify your endpoint accepts the payload — Test with a tool like webhook.site or your service's test mode before enabling.
• Add auth headers when needed — If your endpoint requires authentication, use the HTTP Headers section to add your API key or token.
• Consider AI filters — If you receive a lot of feedback, an AI Filter can reduce noise by only sending webhooks for feedback that meets your criteria.

---

Troubleshooting