Resources · n8n integration

Facebook n8n integrationAutomate Facebook with n8n.

Everything starts with an event here, never with an action. The Facebook n8n integration is one trigger node: it subscribes to Meta webhooks and wakes a workflow when one of 11 objects changes, from a Page feed to an Instagram comment. For teams watching a page, an ad account or a Workplace group.

Try the Facebook integration on n8n

Verified Trustpilot reviews · AI, automation & growth agency

Why automate

What does the Facebook n8n integration actually cover?

The Facebook n8n integration is a trigger, not an action node. n8n ships a Facebook Trigger that registers a webhook with Meta, meaning a URL Facebook calls whenever something changes, and starts your workflow on that call. It covers 11 objects and 11 event families, so the question is never whether n8n can listen, but which object carries the change you care about.

Three shapes of workflow come back constantly. The first watches a Page: pick the page object, keep the Feed and Ratings fields, and every new review or post lands in a channel where someone answers it. Routing that item to Slack takes one more node and turns a page nobody refreshes into a queue somebody clears.

The second listens to instagram. Comments and @mentions on your app users' media arrive as they happen, and a single append node writes them into Google Sheets or Airtable with the media reference attached. Community managers stop scrolling to build their weekly recap because the recap builds itself.

The third is quieter and saves the most money. The adAccount object exposes With Issues Ad Objects, which fires when a campaign, ad set or ad gets the WITH_ISSUES status. Send that straight to Gmail and the person who owns the budget hears about a stalled ad the same day, not at the end of the month.

What the trigger cannot do is push anything back. This catalogue entry has no action node and no operations at all, so replying to a comment, publishing a post or pausing a campaign goes through HTTP Request, which calls any Graph API endpoint while reusing the same credential through predefined authentication. Plan for it: a realistic Facebook workflow is one trigger node plus one or two HTTP Request nodes.

Two limits are worth knowing before you start. n8n recommends the WhatsApp Trigger node with WhatsApp credentials over the whatsappBusinessAccount object, because that node exposes more events to subscribe to. And the page object has real prerequisites, listed below, that have nothing to do with n8n and everything to do with Meta's app review. If you are still choosing a platform, the n8n review goes through the trade-offs in detail.

Connect

How do you connect Facebook to n8n?

  1. 01

    Create the Facebook App credential

    In n8n, open the Credentials menu and create a Facebook App credential. A credential is created once and reused across every workflow, and the node offers it in its dropdown, so you never paste secrets into a node again. The trigger also exposes an Authentication parameter that picks the authentication method to use. Whatever you create here has to belong to a real Facebook app, because the next step asks for that app's identifier.

  2. 02

    Enter the APP ID

    APP ID is the only required text field on the node, and it takes the identifier of the app connected to your credential. It is a required field, so n8n blocks the execution if you leave it empty. Type it once, and the pairing between credential and app is done. If the wrong app sits behind the credential, the webhook registers fine and then never delivers anything, which is a slow way to lose an afternoon.

  3. 03

    Pick the Object, then activate

    Object chooses what you listen to, and Field Names or IDs narrows it down. By default the node uses the * wildcard and triggers on every available event for that object; click the X on the star and select from the dropdown, or use an expression, to keep only what you need. Then activate the workflow. n8n registers the webhook at activation, and events arrive within seconds, with no polling.

Triggers

What can the Facebook Trigger listen to?

Facebook Trigger is the node that starts a workflow when something happens in Facebook. It listens to 11 events, listed below by family. Pick one or several, activate the workflow: n8n registers the webhook on your Facebook account.

What you see in n8n

Every event, by family

One row per object, one chip per action. The event to tick in the node is object.action; hover a chip to read exactly when it fires.

