Dear Lindy Support Team,
I’m experiencing a critical issue with webhook functionality that has persisted despite following all recommended troubleshooting steps multiple times. Your AI support agent has recommended escalating this to your support team as it appears to be a fundamental platform issue.
ISSUE SUMMARY:
Webhooks consistently return HTTP 200 success responses but fail to create any tasks in Lindy. This occurs across multiple webhook recreations and different webhook URLs.
AGENT DETAILS:
Agent Name: Business Review Analysis Expert
Agent ID: 68a483bc3558b11dce43c86c
Workflow: 9-step business review automation (GoHighLevel integration, web scraping, email delivery)
TROUBLESHOOTING STEPS COMPLETED:
- 1.
Manual webhook recreation (3+ times) - Deleted existing webhook triggers and created new ones through the Lindy UI
- 2.
Multiple webhook URL testing - Tested various generated webhook URLs including:
b3865e8e-c7ef-4cd7-a553-7f33b5244be5
Multiple other auto-generated URLs from UI recreation
- 3.
Complete workflow rebuilds - Rebuilt the entire agent workflow from scratch multiple times
- 4.
Authentication troubleshooting - Removed Authorization headers, tested with/without authentication
- 5.
Minimal testing - Created simple test workflows with just webhook → single action
- 6.
External testing - Tested webhooks via curl, Netlify functions, and direct API calls
TECHNICAL EVIDENCE:
All webhook calls return HTTP 200 with {“data”:{“success”:true}} response
Zero tasks appear in the Lindy Tasks tab despite successful responses
Issue persists across different webhook IDs and complete agent rebuilds
External integrations (Netlify functions) receive 200 responses but workflows never execute
CURRENT STATUS:
The webhook system appears to accept requests successfully but fails to trigger workflow execution. This suggests a disconnect between the webhook endpoint and the task creation system.
AI SUPPORT RECOMMENDATION:
Your AI support agent identified this as a “known issue” and recommended manual webhook recreation. However, after multiple manual recreations, the issue persists, leading the AI to suggest this may be a “fundamental platform issue” requiring engineering investigation.