Instead of the <script> tag, use react-facebook or next-facebook for React/Next.js projects. For vanilla JS, use:
npm install facebook-sdk
Then import properly to avoid global namespace pollution.
| n8n Node | Setting | Why |
|----------|---------|-----|
| HTTP Request | Method: GET, URL: https://graph.facebook.com/v18.0/me/posts | Use versioned API |
| | Authentication: OAuth2 or Generic Credential | Never hardcode tokens |
| Code Node | Run once for all items | Avoid hitting rate limits |
| Error Trigger | Continue on fail + route to separate branch | Log errors without breaking automation | n8facebook3jsi7jserrore best
n8n automatically parses JSON responses. However, Facebook's API sometimes returns "wrapped" JSON or inconsistent structures (e.g., an empty object {} instead of a data array).
If you try to reference $json.data.id in a Function node or an Expression, and Facebook returns an error object instead, n8n throws a ReferenceError. Instead of the <script> tag, use react-facebook or
The Solution: Use the Code Node with defensive programming.
// Instead of direct referencing: // return items[0].json.data.id;
// Use optional chaining: const postId = items[0].json?.data?.id || 'fallback_or_error_handling'; return postId ;Then import properly to avoid global namespace pollution
Facebook error codes are usually like #200, #10, #100, not alphanumeric strings like this. But if you saw this on screen, it could be:
Suggested error message content:
“An unexpected error occurred. Please clear your browser cache and cookies, then reload Facebook. If the issue persists, check Facebook’s server status.”