[N8N] Custom Body Not Being Applied in n8n Firecrawl Node
bug
Hi
I'm using the Firecrawl node in n8n with "Use Custom Body" enabled, but it appears that my custom body configuration is not being applied at all.
Here's my custom body:
{
"url": "{{ $json.url }}",
"formats": [
{
"fullPage": true,
"type": "screenshot"
},
{
"type": "json",
"prompt": "Extract product information...",
"schema": { /* my schema */ }
}
],
"waitFor": 30000,
"timeout": 179998,
"actions": [
{
"type": "wait",
"milliseconds": 3000
},
{
"type": "click",
"selector": "div.Overlay.EmailSignup button"
}
],
"location": {
"country": "US",
"languages": ["en-US"]
}
// ... other options
}
Expected behavior: The scrape should use my custom body parameters (screenshot format, JSON extraction, actions, etc.)
Actual behavior: The response suggests the custom body is being ignored - I'm only getting basic markdown output with none of the requested formats or custom configurations applied.
Questions:
Is custom body properly supported in the n8n integration?
Is there a specific syntax or structure required for custom body to work?
Should I be using a different approach to pass these advanced options?
Any help would be appreciated!
I'm using the Firecrawl node in n8n with "Use Custom Body" enabled, but it appears that my custom body configuration is not being applied at all.
Here's my custom body:
{
"url": "{{ $json.url }}",
"formats": [
{
"fullPage": true,
"type": "screenshot"
},
{
"type": "json",
"prompt": "Extract product information...",
"schema": { /* my schema */ }
}
],
"waitFor": 30000,
"timeout": 179998,
"actions": [
{
"type": "wait",
"milliseconds": 3000
},
{
"type": "click",
"selector": "div.Overlay.EmailSignup button"
}
],
"location": {
"country": "US",
"languages": ["en-US"]
}
// ... other options
}
Expected behavior: The scrape should use my custom body parameters (screenshot format, JSON extraction, actions, etc.)
Actual behavior: The response suggests the custom body is being ignored - I'm only getting basic markdown output with none of the requested formats or custom configurations applied.
Questions:
Is custom body properly supported in the n8n integration?
Is there a specific syntax or structure required for custom body to work?
Should I be using a different approach to pass these advanced options?
Any help would be appreciated!
