Activepieces Webhook Not Triggering

How to fix it

Try these in order — the most common fix is first.

1. 1. Use the live URL on a published flow

   Copy steps
   1. Open the Webhook trigger
   2. Copy the Live URL, not the Test URL
   3. Publish the flow and update the sender
   Did this fix it? Yes No

2. 2. Use the sync variant when a response is needed

   Copy steps
   1. Add /sync to the end of the webhook URL
   2. Add a Return Response step
   3. Keep the response within the 30 second webhook timeout
   Did this fix it? Yes No

3. 3. Fix the frontend URL on self-hosted

   Copy steps
   1. Set AP_FRONTEND_URL=https://flows.example.com in .env
   2. Run docker compose up -d
   3. Put a reverse proxy with TLS in front
   Did this fix it? Yes No

4. 4. Check the sender and network

   Copy steps
   1. Match the sender's expected response format
   2. Check firewalls for blocked calls
   3. Look at the run list to see whether anything arrived
   Did this fix it? Yes No

Symptoms

The test call is captured but real events never start a run, the caller sees a timeout or no response, or runs only appear for one source IP.

Why it happens

• Test URL used on a published flow
• Wrong AP_FRONTEND_URL on self-hosted installs
• Missing /sync suffix when the caller needs a response
• Sender requires a text challenge response rather than JSON
• Firewall or IP blocking

This guide also covers

• activepieces webhook not working
• activepieces webhook not triggering
• activepieces webhook live url

Other Activepieces errors

• Activepieces Runs Stuck in Queued
• Activepieces EXECUTION_TIMEOUT Error
• Activepieces Code Step Out of Memory
• Activepieces Flow Shows Success but Step Failed
• Activepieces Self-Hosted Docker Not Working
• Activepieces Upgrade Broke Flows
• Activepieces Connection Expired or Authorization Failed
• Activepieces Flow Won't Turn On or Stops Running