Lindy Community Icon

Critical Webhook Issue in Lindy: Persistent Task Creation Failure | Lindy Community

Critical Webhook Issue in Lindy: Persistent Task Creation Failure

·Aug 21, 2025 10:25 PM·

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.

Alon J.
·
·
Hey Giacomo -- Do you mind sharing your Task URL, so we can take a look? How to share your Lindy task URL: 1. Click your Lindy agent → click “tasks” 2. Find the task you need help with 3. Click the specific task (you should see the full execution) 4. Copy that page URL from your browser 5. Paste the URL in your support request
Giacomo L.
·
·
Alon J. https://chat.lindy.ai/giacomo-la-vitas-workspace/lindy/business-review-analysis-exp[…]stRunId=68a79401bc5daa6b165daeb9&task=68a79469c68720b8ac9cda62 However, please note that my issue has to do with the fact that my Web hook is not creating the tasks even with all the tests. I was able somehow to get curl test to work, so this is the one I’m sharing. Since that one test, I have not been able to get any web hooks to work.
Alon J.
·
·
Hmmm ok gotcha -- where is the webhook being sent from? What are you expecting to be in the payload?

·

·

Where is the webhook being sent from? Netlify Functions (serverless function) What are you expecting to be in the payload?

{
  "business_name": "",
  "place_id": "", 
  "email": "",
  "rating": 0,
  "review_count": 0,
  "address": "",
  "website": "",
  "session_id": ""
}

Giacomo L.
·
·
Alon J. any ideas?
Giacomo L.
·
·
Alon J.?
Giacomo L.
·
·
Alon J. Is this ticket abandoned?
Alon J.
·
·
Hi Giacomo -- Apologies, I was OOO this weekend. I'm taking a look now
👍1
Alon J.
·
·
A couple things:
1.
When i open the field for address, I don't see it there -- Are you still seeing it? The error is saying "property address should not exist." which means that the address field likely doesn't exist as 'Address' in GHL. In GHL, how do the fields look? Are they split into address1 (street), address2 (apt, suit,etc..), city, state?
a.
You will likely only be able to pass one field at a time here
2. For your customFields value, it's expecting an array. You will need to add square brackets at the beginning and the end. That *should resolve it. [ { "place_id": "{{place_id}}", "rating": "{{rating}}", "review_count": "{{review_count}}", "report_status": "processing", "session_id": "{{session_id}}" } ]
Giacomo L.
·
·
Hi Alon J. , thanks for getting back to me — I really appreciate your time. Just to clarify: the original support request wasn’t about the GoHighLevel (GHL) step or the address field error — that’s actually step two of the workflow. My core issue is that no task is being created at all, even when the webhook returns 200 OK with { "data": { "success": true } }. This has persisted through:
Multiple webhook recreations and agent rebuilds
Validated payload formats (including wrapping in data: { ... })
CURL tests, Netlify functions, and direct API requests
Confirming the trigger node is the first in the workflow
Verifying that fields match exactly what the trigger expects
The webhook system accepts the request, but no task ever appears in the Tasks tab. Would it be possible to have someone from the engineering team take a look at why the trigger itself is not initiating task creation, even though the webhook receives a valid payload and returns success? Happy to provide any additional logs or testing outputs you need. Thanks again!
Alon J.
·
·
Oh interesting! Hmmm -- It looks like you had a successful trigger on Thursday. Let me double check
Alon J.
·
·
Connecting with my team! Will follow up ASAP
Giacomo L.
·
·
Alon J. have you heard back from the technical team?
Giacomo L.
·
·
Alon J. has there been any progress on this? This ticket has been open for a week now… My workflow has completely stopped until I can figure this out. Thank you.
Kha N.
·
·
Giacomo L. I'll investigate this for you right now and get back to you shortly.