[N8N] Custom Body Not Being Applied in n8n Firecrawl Node
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!
8 Replies
Can you clear out the additional fields if you are using a custom body? They are probably just conflicting.
Hi. micah.stairs.
This is my custombody.
{"url": {{ $json.url }},
"formats": [
{
"fullPage": true,
"type": "screenshot"
},
{
"type": "json",
"prompt": "Extract product~~~~ OUTPUT: Valid JSON only.",
"schema": {}
}
],
"onlyMainContent": true,
"includeTags": [
"<string>"
],
"excludeTags": [
"<string>"
],
"maxAge": 172800000,
"headers": {},
"waitFor": 30000,
"mobile": false,
"skipTlsVerification": true,
"timeout": 179998,
"parsers": [
"pdf"
],
"actions": [
{
"type": "wait",
"milliseconds": 3000,
"selector": "#my-element"
},
{
"all": true,
"type": "click",
"selector": "div.Overlay.EmailSignup button"
}
],
"location": {
"country": "US",
"languages": [
"en-US"
]
},
"removeBase64Images": true,
"blockAds": true,
"proxy": "auto",
"storeInCache": true,
"zeroDataRetention": false
}
When I send it like this, I get the same response as if nothing was configured.
The same value is returned even when I send it with an empty custom body.
Can you share a job ID? I can verify whether we received the parameters you specified.
I think this might be the one. Could you verify whether the information here is correct?
{
"google-site-verification": "Wws-Fq-agruoQjHyvs_kzYIYVteoRd1GpPLaOOH9zj0",
"og:url": "https://www.modaoperandi.com/women/p/jacquemus/le-petit-calino/657993",
"og:description": "Shop the Neutral The Calino Petit Leather Bag by Jacquemus and more new designer fashion on Moda Operandi.",
"og:title": "The Calino Petit Leather Bag By Jacquemus | Moda Operandi",
"og:image": "https://cdn.modaoperandi.com/assets/images/products/1014244/657993/medium_jacquemus-neutral-le-petit-calino.jpg?_v=1763739743",
"position": [
"1",
"2",
"3",
"4"
],
"theme-color": "rgb(248, 245, 238)",
"apple-itunes-app": "app-id=781702094, app-argument=/women/p/jacquemus/le-petit-calino/657993",
"fb:app_id": "116030325161657",
"title": "The Calino Petit Leather Bag By Jacquemus | Moda Operandi",
"viewport": "width=device-width, initial-scale=1.0, minimum-scale=1.0",
"description": "Shop the Neutral The Calino Petit Leather Bag by Jacquemus and more new designer fashion on Moda Operandi.",
"language": "en-US",
"og:site_name": "Moda Operandi",
"favicon": "https://www.modaoperandi.com/dist/public/favicon.png",
"scrapeId": "cf82ccaa-0fe2-4d54-8ff2-291383e2d228",
"sourceURL": "www.modaoperandi.com/women/p/jacquemus/le-petit-calino/657993",
"url": "https://www.modaoperandi.com/women/p/jacquemus/le-petit-calino/657993",
"statusCode": 200,
"contentType": "text/html; charset=utf-8",
"proxyUsed": "basic",
"cacheState": "hit",
"cachedAt": "2025-11-25T14:31:16.104Z",
"creditsUsed": 1
}
Moda Operandi
The Calino Petit Leather Bag By Jacquemus | Moda Operandi
Shop the Neutral The Calino Petit Leather Bag by Jacquemus and more new designer fashion on Moda Operandi.
Hi @donddaeng, instead of relying on the custom body field in the Firecrawl node, I’d recommend using n8n’s built-in HTTP Request node and calling the Firecrawl /v2/scrape API directly. This lets you send the full JSON body (formats, actions, location, etc.) exactly as the Firecrawl API expects, and avoids the limitations of the current community node.
Hi Himanshu.
Yes, I was hoping to avoid that, but it looks like there’s no other choice. Thank you!
I don't think you're using the official Firecrawl node though? Looks like you're using one of the community nodes, which is not officially supported by the Firecrawl team.
Ah, I see—I misunderstood. Sorry about that.
It wasn’t an official node.
I was using this one instead: https://www.npmjs.com/package/@mendable/n8n-nodes-firecrawl
Thanks.