Portal Community
BizFirstAI Portal / Nodes / Facebook / Examples

Examples

Worked workflow patterns using the Facebook node

1. Publish a Post and Attach a Follow-Up Image

Publish a text update, then upload a supporting image as a separate photo post.

  1. Facebook node: resource=page, operation=post, pageId={{pageId}}, message="New feature just shipped!"
  2. Facebook node: resource=media, operation=uploadImage, pageId={{pageId}}, imageUrl={{screenshotUrl}}, caption="See it in action"
Why two steps: Graph's /{pageId}/feed post endpoint can attach one picture inline, but for a photo you want indexed as its own Page photo (not just an attachment), a separate media.uploadImage call is the correct approach.

2. Auto-Reply to New Comments on a Post

Poll a post's comments and acknowledge new ones automatically.

  1. Store the highest comment ID/timestamp already processed.
  2. On each run: Facebook node, resource=post, operation=getComments, postId={{postId}}, limit=25
  3. Filter step: keep only comments newer than the stored checkpoint.
  4. For each new comment: Facebook node, resource=post, operation=comment — but note this adds a top-level comment on the post, not a threaded reply to the specific commenter; combine with a mention (@[commentAuthorId] in message) if you want to address them by name.
  5. Update the stored checkpoint to the newest comment seen.

3. Hide Spam Comments Matching a Keyword List

  1. Facebook node: resource=post, operation=getComments, postId={{postId}}
  2. Filter step: keep comments whose message matches a spam keyword/regex list.
  3. For each match: Facebook node, resource=moderation, operation=hideComment, commentId={{matchedCommentId}}, isHidden=true
Tip: Prefer hideComment over deleteComment here — hiding is reversible if the keyword filter has a false positive; deletion is not (see Moderation).

4. Reply to a Messenger Conversation from a Support Queue

  1. Facebook node: resource=message, operation=getConversations, pageId={{pageId}}, limit=25
  2. Transform/branch step: pick the conversation(s) needing a reply and extract the sender's PSID.
  3. Facebook node: resource=message, operation=send, recipientId={{senderPsid}}, messageText="Thanks for reaching out — a team member will follow up shortly."
Mind the 24-hour window: if the queued conversation's last inbound message is older than 24 hours, send will fail with a Graph permission error — see Message Operations.

5. Weekly Page Performance Snapshot

  1. Facebook node: resource=page, operation=getInfo, pageId={{pageId}} → capture fanCount
  2. Facebook node: resource=page, operation=getInsights, pageId={{pageId}}, period=week
  3. Transform step: parse the raw data JSON and assemble a summary.
  4. Send the summary via email/Slack/whatever notification node is configured for the workflow.