ad.*1
    application.*1
    • application.
      • application
    certificate.*1
      group.*1
      • group.
        • group
      instagram.*1
      • instagram.
        • instagram
      link.*1
      • link.
        • link
      page.*1
      • page.
        • page
      permissions.*1
      • permissions.
        • permissions
      user.*1
      • user.
        • user
      whatsapp.*1
        workplace.*1

          Configuration notes

          01Configure the Facebook TriggerOne trigger node, version 1, covers the whole integration. It starts a workflow when Facebook events occur, and the catalogue splits those into 11 objects, each one its own event family. There is no catch-all object, so you choose a subject before you choose a signal.

          One trigger node, version 1, covers the whole integration. It starts a workflow when Facebook events occur, and the catalogue splits those into 11 objects, each one its own event family. There is no catch-all object, so you choose a subject before you choose a signal.

          Key parameters

          • Object: a single-choice dropdown, so one node listens to one object. Watching a Page and an ad account means two Facebook Trigger nodes in the same workflow.
          • Field Names or IDs: a multi-select that defaults to the * wildcard. Remove the star to subscribe to specific fields only, or drive the list with an expression.
          • Include Values, under Options: decides whether change notifications carry the new values. Required by most objects.
          Use cases
          a workflow that reacts to one clear signal, like a review or an ad status, rather than a firehose you filter downstream.
          02Page and Instagram ObjectsThese two carry the social workload. The page object reports page updates: Feed describes most changes to a page's feed, including posts, likes and shares, while Ratings covers new ratings and reactions to them, Mention catches new mentions, Leadgen signals a change in lead generation settings, and Live Videos, Videos, Product Review, Merchant Review, Page Change Proposal and Page Upcoming Change fill in the rest. The instagram object notifies you when someone comments on your app users' media, @mentions them, or when their Stories expire, through Comments, Mentions, Messages, Messaging Seen, Messaging Handover, Standby and Story Insights.

          These two carry the social workload. The page object reports page updates: Feed describes most changes to a page's feed, including posts, likes and shares, while Ratings covers new ratings and reactions to them, Mention catches new mentions, Leadgen signals a change in lead generation settings, and Live Videos, Videos, Product Review, Merchant Review, Page Change Proposal and Page Upcoming Change fill in the rest. The instagram object notifies you when someone comments on your app users' media, @mentions them, or when their Stories expire, through Comments, Mentions, Messages, Messaging Seen, Messaging Handover, Standby and Story Insights.

          Key parameters

          • Field Names or IDs: with page the dropdown also lists individual profile fields, so you can watch a single setting instead of the whole feed.
          When to use it
          anything customer-facing that deserves an answer the same hour.
          03Ad Account and Application ObjectsAdvertising and app plumbing sit here. adAccount gets updates about certain ads changes, with In Process Ad Objects notifying you when a campaign, ad set or ad leaves the IN_PROCESS status, and With Issues Ad Objects when one of them picks up the WITH_ISSUES status. Both cover post-processing for ad creation and edits, which is exactly the window where a creative silently stops serving. application gets updates sent to the app itself: Add Account, Ads Rules Engine, Async Requests, Async Sessions, Group Install, Oe Reseller Onboarding Request Created, Plugin Comment and Plugin Comment Reply.

          Advertising and app plumbing sit here. adAccount gets updates about certain ads changes, with In Process Ad Objects notifying you when a campaign, ad set or ad leaves the IN_PROCESS status, and With Issues Ad Objects when one of them picks up the WITH_ISSUES status. Both cover post-processing for ad creation and edits, which is exactly the window where a creative silently stops serving. application gets updates sent to the app itself: Add Account, Ads Rules Engine, Async Requests, Async Sessions, Group Install, Oe Reseller Onboarding Request Created, Plugin Comment and Plugin Comment Reply.

          Key parameters

          • Include Values: both objects fail without the toggle on, and an ad status change with no values attached tells you nothing anyway.
          Use cases
          alerting a media buyer on a broken ad, or tracking async jobs your own app kicks off.
          04Group, Link and Workplace Security ObjectsWorkplace has its own corner of the trigger. group gets updates about activity in groups and events in groups for Workplace, which is the closest thing to an internal feed you can automate. link gets updates about links for rich previews by an external provider, useful when an internal tool renders previews and you want to know what got shared. workplaceSecurity reports security events like adding or removing admins, and users joining or leaving a Workplace.

          Workplace has its own corner of the trigger. group gets updates about activity in groups and events in groups for Workplace, which is the closest thing to an internal feed you can automate. link gets updates about links for rich previews by an external provider, useful when an internal tool renders previews and you want to know what got shared. workplaceSecurity reports security events like adding or removing admins, and users joining or leaving a Workplace.

          Key parameters

          • Field Names or IDs: these three objects publish no curated shortlist in the docs, so the * wildcard is the honest default and you filter in the workflow.
          • Include Values: required by all three; without it the notification arrives empty.
          When to use it
          compliance and onboarding trails, where a joiner or a new admin has to be logged somewhere outside Workplace.
          05User, Permissions, Certificate Transparency and WhatsApp Business Account ObjectsFour account-level objects close the list. user sends user profile updates, and permissions fires when someone grants or revokes a permission for your app, which is the signal to stop calling an endpoint you no longer have rights on. certificateTransparency notifies you when a new certificate is issued for a domain you subscribed for alerts, split between Certificate and Phishing, the second covering certificates that may be impersonating one of your legitimate domains. whatsappBusinessAccount reports changes to a WhatsApp Business Account through Message Template Status Update, Phone Number Name Update, Phone Number Quality Update, Account Review Update and Account Update.

          Four account-level objects close the list. user sends user profile updates, and permissions fires when someone grants or revokes a permission for your app, which is the signal to stop calling an endpoint you no longer have rights on. certificateTransparency notifies you when a new certificate is issued for a domain you subscribed for alerts, split between Certificate and Phishing, the second covering certificates that may be impersonating one of your legitimate domains. whatsappBusinessAccount reports changes to a WhatsApp Business Account through Message Template Status Update, Phone Number Name Update, Phone Number Quality Update, Account Review Update and Account Update.

          Key parameters

          • Include Values: optional on user and permissions, required on the other two.
          When to use it
          security and account hygiene, not marketing.
          Need help

          Need help automating Facebook with n8n?

          A person reads every message.

          FAQ

          Facebook and n8n, the questions that come next

          01Is the Facebook n8n integration free?
          Yes, on the n8n side. The Facebook Trigger ships with n8n, so there is nothing to install and no extra cost, and it behaves the same on n8n Cloud and on a self-hosted instance running the Community Edition under the Sustainable Use licence. A workflow built on one runs identically on the other, which matters if you prototype on Cloud and move to your own server later. What Meta charges for the app, the ad account or the WhatsApp Business Account is a separate question this page does not cover. The only real cost is setup time: one credential, one APP ID, one object, and the webhook does the rest.
          02What credentials does the Facebook Trigger need?
          A Facebook App credential, created once in the Credentials menu and reused in every workflow that touches Facebook. The node also carries an Authentication parameter that selects the authentication method to use, and an APP ID field that must hold the identifier of the app sitting behind that credential. Beyond that, some objects add their own prerequisites on Meta's side. The page object needs a page admin to grant the manage_pages permission to your app, that admin to hold at least moderator privileges, and the app to be added to the page, sometimes with a subscribed_apps call through the Graph API explorer. The WhatsApp Business Account object requires an app owned by your business, subscribed under the account.
          03What are the limits of Facebook in n8n?
          The big one: there is no Facebook action node here. The catalogue lists 0 operations and 0 resources, so n8n can hear Facebook but cannot speak to it from this integration. Anything outbound, replying to a comment, publishing, pausing a campaign, goes through HTTP Request against the Graph API, reusing the same credential via predefined authentication. Second limit: no wildcard object exists, so one node listens to exactly one of the 11 objects. Third: n8n itself recommends the WhatsApp Trigger node with WhatsApp credentials rather than the whatsappBusinessAccount object, because it exposes more events. And Certificate Transparency only works on domains you have already subscribed for certificate or phishing alerts.
          04Does the Facebook Trigger fire in real time?
          Yes. It works by webhook, not by polling. n8n registers the webhook URL with Facebook when you activate the workflow, and from then on Meta pushes each event to that URL, so it arrives within seconds. Nothing checks an API on a schedule, which means no interval to tune and no window where a change sits unnoticed. Two practical consequences. An inactive workflow has no registered webhook, so test with the workflow active if you want real deliveries. And the trigger only carries what Facebook sends: turn on Include Values in Options, or most objects deliver nothing usable, and several fail outright.
          05n8n or Make for Facebook?
          It depends on where your data can live and how you want to pay. Make is hosted only, with no self-hosting option, and bills per operation, so a chatty webhook on a busy Page has a running cost that scales with volume. n8n runs on Cloud or on your own infrastructure, which is usually the deciding factor when a legal or security team has an opinion about where Facebook event payloads land. On features, be realistic about this specific integration: n8n gives you a trigger with 11 objects and no action node, so the outbound half of the job runs on HTTP Request either way. Both tools build visually. Pick on hosting, data control and cost model.
          Hack'celeration Lab

          Get our weekly integration tips.

          No spam. Unsubscribe anytime.

          Same platform

          Other docs you might need on this stack.

          Browse all integrations