Overview
Section titled “Overview”Facebook is a social media and advertising platform used by individuals and businesses to connect, share content, and promote products or services. This integration supports Facebook Pages only — it does not work with personal profiles. With the SquadOS integration, your agents can create and schedule posts, reply to comments, send Messenger messages, manage Page collaborator roles, and query engagement and reach metrics, all in an automated fashion.
- Official website: https://www.facebook.com/
- Composio documentation: docs.composio.dev/toolkits/facebook
Authentication
Section titled “Authentication”This tool uses OAuth 2.0 (OAUTH2) to connect.
You will need the following fields:
| Field | Required | Description |
|---|---|---|
access_token | Yes | OAuth 2.0 access token obtained by authorizing the Meta app on your Facebook account. Managed automatically by Composio during the connection flow. |
How to get credentials
Section titled “How to get credentials”Authentication is done via OAuth 2.0 — you do not need to generate tokens manually. The complete flow is described on the official Composio page for this integration:
- Visit composio.dev/auth/facebook for the step-by-step guide on configuring custom OAuth credentials for Meta (Facebook).
- Create a Meta app on Meta for Developers and configure the required permissions (e.g.,
pages_manage_posts,pages_read_engagement,pages_messaging). - In Composio, use the OAuth connection flow to authorize access — Composio manages token retrieval and refresh automatically.
How to connect in SquadOS
Section titled “How to connect in SquadOS”- Go to Tools in the side menu (
/admin/tools). - Open the Available tab and search for
Facebook. - Click the card to open the details modal and hit Connect.
- You’re taken to the secure connection page hosted by Composio, where you authorize access to your Meta account (OAuth 2.0).
- Once done, you’re sent back to SquadOS with the account connected and the tool available to your agents. (Connection-flow details in Organization Tools.)
How do I set up custom OAuth credentials for Meta (Facebook)?
Section titled “How do I set up custom OAuth credentials for Meta (Facebook)?”For a step-by-step guide on creating and configuring your own Meta (Facebook) OAuth credentials with Composio, see How to create OAuth credentials for Meta (Facebook).
Available actions
Section titled “Available actions”Assign Page Task
Section titled “Assign Page Task”FACEBOOK_ASSIGN_PAGE_TASK
Assigns tasks/roles to a business-scoped user or system user for a specific Facebook Page. Important: This action requires a business-scoped user ID or system user ID from Facebook Business Manager. Regular Facebook user IDs cannot be used. The page must also be managed through Facebook Business Manager for this action to work. Required permissions: business_management, pages_manage_metadata
Input parameters
Section titled “Input parameters”| Name | Type | Required | Description |
|---|---|---|---|
user | string | Yes | The business-scoped user ID or system user ID to assign tasks to. Note: Regular Facebook user IDs are not accepted - only business-scoped IDs (from Business Manager) or system user IDs can be used with this endpoint. |
tasks | array | Yes | List of tasks to assign. Valid values include: ‘MANAGE’, ‘CREATE_CONTENT’, ‘MODERATE’, ‘ADVERTISE’, ‘ANALYZE’, ‘MESSAGING’. Example: [‘MANAGE’, ‘CREATE_CONTENT’] |
page_id | string | Yes | The ID of the Facebook Page |
Output
Section titled “Output”| Name | Type | Required | Description |
|---|---|---|---|
data | string | Yes | Data from the action execution |
error | string | No | Error if any occurred during the execution of the action |
successful | boolean | Yes | Whether or not the action execution was successful or not |
Create Comment
Section titled “Create Comment”FACEBOOK_CREATE_COMMENT
Creates a comment on a Facebook post or replies to an existing comment.
Input parameters
Section titled “Input parameters”| Name | Type | Required | Description |
|---|---|---|---|
message | string | Yes | The text content of the comment |
object_id | string | Yes | The ID of the post or comment to comment on. Must be a numeric ID (e.g., ‘3071372469667482’) or compound format ‘pageId_postId’ (e.g., ‘678465505624869_3071372469667482’). Do not include prefixes like ‘post_’, ‘id_’, or ‘p’. |
attachment_id | string | No | ID of an unpublished photo to attach to the comment |
attachment_url | string | No | URL of a photo to attach to the comment |
attachment_share_url | string | No | URL of a GIF to attach to the comment |
Output
Section titled “Output”| Name | Type | Required | Description |
|---|---|---|---|
data | string | Yes | Data from the action execution |
error | string | No | Error if any occurred during the execution of the action |
successful | boolean | Yes | Whether or not the action execution was successful or not |
Create Photo Album
Section titled “Create Photo Album”FACEBOOK_CREATE_PHOTO_ALBUM
Creates a new photo album on a Facebook Page. Note: This endpoint requires the ‘pages_manage_posts’ permission or equivalent permissions to be granted to your Facebook application. This action is publicly visible on the Page; confirm with the user before calling.
Input parameters
Section titled “Input parameters”| Name | Type | Required | Description |
|---|---|---|---|
name | string | Yes | Name of the photo album |
message | string | No | Description of the album |
page_id | string | Yes | The ID of the Facebook Page Must be a Facebook Page ID — personal profile or user timeline IDs are invalid. |
privacy | object | No | Privacy settings for the album (e.g., {'value': 'EVERYONE'}) |
location | string | No | Location associated with the album |
Output
Section titled “Output”| Name | Type | Required | Description |
|---|---|---|---|
data | string | Yes | Data from the action execution |
error | string | No | Error if any occurred during the execution of the action |
successful | boolean | Yes | Whether or not the action execution was successful or not |
Create Photo Post
Section titled “Create Photo Post”FACEBOOK_CREATE_PHOTO_POST
Creates a photo post on a Facebook Page. Requires an image to be provided via either ‘url’ (publicly accessible image URL) or ‘photo’ (local image file upload). This action is specifically for posting images with optional captions, not text-only posts. Returns a composite post_id (PageID_PostID); use this for follow-up operations, not the photo/media id alone.
Input parameters
Section titled “Input parameters”| Name | Type | Required | Description |
|---|---|---|---|
url | string | No | URL of a publicly accessible image to upload. Supports direct image links with or without file extensions. The image host must not block requests from Facebook. Cannot be a Facebook URL. At least one of ‘url’, ‘photo’, or ‘media’ is required. The URL must return an image MIME type directly — redirects or HTML pages cause upload failures. |
media | object | No | Alias for ‘photo’. for uploading a local image file (e.g. .jpg, .png, .gif). At least one of ‘media’, ‘photo’, or ‘url’ is required. |
photo | object | No | for uploading a local image file (e.g. .jpg, .png, .gif). At least one of ‘photo’, ‘url’, or ‘media’ is required. |
message | string | No | Caption text for the photo. Can also be provided as ‘caption’. |
page_id | string | Yes | The numeric ID of the Facebook Page to post to. Can be provided as a string or number. |
published | boolean | No | Set to true to publish immediately, false to save as unpublished |
backdated_time | integer | No | Unix timestamp to backdate the post |
scheduled_publish_time | integer | No | Unix timestamp for scheduled posts (required if published=false) Must be a future UTC epoch timestamp. Providing this with published=true triggers a 400 validation error. |
backdated_time_granularity | string | No | Granularity of backdated time: year, month, day, hour, or min |
Output
Section titled “Output”| Name | Type | Required | Description |
|---|---|---|---|
data | string | Yes | Data from the action execution |
error | string | No | Error if any occurred during the execution of the action |
successful | boolean | Yes | Whether or not the action execution was successful or not |
Create Post
Section titled “Create Post”FACEBOOK_CREATE_POST
Creates a new text or link post on a Facebook Page. Requires pages_manage_posts permission and manage-level Page role on the target Page. For image posts use FACEBOOK_CREATE_PHOTO_POST; for video posts use FACEBOOK_CREATE_VIDEO_POST — media fields are not supported here. Returns a composite post ID in PageID_PostID format, required for FACEBOOK_GET_POST retrieval.
Input parameters
Section titled “Input parameters”| Name | Type | Required | Description |
|---|---|---|---|
link | string | No | URL to include in the post |
message | string | Yes | The text content of the post At least one of message or link must be non-empty; omitting both causes a validation error. |
page_id | string | Yes | The numeric ID of the Facebook Page to post to. This is a numeric string (e.g., ‘123456789012345’). To obtain a valid page_id, use the ‘Get User Pages’ or ‘List Managed Pages’ action which returns page IDs for pages you have access to manage. |
published | boolean | No | Set to true to publish immediately, false to save as draft or schedule |
targeting | object | No | Audience targeting specifications |
scheduled_publish_time | integer | No | Unix timestamp for when the post should be published. Must be at least 10 minutes in the future. When provided, published must be false (will be auto-set to false if true). Must be Unix UTC epoch (not local time); timezone mismatches cause validation failures. |
Output
Section titled “Output”| Name | Type | Required | Description |
|---|---|---|---|
data | string | Yes | Data from the action execution |
error | string | No | Error if any occurred during the execution of the action |
successful | boolean | Yes | Whether or not the action execution was successful or not |
Create Video Post
Section titled “Create Video Post”FACEBOOK_CREATE_VIDEO_POST
Creates a video post on a Facebook Page. Requires a Page access token with pages_manage_posts scope and manage-level permissions on the target page.
Input parameters
Section titled “Input parameters”| Name | Type | Required | Description |
|---|---|---|---|
title | string | No | Title of the video |
video | object | No | Local video file to upload. At least one of ‘video’ or ‘file_url’ must be provided. |
page_id | string | Yes | The ID of the Facebook Page Must be a Facebook Page ID (not a personal profile ID); the authenticated token must have manage-level access. |
file_url | string | No | URL of the video file to upload. At least one of ‘file_url’ or ‘video’ must be provided. Must be a direct download URL (e.g., direct MP4 link), not a watch/share URL. Use MP4 with H.264/AAC encoding; unsupported formats or very large files may fail. |
published | boolean | No | Whether to publish immediately |
targeting | object | No | Audience targeting specifications |
description | string | No | Description of the video |
scheduled_publish_time | integer | No | Unix timestamp to schedule the video post Requires published=false; must be a UTC Unix epoch at least ~10 minutes in the future. Combining with published=true or omitting when published=false causes 400 errors. |
Output
Section titled “Output”| Name | Type | Required | Description |
|---|---|---|---|
data | string | Yes | Data from the action execution |
error | string | No | Error if any occurred during the execution of the action |
successful | boolean | Yes | Whether or not the action execution was successful or not |
Delete Comment
Section titled “Delete Comment”FACEBOOK_DELETE_COMMENT
Deletes a Facebook comment. Requires a Page Access Token with appropriate permissions for comments on Page-owned content. The page_id parameter helps ensure the correct page token is used for authentication.
Input parameters
Section titled “Input parameters”| Name | Type | Required | Description |
|---|---|---|---|
page_id | string | No | Optional: The ID of the Facebook Page that owns the post containing this comment. If not provided, the action will use the first available managed page. Providing the correct page_id ensures proper authentication. |
comment_id | string | Yes | The ID of the comment to delete. Can be in format ‘parentId_commentId’ (e.g., ‘122157027176937815_1371138271476143’) or just the comment ID. |
Output
Section titled “Output”| Name | Type | Required | Description |
|---|---|---|---|
data | string | Yes | Data from the action execution |
error | string | No | Error if any occurred during the execution of the action |
successful | boolean | Yes | Whether or not the action execution was successful or not |
Delete Post
Section titled “Delete Post”FACEBOOK_DELETE_POST
Permanently deletes a Facebook Page post. Deletion is irreversible — deleted posts cannot be recovered. For bulk deletions, keep throughput to ~1 delete/second to avoid Graph API rate limits.
Input parameters
Section titled “Input parameters”| Name | Type | Required | Description |
|---|---|---|---|
post_id | string | Yes | The ID of the post to delete The token must have Page-level delete permissions for this post. Posts created by other users or requiring elevated Page roles may not be deletable. |
Output
Section titled “Output”| Name | Type | Required | Description |
|---|---|---|---|
data | string | Yes | Data from the action execution |
error | string | No | Error if any occurred during the execution of the action |
successful | boolean | Yes | Whether or not the action execution was successful or not |
Get Comment
Section titled “Get Comment”FACEBOOK_GET_COMMENT
Retrieves details of a specific Facebook comment.
Input parameters
Section titled “Input parameters”| Name | Type | Required | Description |
|---|---|---|---|
fields | string | No | Comma-separated list of fields to return |
comment_id | string | Yes | The ID of the comment to retrieve |
Output
Section titled “Output”| Name | Type | Required | Description |
|---|---|---|---|
data | string | Yes | Data from the action execution |
error | string | No | Error if any occurred during the execution of the action |
successful | boolean | Yes | Whether or not the action execution was successful or not |
Get Comments
Section titled “Get Comments”FACEBOOK_GET_COMMENTS
Retrieves comments from a Facebook post or comment (for replies). This endpoint requires appropriate permissions: - For page-owned posts: A Page Access Token with ‘pages_read_engagement’ permission - The API automatically swaps user tokens for page tokens when available API Version: Uses v23.0 which was released May 2025.
Input parameters
Section titled “Input parameters”| Name | Type | Required | Description |
|---|---|---|---|
limit | integer | No | Number of comments to return (max 100) |
order | string | No | Order of comments: ‘chronological’ (oldest first) or ‘reverse_chronological’ (newest first, default). |
fields | string | No | Comma-separated list of fields to return for each comment. Available fields: id, message, created_time, from, attachment, comment_count, like_count, is_hidden, user_likes, can_comment, can_remove, can_hide, permalink_url, parent, comments (for nested replies). Note: ‘from’ field requires a Page Token to access user information (since Graph API v2.11). |
filter | string | No | Filter comments by type: ‘stream’ returns all comments including replies in flat list (default), ‘toplevel’ returns only top-level comments without replies. |
object_id | string | Yes | The ID of the post or comment to get comments from. Must be in full format ‘pageId_postId’ for posts (e.g., ‘123456789_987654321’). For comments, use the comment ID directly. |
Output
Section titled “Output”| Name | Type | Required | Description |
|---|---|---|---|
data | string | Yes | Data from the action execution |
error | string | No | Error if any occurred during the execution of the action |
successful | boolean | Yes | Whether or not the action execution was successful or not |
Get Conversation Messages
Section titled “Get Conversation Messages”FACEBOOK_GET_CONVERSATION_MESSAGES
Retrieves messages from a specific conversation.
Input parameters
Section titled “Input parameters”| Name | Type | Required | Description |
|---|---|---|---|
limit | integer | No | Number of messages to return (max 25) To retrieve full histories, paginate using paging.cursors.after or the next URL from the response. |
fields | string | No | Comma-separated list of fields to return for each message. Available fields include: id, created_time, from, to, message, attachments, sticker, shares, tags. |
page_id | string | Yes | The ID of the Facebook Page that owns the conversation. Required to obtain the correct page access token. Get this from the List Managed Pages action. |
conversation_id | string | Yes | The ID of the conversation in the format ‘t_’ followed by a numeric ID (e.g., ‘t_3638640842939952’). Obtain valid conversation IDs from the Get Page Conversations action. If a numeric-only ID is provided, the ‘t_’ prefix will be added automatically. |
Output
Section titled “Output”| Name | Type | Required | Description |
|---|---|---|---|
data | string | Yes | Data from the action execution |
error | string | No | Error if any occurred during the execution of the action |
successful | boolean | Yes | Whether or not the action execution was successful or not |
Get Current User
Section titled “Get Current User”FACEBOOK_GET_CURRENT_USER
Validates the access token and retrieves the authenticated user’s own profile via /me. Cannot fetch arbitrary users by name or ID.
Input parameters
Section titled “Input parameters”| Name | Type | Required | Description |
|---|---|---|---|
fields | string | No | Comma-separated list of fields to return for the current user Fields are silently omitted or return null if the access token lacks the required Facebook permissions — including defaults like email. Handle missing fields defensively. |
Output
Section titled “Output”| Name | Type | Required | Description |
|---|---|---|---|
data | string | Yes | Data from the action execution |
error | string | No | Error if any occurred during the execution of the action |
successful | boolean | Yes | Whether or not the action execution was successful or not |
Get Message Details
Section titled “Get Message Details”FACEBOOK_GET_MESSAGE_DETAILS
Retrieves details of a specific message sent or received by the Page.
Input parameters
Section titled “Input parameters”| Name | Type | Required | Description |
|---|---|---|---|
fields | string | No | Comma-separated list of fields to return |
message_id | string | Yes | The ID of the message to retrieve details for |
Output
Section titled “Output”| Name | Type | Required | Description |
|---|---|---|---|
data | string | Yes | Data from the action execution |
error | string | No | Error if any occurred during the execution of the action |
successful | boolean | Yes | Whether or not the action execution was successful or not |
Get Page Conversations
Section titled “Get Page Conversations”FACEBOOK_GET_PAGE_CONVERSATIONS
Retrieves a list of conversations between users and the Page.
Input parameters
Section titled “Input parameters”| Name | Type | Required | Description |
|---|---|---|---|
limit | integer | No | Number of conversations to return (max 25) Use paging.cursors.after or paging.next from the response to paginate beyond the first page. |
fields | string | No | Comma-separated list of fields to return for each conversation Avoid requesting heavy nested fields (e.g., embedded messages) to prevent large payloads. |
page_id | string | Yes | The ID of the Facebook Page. Numeric IDs are accepted and will be converted to strings. |
Output
Section titled “Output”| Name | Type | Required | Description |
|---|---|---|---|
data | string | Yes | Data from the action execution |
error | string | No | Error if any occurred during the execution of the action |
successful | boolean | Yes | Whether or not the action execution was successful or not |
Get Page Details
Section titled “Get Page Details”FACEBOOK_GET_PAGE_DETAILS
Fetches details about a specific Facebook Page.
Input parameters
Section titled “Input parameters”| Name | Type | Required | Description |
|---|---|---|---|
fields | string | No | Comma-separated list of fields to return for the Page. Common valid fields include: id, name, about, category, description, fan_count, followers_count, website, link, username, is_published, access_token, emails, phone, location, hours, cover, picture, engagement, verification_status, and many more. IMPORTANT: The following fields are NOT valid for direct Page queries and will be automatically filtered out: ‘tasks’ and ‘created_time’. For a complete list of valid Page fields, refer to the Facebook Graph API Page reference. |
page_id | string | Yes | The unique numeric ID of the Facebook Page to get details for. Facebook Page IDs are numeric strings typically 15-16 digits long (e.g., ‘678594635343968’). To find valid page IDs, use FACEBOOK_LIST_MANAGED_PAGES or FACEBOOK_GET_USER_PAGES. |
Output
Section titled “Output”| Name | Type | Required | Description |
|---|---|---|---|
data | string | Yes | Data from the action execution |
error | string | No | Error if any occurred during the execution of the action |
successful | boolean | Yes | Whether or not the action execution was successful or not |
Get Page Insights
Section titled “Get Page Insights”FACEBOOK_GET_PAGE_INSIGHTS
Retrieves analytics and insights for a Facebook Page. Returns metrics like impressions, page views, fan counts, and engagement data. Empty objects ({}) in results indicate missing data, not zero values. High-volume calls risk Graph API rate limits (error codes 4/613).
Input parameters
Section titled “Input parameters”| Name | Type | Required | Description |
|---|---|---|---|
since | string | No | Start of date range as Unix timestamp (e.g., ‘1704067200’), ISO 8601 datetime (e.g., ‘2024-10-01T00:00:00+0000’), or strtotime-compatible string (e.g., ‘yesterday’, ‘-7 days’). Maximum range is 90 days when combined with ‘until’. |
until | string | No | End of date range as Unix timestamp, ISO 8601 datetime, or strtotime string (e.g., ‘now’, ‘-1 day’). Maximum range is 90 days when combined with ‘since’. |
period | string | No | Period for the metrics: day, week, days_28, month, lifetime. Using lifetime with bounded since/until ranges produces misleading or empty results. Standardize all date inputs to UTC. |
metrics | string | No | Comma-separated list of metrics to retrieve. VALID METRICS: page_follows, page_daily_follows_unique, page_daily_unfollows_unique, page_media_view, page_post_engagements, page_video_views, page_total_actions, page_actions_post_reactions_total. DEPRECATED (will be auto-replaced): page_impressions, page_fans, page_engaged_users, page_fan_adds. Not all metric/period combinations are valid; incompatible combinations return empty data. |
page_id | string | Yes | The ID of the Facebook Page Must be a numeric Page ID; page names, URLs, and personal profile IDs are invalid. |
Output
Section titled “Output”| Name | Type | Required | Description |
|---|---|---|---|
data | string | Yes | Data from the action execution |
error | string | No | Error if any occurred during the execution of the action |
successful | boolean | Yes | Whether or not the action execution was successful or not |
Get Page Photos
Section titled “Get Page Photos”FACEBOOK_GET_PAGE_PHOTOS
Retrieves photos from a Facebook Page. CDN-based URLs (including source) are time-limited and expire; download and persist images promptly if long-term access is needed.
Input parameters
Section titled “Input parameters”| Name | Type | Required | Description |
|---|---|---|---|
type | string | No | Filter by photo type: uploaded, tagged |
limit | integer | No | Number of photos to return (max 100) Use paging cursors from the response to iterate through all available photos in large libraries; limit=100 does not guarantee all photos are returned in one call. |
fields | string | No | Comma-separated list of valid Photo fields to return. Valid fields include: id, created_time, updated_time, name, images, height, width, picture, link, icon, from, album, backdated_time, place, page_story_id, target, event, can_delete, can_tag, webp_images. NOTE: ‘reactions’ and ‘comments’ are NOT valid fields - they are edges that must be accessed via separate API calls. |
page_id | string | Yes | The numeric ID of the Facebook Page (e.g., ‘678594635343968’). You can obtain page IDs using the FACEBOOK_LIST_MANAGED_PAGES action. Do NOT pass datetime strings, timestamps, or date values - only valid Facebook page IDs. |
Output
Section titled “Output”| Name | Type | Required | Description |
|---|---|---|---|
data | string | Yes | Data from the action execution |
error | string | No | Error if any occurred during the execution of the action |
successful | boolean | Yes | Whether or not the action execution was successful or not |
Get Page Posts
Section titled “Get Page Posts”FACEBOOK_GET_PAGE_POSTS
Retrieves posts from a Facebook Page. Endpoint choice: Uses /{page_id}/feed instead of /posts or /published_posts because /feed returns all content on page timeline (page’s posts + visitor posts + tagged posts). Pagination: follow paging.cursors.after or paging.next across multiple calls until no next cursor exists. API Version: Uses v23.0 (released May 2025).
Input parameters
Section titled “Input parameters”| Name | Type | Required | Description |
|---|---|---|---|
limit | integer | No | Number of posts to return (max 100) |
since | string | No | Filter posts updated after this time. Accepts: Unix timestamp (e.g., ‘1705320000’), strtotime values (e.g., ‘yesterday’, ‘7 days ago’, ‘last week’), or datetime strings (e.g., ‘2024-01-15’, ‘2024-01-15T12:00:00’). Datetime strings are automatically converted to Unix timestamps. |
until | string | No | Filter posts updated before this time. Accepts: Unix timestamp, strtotime values, or datetime strings. |
fields | string | No | Comma-separated list of fields to return for each post. Supported fields include: id, message, created_time, updated_time, permalink_url, attachments, story, from, status_type, full_picture, shares, reactions, comments, is_hidden, is_published. For summary counts, use ‘.summary(true)’ syntax (e.g., ‘reactions.summary(true)’). Note: ‘type’, ‘link’, ‘source’, ‘picture’, ‘name’, ‘caption’, ‘description’, and ‘icon’ are deprecated since Graph API v3.3. |
page_id | string | Yes | The ID of the Facebook Page. Can be provided as a string or number. Must be a Facebook Page ID, not a personal profile or user ID — use FACEBOOK_GET_USER_PAGES to obtain a valid Page ID. |
removed_deprecated_fields | array | No | Internal field to track deprecated fields that were automatically removed. |
Output
Section titled “Output”| Name | Type | Required | Description |
|---|---|---|---|
data | string | Yes | Data from the action execution |
error | string | No | Error if any occurred during the execution of the action |
successful | boolean | Yes | Whether or not the action execution was successful or not |
Get Page Roles
Section titled “Get Page Roles”FACEBOOK_GET_PAGE_ROLES
Retrieves a list of people and their tasks/roles on a Facebook Page. The connected account must have management access to the target Page; otherwise the response may be empty or incomplete. Returned role types include MANAGE and CREATE_CONTENT — verify these before calling tools like FACEBOOK_UPDATE_PAGE_SETTINGS. Recently changed roles may take time to propagate; retry if role data appears stale after an update.
Input parameters
Section titled “Input parameters”| Name | Type | Required | Description |
|---|---|---|---|
after | string | No | Cursor string for forward pagination. Use the ‘after’ cursor from a previous response’s paging.cursors.after field to retrieve the next page of results. |
limit | integer | No | Maximum number of roles to return per request. |
before | string | No | Cursor string for backward pagination. Use the ‘before’ cursor from a previous response’s paging.cursors.before field to retrieve the previous page of results. |
page_id | string | Yes | The ID of the Facebook Page |
Output
Section titled “Output”| Name | Type | Required | Description |
|---|---|---|---|
data | string | Yes | Data from the action execution |
error | string | No | Error if any occurred during the execution of the action |
successful | boolean | Yes | Whether or not the action execution was successful or not |
Get Page Tagged Posts
Section titled “Get Page Tagged Posts”FACEBOOK_GET_PAGE_TAGGED_POSTS
Retrieves posts where a Facebook Page is tagged or mentioned. Use when monitoring brand mentions or tracking posts that tag your Page but don’t appear on your Page’s own feed.
Input parameters
Section titled “Input parameters”| Name | Type | Required | Description |
|---|---|---|---|
limit | integer | No | Number of posts to return (max 100) |
since | string | No | Filter posts updated after this time. Accepts: Unix timestamp, strtotime values, or datetime strings. |
until | string | No | Filter posts updated before this time. Accepts: Unix timestamp, strtotime values, or datetime strings. |
fields | string | No | Comma-separated list of fields to return for each post |
page_id | string | Yes | The ID of the Facebook Page. Can be provided as a string or number. |
Output
Section titled “Output”| Name | Type | Required | Description |
|---|---|---|---|
data | string | Yes | Data from the action execution |
error | string | No | Error if any occurred during the execution of the action |
successful | boolean | Yes | Whether or not the action execution was successful or not |
Get Page Videos
Section titled “Get Page Videos”FACEBOOK_GET_PAGE_VIDEOS
Retrieves videos from a Facebook Page.
Input parameters
Section titled “Input parameters”| Name | Type | Required | Description |
|---|---|---|---|
type | string | No | Filter by video type: uploaded, tagged |
limit | integer | No | Number of videos to return (max 100) Controls only the first batch; iterate through paging cursors (paging.cursors.after) until no next page is returned to retrieve all videos. |
fields | string | No | Comma-separated list of fields to return for each video The source field returns time-limited URLs; download or process promptly rather than storing for later use. |
page_id | string | Yes | The numeric ID of the Facebook Page. This is a numeric string (e.g., ‘123456789012345’). To obtain a valid page_id, use the ‘Get User Pages’ or ‘List Managed Pages’ action which returns page IDs for pages you have access to manage. |
Output
Section titled “Output”| Name | Type | Required | Description |
|---|---|---|---|
data | string | Yes | Data from the action execution |
error | string | No | Error if any occurred during the execution of the action |
successful | boolean | Yes | Whether or not the action execution was successful or not |
Get Post
Section titled “Get Post”FACEBOOK_GET_POST
Retrieves details of a specific Facebook post.
Input parameters
Section titled “Input parameters”| Name | Type | Required | Description |
|---|---|---|---|
fields | string | No | Comma-separated list of fields to return. Common fields: id, message, created_time, updated_time, permalink_url, from, attachments, shares, story, picture, full_picture, place, privacy, status_type. For engagement metrics with counts, use edge.summary(true) syntax. CORRECT: likes.summary(true), comments.summary(true). WRONG: likes.summary(total_count). Note: Legacy post fields (name, link, description, type) are deprecated; use ‘attachments’ edge instead. |
post_id | string | Yes | The ID of the post to retrieve. Must be in full format: ‘pageId_postId’ where both pageId and postId are numeric (e.g., ‘123456789_987654321’). Page-scoped IDs (alphanumeric strings like ‘1ANtnBaCHX’) are not supported. Use FACEBOOK_GET_PAGE_POSTS to obtain valid full-format post IDs. |
Output
Section titled “Output”| Name | Type | Required | Description |
|---|---|---|---|
data | string | Yes | Data from the action execution |
error | string | No | Error if any occurred during the execution of the action |
successful | boolean | Yes | Whether or not the action execution was successful or not |
Get Post Insights
Section titled “Get Post Insights”FACEBOOK_GET_POST_INSIGHTS
Retrieves analytics and insights for a specific Facebook post. Returns metrics like impressions, clicks, and engagement data. Very new posts may return empty metric values; allow a short delay before querying and treat absent fields as partial data.
Input parameters
Section titled “Input parameters”| Name | Type | Required | Description |
|---|---|---|---|
period | string | No | Period for the metrics (only applicable for some metrics): lifetime Supports since/until parameters in UTC; convert from user timezone to avoid misleading aggregates when comparing posts across time windows. |
metrics | string | No | Comma-separated list of metrics to retrieve. Valid metric: post_media_view (the number of times the post entered a person’s screen). Note: Older metrics like post_impressions, post_impressions_unique, post_clicks, post_engagements, post_engaged_users, post_reactions_by_type_total were deprecated by Facebook as of November 15, 2025 and are no longer supported. Request only needed metrics to reduce payload size and avoid rate limit errors (error codes 4/613) when iterating over many posts. |
post_id | string | Yes | The ID of the post to get insights for |
Output
Section titled “Output”| Name | Type | Required | Description |
|---|---|---|---|
data | string | Yes | Data from the action execution |
error | string | No | Error if any occurred during the execution of the action |
successful | boolean | Yes | Whether or not the action execution was successful or not |
Get Post Reactions
Section titled “Get Post Reactions”FACEBOOK_GET_POST_REACTIONS
Retrieves reactions (like, love, wow, etc.) for a Facebook post. Very recent posts may return empty or partial reactions data; treat missing fields as incomplete coverage, not an error.
Input parameters
Section titled “Input parameters”| Name | Type | Required | Description |
|---|---|---|---|
type | string | No | Filter by reaction type: LIKE, LOVE, WOW, HAHA, SAD, ANGRY, THANKFUL |
limit | integer | No | Number of reactions to return (max 100) |
post_id | string | Yes | The ID of the post to get reactions for |
summary | boolean | No | Include summary with total count per reaction type |
Output
Section titled “Output”| Name | Type | Required | Description |
|---|---|---|---|
data | string | Yes | Data from the action execution |
error | string | No | Error if any occurred during the execution of the action |
successful | boolean | Yes | Whether or not the action execution was successful or not |
Get Scheduled Posts
Section titled “Get Scheduled Posts”FACEBOOK_GET_SCHEDULED_POSTS
Retrieves scheduled and unpublished posts for a Facebook Page. Results are cursor-paginated; follow pagination cursors to retrieve all results beyond the limit. When searching for posts near a specific time, filter to a narrow (~±5 minutes) window. Use this tool to check for existing entries before scheduling new posts to avoid duplicates.
Input parameters
Section titled “Input parameters”| Name | Type | Required | Description |
|---|---|---|---|
limit | integer | No | Number of posts to return (max 100) |
fields | string | No | Comma-separated list of fields to return for each post |
page_id | string | Yes | The ID of the Facebook Page |
Output
Section titled “Output”| Name | Type | Required | Description |
|---|---|---|---|
data | string | Yes | Data from the action execution |
error | string | No | Error if any occurred during the execution of the action |
successful | boolean | Yes | Whether or not the action execution was successful or not |
Get User Pages (Deprecated)
Section titled “Get User Pages (Deprecated)”FACEBOOK_GET_USER_PAGES
DEPRECATED: Use FACEBOOK_LIST_MANAGED_PAGES instead. Retrieves Facebook Pages the user manages (excludes personal profiles, groups, and non-Page entities); an empty data array means no manageable Pages exist. Requires pages_show_list scope; missing scopes yield empty data or OAuthException code 200. Results paginate ~100 items per page — follow paging.cursors.after or next until exhausted.
Input parameters
Section titled “Input parameters”| Name | Type | Required | Description |
|---|---|---|---|
after | string | No | Cursor string for pagination. Use the ‘after’ cursor from a previous response’s paging.cursors.after field to retrieve the next page of results. |
limit | integer | No | Maximum number of pages to return per request. |
fields | string | No | Comma-separated list of fields to return for each page. Supported fields include: id, name, access_token, tasks, category, category_list, picture, link, fan_count, followers_count, is_published, global_brand_page_name, instagram_business_account, verification_status, is_webhooks_subscribed. Always include id and name to avoid extra identity-resolution calls. |
user_id | string | No | The ID of the user whose pages to retrieve. Defaults to ‘me’ for current user. |
composio_execution_message | string | No | Execution message from preprocessing. |
Output
Section titled “Output”| Name | Type | Required | Description |
|---|---|---|---|
data | string | Yes | Data from the action execution |
error | string | No | Error if any occurred during the execution of the action |
successful | boolean | Yes | Whether or not the action execution was successful or not |
Add Reaction
Section titled “Add Reaction”FACEBOOK_LIKE_POST_OR_COMMENT
Adds a LIKE reaction to a Facebook post or comment. Note: Due to API limitations, only LIKE reactions can be added programmatically. This action is user-visible and irreversible — confirm with the user before calling.
Input parameters
Section titled “Input parameters”| Name | Type | Required | Description |
|---|---|---|---|
type | string | No | Reaction type: Currently only LIKE is supported via API. Other reactions (LOVE, WOW, HAHA, SAD, ANGRY, THANKFUL) cannot be added programmatically |
object_id | string | Yes | The ID of the post or comment to react to. Facebook IDs are numeric strings (typically 15-20 digits). Must belong to a Page post or comment, not a personal profile timeline. IMPORTANT: Always pass IDs as strings to preserve precision. Integer values will be converted to strings, but float values (including scientific notation like 5.3e+32) are rejected because they lose precision. |
Output
Section titled “Output”| Name | Type | Required | Description |
|---|---|---|---|
data | string | Yes | Data from the action execution |
error | string | No | Error if any occurred during the execution of the action |
successful | boolean | Yes | Whether or not the action execution was successful or not |
List Managed Pages
Section titled “List Managed Pages”FACEBOOK_LIST_MANAGED_PAGES
Retrieves a list of Facebook Pages that the user manages (not personal profiles), including page details, access tokens, and tasks. Requires pages_show_list or pages_read_engagement OAuth scopes; missing scopes silently return empty results rather than an error. An empty data array means the user manages no Pages. Results are paginated via paging.cursors; follow paging.next until absent to retrieve all Pages when count exceeds limit. Graph API throttling (error codes 4, 17, 613) can occur during pagination — use exponential backoff.
Input parameters
Section titled “Input parameters”| Name | Type | Required | Description |
|---|---|---|---|
after | string | No | Cursor string for forward pagination. Use the ‘after’ cursor from a previous response’s paging.cursors.after field to retrieve the next page of results. |
limit | integer | No | Maximum number of pages to retrieve per request. |
before | string | No | Cursor string for backward pagination. Use the ‘before’ cursor from a previous response’s paging.cursors.before field to retrieve the previous page of results. |
fields | string | No | Comma-separated list of fields to return for each managed page. |
user_id | string | No | The ID of the user whose managed pages to retrieve. Defaults to ‘me’ for current user. |
Output
Section titled “Output”| Name | Type | Required | Description |
|---|---|---|---|
data | string | Yes | Data from the action execution |
error | string | No | Error if any occurred during the execution of the action |
successful | boolean | Yes | Whether or not the action execution was successful or not |
Mark Message Seen
Section titled “Mark Message Seen”FACEBOOK_MARK_MESSAGE_SEEN
Marks a user’s message as seen by the Page, visibly updating the read status in the user’s conversation. Note: This action requires an active messaging session with the user. Facebook’s messaging policy requires that users have messaged the Page within the last 24 hours for sender actions to work.
Input parameters
Section titled “Input parameters”| Name | Type | Required | Description |
|---|---|---|---|
page_id | string | Yes | The ID of the Facebook Page |
recipient_id | string | Yes | The ID of the user whose message to mark as seen |
Output
Section titled “Output”| Name | Type | Required | Description |
|---|---|---|---|
data | string | Yes | Data from the action execution |
error | string | No | Error if any occurred during the execution of the action |
successful | boolean | Yes | Whether or not the action execution was successful or not |
Publish Scheduled Post
Section titled “Publish Scheduled Post”FACEBOOK_PUBLISH_SCHEDULED_POST
Publishes a previously scheduled or unpublished Facebook post immediately. This action takes a scheduled or unpublished post and publishes it immediately by setting is_published to true. The post must have been previously created with published=false or with a scheduled_publish_time. Requirements: - The post must exist and be in an unpublished/scheduled state - The user must have admin access to the page that owns the post - The app must have pages_manage_posts permission
Input parameters
Section titled “Input parameters”| Name | Type | Required | Description |
|---|---|---|---|
page_id | string | No | Optional: The ID of the Facebook Page that owns the post. If not provided, it will be extracted from the post_id (the part before the underscore). |
post_id | string | Yes | The ID of the scheduled/unpublished post to publish. Format is typically ‘pageId_postId’ (e.g., ‘123456789_987654321’). Use ‘Get Scheduled Posts’ action to find scheduled post IDs. |
Output
Section titled “Output”| Name | Type | Required | Description |
|---|---|---|---|
data | string | Yes | Data from the action execution |
error | string | No | Error if any occurred during the execution of the action |
successful | boolean | Yes | Whether or not the action execution was successful or not |
Remove Page Task
Section titled “Remove Page Task”FACEBOOK_REMOVE_PAGE_TASK
Removes a user’s tasks/access from a specific Facebook Page. Caller must have admin-level rights on the Page. Operates on one page_id at a time; repeat for each page if removing from multiple pages. Partial access may remain if only some tasks are revoked.
Input parameters
Section titled “Input parameters”| Name | Type | Required | Description |
|---|---|---|---|
user | string | Yes | The ID or username of the user to remove Verify this matches the intended collaborator before calling; a mismatch revokes access for the wrong account. |
page_id | string | Yes | The ID of the Facebook Page |
Output
Section titled “Output”| Name | Type | Required | Description |
|---|---|---|---|
data | string | Yes | Data from the action execution |
error | string | No | Error if any occurred during the execution of the action |
successful | boolean | Yes | Whether or not the action execution was successful or not |
Reschedule Post
Section titled “Reschedule Post”FACEBOOK_RESCHEDULE_POST
Changes the scheduled publish time of an unpublished Facebook post. This action updates the scheduled_publish_time of a previously scheduled post. The post must have been created with published=false and a scheduled_publish_time.
Input parameters
Section titled “Input parameters”| Name | Type | Required | Description |
|---|---|---|---|
post_id | string | Yes | The ID of the scheduled post to reschedule. Format is typically ‘pageId_postId’ (e.g., ‘123456789_987654321’). |
scheduled_publish_time | integer | Yes | New Unix timestamp for when to publish the post. Must be at least 10 minutes in the future and no more than 6 months ahead. |
Output
Section titled “Output”| Name | Type | Required | Description |
|---|---|---|---|
data | string | Yes | Data from the action execution |
error | string | No | Error if any occurred during the execution of the action |
successful | boolean | Yes | Whether or not the action execution was successful or not |
Search Pages
Section titled “Search Pages”FACEBOOK_SEARCH_PAGES
Searches for Facebook Pages based on a query string. Returns pages matching the search criteria with requested fields. DEPRECATION WARNING: The /pages/search endpoint was deprecated by Facebook in 2019 and is now ONLY available to Workplace by Meta apps. Standard Facebook apps will receive Error #10 (permission error) regardless of which permissions or features have been granted. For Workplace apps only - requires one of: - ‘pages_read_engagement’ permission - ‘Page Public Content Access’ feature - ‘Page Public Metadata Access’ feature Standard Facebook apps should use alternative methods to discover pages, such as: - Direct page ID lookup via /{page-id} endpoint - User’s managed pages via /me/accounts endpoint Results include only Facebook Pages; personal profiles, groups, and other entity types are excluded.
Input parameters
Section titled “Input parameters”| Name | Type | Required | Description |
|---|---|---|---|
limit | integer | No | Maximum number of results to return (max 100) A specific target page may not appear in a single response; refine the query string if the desired page is missing. |
query | string | Yes | Search query for finding pages (e.g., business name, topic, etc.) |
fields | string | No | Comma-separated list of fields to retrieve for each page Returned field data (e.g., fan_count, location) can be sparse or outdated; avoid relying on a single field for selection logic. |
Output
Section titled “Output”| Name | Type | Required | Description |
|---|---|---|---|
data | string | Yes | Data from the action execution |
error | string | No | Error if any occurred during the execution of the action |
successful | boolean | Yes | Whether or not the action execution was successful or not |
Send Media Message
Section titled “Send Media Message”FACEBOOK_SEND_MEDIA_MESSAGE
Sends a media message (image, video, audio, or file) from the Page to a user.
Input parameters
Section titled “Input parameters”| Name | Type | Required | Description |
|---|---|---|---|
tag | string | No | Message tag required when messaging_type is MESSAGE_TAG. Valid tags include: CONFIRMED_EVENT_UPDATE, POST_PURCHASE_UPDATE, ACCOUNT_UPDATE, HUMAN_AGENT |
page_id | string | Yes | The ID of the Facebook Page sending the message |
media_url | string | Yes | URL of the media to send |
media_type | string | Yes | Type of media: image, video, audio, or file |
is_reusable | boolean | No | Whether the attachment is reusable |
recipient_id | string | Yes | The ID of the message recipient (user ID or PSID) |
messaging_type | string | No | The messaging type - RESPONSE, UPDATE, or MESSAGE_TAG |
Output
Section titled “Output”| Name | Type | Required | Description |
|---|---|---|---|
data | string | Yes | Data from the action execution |
error | string | No | Error if any occurred during the execution of the action |
successful | boolean | Yes | Whether or not the action execution was successful or not |
Send Message
Section titled “Send Message”FACEBOOK_SEND_MESSAGE
Sends a text message from a Facebook Page (not personal profiles) to a user via Messenger. Requires explicit user confirmation before calling, as this action delivers a message to a real end user.
Input parameters
Section titled “Input parameters”| Name | Type | Required | Description |
|---|---|---|---|
tag | string | No | Required when messaging_type is MESSAGE_TAG. Valid tags: HUMAN_AGENT (within 7 days of last user message for human agent responses), CONFIRMED_EVENT_UPDATE (for registered event updates), POST_PURCHASE_UPDATE (for purchase-related updates), ACCOUNT_UPDATE (for non-recurring account changes). |
page_id | string | Yes | The ID of the Facebook Page sending the message Must be a numeric page ID, not a username or alias. |
message_text | string | Yes | The text content of the message to send |
recipient_id | string | Yes | The ID of the message recipient (user ID or PSID) Must be a numeric PSID, not a username or display name. |
messaging_type | string | No | The messaging type - RESPONSE, UPDATE, or MESSAGE_TAG. Use RESPONSE within 24 hours of user’s last message. Use MESSAGE_TAG with a tag parameter to send outside the 24-hour window. |
Output
Section titled “Output”| Name | Type | Required | Description |
|---|---|---|---|
data | string | Yes | Data from the action execution |
error | string | No | Error if any occurred during the execution of the action |
successful | boolean | Yes | Whether or not the action execution was successful or not |
Toggle Typing Indicator
Section titled “Toggle Typing Indicator”FACEBOOK_TOGGLE_TYPING_INDICATOR
Shows or hides the typing indicator for a user in Messenger.
Input parameters
Section titled “Input parameters”| Name | Type | Required | Description |
|---|---|---|---|
page_id | string | Yes | The ID of the Facebook Page |
typing_on | boolean | Yes | True to show typing indicator, False to hide it |
recipient_id | string | Yes | The Page-Scoped ID (PSID) of the user to show/hide typing indicator for |
Output
Section titled “Output”| Name | Type | Required | Description |
|---|---|---|---|
data | string | Yes | Data from the action execution |
error | string | No | Error if any occurred during the execution of the action |
successful | boolean | Yes | Whether or not the action execution was successful or not |
Unlike Post or Comment
Section titled “Unlike Post or Comment”FACEBOOK_UNLIKE_POST_OR_COMMENT
Removes a like from a Facebook post or comment.
Input parameters
Section titled “Input parameters”| Name | Type | Required | Description |
|---|---|---|---|
object_id | string | Yes | The ID of the post or comment to unlike. Facebook IDs are numeric strings (typically 15-20 digits). IMPORTANT: Always pass IDs as strings to preserve precision. Integer values will be converted to strings, but float values (including scientific notation like 5.3e+32) are rejected because they lose precision. |
Output
Section titled “Output”| Name | Type | Required | Description |
|---|---|---|---|
data | string | Yes | Data from the action execution |
error | string | No | Error if any occurred during the execution of the action |
successful | boolean | Yes | Whether or not the action execution was successful or not |
Update Comment
Section titled “Update Comment”FACEBOOK_UPDATE_COMMENT
Updates an existing Facebook comment. IMPORTANT: This action requires a Page Access Token. The comment must belong to a post on a Page that you manage. Use the page_id parameter to ensure the correct page token is used, especially if you manage multiple pages.
Input parameters
Section titled “Input parameters”| Name | Type | Required | Description |
|---|---|---|---|
message | string | Yes | The new text content of the comment |
page_id | string | No | The ID of the Facebook Page that owns the comment. Required to ensure the correct page access token is used. If not provided, the action will attempt to use the first available page’s token, which may fail if you manage multiple pages. |
is_hidden | boolean | No | Whether to hide or unhide the comment |
comment_id | string | Yes | The ID of the comment to update. Format is typically ‘objectId_commentId’ (e.g., ‘122157027176937815_1371138271476143’). |
Output
Section titled “Output”| Name | Type | Required | Description |
|---|---|---|---|
data | string | Yes | Data from the action execution |
error | string | No | Error if any occurred during the execution of the action |
successful | boolean | Yes | Whether or not the action execution was successful or not |
Update Page Settings
Section titled “Update Page Settings”FACEBOOK_UPDATE_PAGE_SETTINGS
Updates settings for a specific Facebook Page. Requires the authenticated user to have MANAGE and CREATE_CONTENT tasks for the target page; verify roles via FACEBOOK_GET_PAGE_ROLES. Not all fields (about, description, general_info, etc.) are available for every Page category.
Input parameters
Section titled “Input parameters”| Name | Type | Required | Description |
|---|---|---|---|
about | string | No | Updated about section for the page |
phone | string | No | Updated phone number |
emails | array | No | Updated email addresses |
page_id | string | Yes | The ID of the Facebook Page to update |
website | string | No | Updated website URL |
description | string | No | Updated description for the page |
general_info | string | No | Updated general information |
Output
Section titled “Output”| Name | Type | Required | Description |
|---|---|---|---|
data | string | Yes | Data from the action execution |
error | string | No | Error if any occurred during the execution of the action |
successful | boolean | Yes | Whether or not the action execution was successful or not |
Update Post
Section titled “Update Post”FACEBOOK_UPDATE_POST
Updates an existing Facebook Page post.
Input parameters
Section titled “Input parameters”| Name | Type | Required | Description |
|---|---|---|---|
message | string | No | Updated text content of the post |
post_id | string | Yes | The ID of the post to update |
og_phrase | string | No | Open Graph phrase |
og_icon_id | string | No | Open Graph icon ID |
og_object_id | string | No | Open Graph object ID |
og_action_type_id | string | No | Open Graph action type ID |
og_suggestion_mechanism | string | No | Open Graph suggestion mechanism |
Output
Section titled “Output”| Name | Type | Required | Description |
|---|---|---|---|
data | string | Yes | Data from the action execution |
error | string | No | Error if any occurred during the execution of the action |
successful | boolean | Yes | Whether or not the action execution was successful or not |
Upload Photo (Deprecated)
Section titled “Upload Photo (Deprecated)”FACEBOOK_UPLOAD_PHOTO
DEPRECATED: Use FACEBOOK_CREATE_PHOTO_POST instead. Uploads a photo file directly to a Facebook Page. Supports local file upload up to 10MB.
Input parameters
Section titled “Input parameters”| Name | Type | Required | Description |
|---|---|---|---|
url | string | No | Public URL of the photo (must be accessible by Facebook servers). Alternative to ‘photo’. Use this for images hosted on external servers. Must be a direct HTTPS endpoint returning an image MIME type; redirects, HTML pages, and non-HTTPS URLs fail validation. |
tags | array | No | List of user tags with format [{'tag_uid': 'USER_ID', 'x': 50, 'y': 50}] |
photo | object | No | Photo file to upload (max 10MB). Alternative to ‘url’. If a URL string is mistakenly passed here, it will be auto-converted to use the ‘url’ parameter. |
caption | string | No | Caption for the photo |
page_id | string | Yes | The ID of the Facebook Page. Can be provided as a string or number. Must be a Page ID; personal profile/user timeline IDs are not valid. |
published | boolean | No | Whether to publish the photo immediately |
targeting | object | No | Audience targeting specifications |
scheduled_publish_time | integer | No | Unix timestamp to schedule the post Requires published=false; value must be a future UTC epoch in seconds. Using published=true with this field causes validation errors. |
Output
Section titled “Output”| Name | Type | Required | Description |
|---|---|---|---|
data | string | Yes | Data from the action execution |
error | string | No | Error if any occurred during the execution of the action |
successful | boolean | Yes | Whether or not the action execution was successful or not |
Upload Photos Batch
Section titled “Upload Photos Batch”FACEBOOK_UPLOAD_PHOTOS_BATCH
Uploads multiple photo files in batch to a Facebook Page or Album. Uses Facebook’s batch API for efficient multi-photo upload. Maximum 50 photos per batch.
Input parameters
Section titled “Input parameters”| Name | Type | Required | Description |
|---|---|---|---|
photos | array | No | List of photo files to upload (max 50 photos) |
page_id | string | Yes | The ID of the Facebook Page |
album_id | string | No | ID of album to add photos to. If not provided, photos will be uploaded to timeline |
published | boolean | No | Whether to publish the photos immediately To schedule, set to false and include scheduled_publish_time as a Unix UTC epoch timestamp; mismatched combinations trigger 400 errors. |
photo_urls | array | No | List of photo URLs to upload (alternative to ‘photos’) Must be direct, publicly accessible HTTPS URLs — no redirects, private URLs, or HTTP. |
Output
Section titled “Output”| Name | Type | Required | Description |
|---|---|---|---|
data | string | Yes | Data from the action execution |
error | string | No | Error if any occurred during the execution of the action |
successful | boolean | Yes | Whether or not the action execution was successful or not |
Upload Video (Deprecated)
Section titled “Upload Video (Deprecated)”FACEBOOK_UPLOAD_VIDEO
DEPRECATED: Use CreateVideoPost instead. Uploads a video file directly to a Facebook Page. Supports local file upload. For large videos (>100MB), uses resumable upload. After upload completes, the video enters a processing/pending state; do not reference or schedule it until processing finishes.
Input parameters
Section titled “Input parameters”| Name | Type | Required | Description |
|---|---|---|---|
title | string | No | Title of the video |
video | object | No | Video file to upload (max 10GB, recommended under 1GB). Either ‘video’ or ‘file_url’ must be provided. Use MP4 with H.264 video and AAC audio to avoid upload failures. |
page_id | string | Yes | The ID of the Facebook Page |
file_url | string | No | URL of a publicly accessible video file to upload. Either ‘file_url’ or ‘video’ must be provided. This is an alternative to uploading a local file. |
published | boolean | No | Whether to publish immediately |
targeting | object | No | Audience targeting specifications |
description | string | No | Description of the video |
content_tags | array | No | List of content tags |
custom_labels | array | No | Custom labels for the video |
scheduled_publish_time | integer | No | Unix timestamp to schedule the video post Requires published=false; combining with published=true triggers a 400 validation error. |
Output
Section titled “Output”| Name | Type | Required | Description |
|---|---|---|---|
data | string | Yes | Data from the action execution |
error | string | No | Error if any occurred during the execution of the action |
successful | boolean | Yes | Whether or not the action execution was successful or not |