Overview

Webhook listener is a Workflow initiator that allows external systems to trigger an Alchemer Workflow via webhook (HTTP POST or GET request).

Common uses for the Custom Events initiator

• Trigger a Workflow when specific conditions are met in an external system (e.g., Salesforce, CRM, support tools)
• Send personalized survey invitations after a transaction or status change
• Pass external system data into Workflow merge codes
• Use external values in Workflow If/Else logic
• Connect complex third-party automations to Alchemer
• Automate feedback collection from external systems

What can the Custom Events initiator do?

• Trigger a Workflow via HTTPS POST request
• Trigger a Workflow via HTTPS GET request
• Accept custom fields as query parameters or JSON body values
• Validate incoming requests using custom header security and IP whitelisting

You will need

• An Alchemer plan that includes Workflow
• The Integration Manager permission enabled
• An external system capable of sending HTTPS POST or GET requests
• Defined field names and values to pass into the Workflow

Setup Custom Events initiator in Workflow

Custom Events| Webhook listener

You will need:

• To determine how your external system will call the webhook endpoint.
• To define the field names and values you want passed into Alchemer Workflow.

Configure the initiator

1. Open your workflow in Workflow builder.
2. Select Custom Events as the Workflow initiator.
3. Select Webhook listener and click Next.
4. Review the initiator overview screen and click Next.
5. Custom events | Webhook listener: On this screen you will:
   • Copy the Webhook URL to use in your external system to trigger the Workflow.
   • In the Custom Fields section, define the parameters your external system will send to the webhook.
   • Configure security options such as custom headers, IP whitelisting and basic authentication.
6. Click Save to complete setup.

Merge Codes

When the webhook fires, custom fields are passed into Alchemer Workflow and become available as merge codes. These can be used in:

• Survey Invite steps
• Send Email steps
• If/Else logic
• Subsequent integration steps

Testing and Troubleshooting

Testing and Validation

How to test

• Send a test POST or GET request from your external system.
• Monitor the Workflow run in the Monitor tab.
• Inspect metadata outputs to confirm field values were received.

How to verify results

• Confirm the Workflow triggered successfully.
• Verify merge codes populated as expected.
• Confirm downstream actions executed properly.

Monitoring Integration Activity

Where to find logs

• Go to Results → Monitor.
• Select the Workflow run to inspect request details.

What logs display

• Incoming field values
• Header validation results
• Status codes (200 or 400)

Troubleshooting

Workflow not triggering

• Incorrect webhook URL
• Invalid HTTP method
• Improper request formatting

Fields missing

• Fields not configured in initiator setup
• Nested JSON structure (unsupported)

400 errors

• Missing or invalid custom header values
• Malformed request body

FAQs