run-llama/llama_cloud_services
1
0
Fork 0
mirror of https://github.com/run-llama/llama_cloud_services.git synced 2026-08-26 16:56:36 -04:00
Code Issues 352 Packages Projects Releases 10 Wiki Activity

Extraction job webhooks not delivered to automation platform Make.com endpoint #515

New Issue
Open
opened 2026-02-16 00:18:06 -05:00 by yindo · 0 comments
yindo commented 2026-02-16 00:18:06 -05:00
Owner
Copy Link
Copy Source

Originally created by @AntonDobrev on GitHub (Aug 10, 2025).

Describe the bug
When running an extraction job with webhook_configurations with a receiving webhook configured in a low-code automation platform (Make.com), the webhook is never called, despite identical payloads being successfully delivered to webhook.site. The issue seems dependent on the target URL domain validation or HTTP connection handling.

Files
Not a file issue (though only testing with PDF files)

Job ID
Successful delivery to webhook.site - 8b08e69f-bdab-4c95-8e77-12d87f460b1c
Not successful to make.com webhook - b7958bd8-9e10-46ae-8edf-b0bc8976e38d

Client:

  • API v1

Additional context

  1. Working webhook URLs:

  • (tested) https://webhook.site/unique-webhook-guid-here

  • (as per the GitHub issues) https://api-staging.mydomain.org/llama_cloud_webhook

Failing URLs:

  • (tested with webhook in make.com) https://hook.eu1.make.com/unique-webhook-id
  1. Job Run payload configuration in webhook_configurations - changing the event subscriptions in the webhook_configurations array or toggling the presence of custom headers don't influence the behaviour
  2. Make.com is highly-used automation platform and widely-used for accepting webhooks result from various services
Originally created by @AntonDobrev on GitHub (Aug 10, 2025). **Describe the bug** When running an extraction job with `webhook_configurations` with a receiving webhook configured in a low-code automation platform (Make.com), the webhook is never called, despite identical payloads being successfully delivered to `webhook.site`. The issue seems dependent on the target URL domain validation or HTTP connection handling. **Files** Not a file issue (though only testing with PDF files) **Job ID** Successful delivery to `webhook.site` - `8b08e69f-bdab-4c95-8e77-12d87f460b1c` **Not successful** to make.com webhook - `b7958bd8-9e10-46ae-8edf-b0bc8976e38d` **Client:** - API v1 **Additional context** 1. Working webhook URLs: - (tested) `https://webhook.site/unique-webhook-guid-here` - (as per the GitHub issues) `https://api-staging.mydomain.org/llama_cloud_webhook` Failing URLs: - (tested with webhook in make.com) `https://hook.eu1.make.com/unique-webhook-id` 2. Job Run payload configuration in `webhook_configurations` - changing the event subscriptions in the `webhook_configurations` array or toggling the presence of custom headers don't influence the behaviour 3. Make.com is highly-used automation platform and widely-used for accepting webhooks result from various services
yindo added the bug label 2026-02-16 00:18:06 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
LlamaCloud
LlamaExtract
LlamaParse
bug
client
complex layout
documentation
duplicate
enhancement
figure
font
header footer
help wanted
ocr
parser
pdf_debug
pdf_debug
pull-request
Mirrored from GitHub Pull Request
 python-lib
question
server_issue
server_issue
ui
No Label bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: run-llama/llama_cloud_services#515
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?