Replies: 2 comments
-
|
I'm having the same issue. I'm using n8n with crawl4ai both in a docker compose file and when I go to /crawl I get back the scrape not the task_id. This is fine for small scrapes but won't work well for launching larger jobs. |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
Have you guys figured this out in n8n? Any pointers would be appreciated. thanks. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
I was initially (a few weeks ago) using Crawl4AI as a Docker service and receiving task IDs after submitting crawl requests with curl. I recently discovered n8n the low code tool can also utilize the Crawl4AI Docker API. I’m now finding that I’m unable to retrieve a task ID from Crawl4AI I get the results immediately or have to wait a few seconds to receive them. Has anyone else experienced a change in the Crawl4AI API regarding task IDs? Any insights would be appreciated!
There must be wait for enable the task_id workflow as there's a load of tutorials out there that depend on that feature.
Beta Was this translation helpful? Give feedback.
All reactions