How to schedule Facebook Page posts with the Graph API
Facebook Pages have scheduling built into the Graph API: create the post with published set to false and scheduled_publish_time set to when it should go live, and Meta holds it and publishes it then. Meta's Pages guide sets the time between 10 minutes and 30 days after the request, and GET /{page-id}/scheduled_posts lists what is waiting.
easyCoexistence schedules Facebook Page posts in its own queue: ask Claude, ChatGPT or your own code for a date, a time and a timezone, and publish_facebook_post holds the text, link, photo or video from 1 minute to 90 days ahead and publishes it then, with list, update, cancel and retry tools and an email if it fails.
The window Meta's Pages guide sets for scheduled_publish_time, counted from the time of the API request.
Ways to give scheduled_publish_time: a UNIX timestamp in seconds, an ISO 8601 string, or a strtotime() string.
Post field that says whether a scheduled Page post has been published yet.
Furthest ahead Meta's videos reference allows scheduled_publish_time for a video post.
The Page edge that returns the Page's scheduled posts, read with a Page access token.
How far ahead easyCoexistence's queue takes a Facebook post through scheduled_at, against the 30 days of Meta's own scheduling.
How does Meta's own scheduling work?
The post is created at once, unpublished, and Meta holds it until the time set. On the feed edge that means published set to false and scheduled_publish_time set to the moment it should go live, and the photos and videos edges take the same pair. Until then the post reads back with is_published false and its scheduled_publish_time, and the Page's scheduled_posts edge lists it.
How far ahead can a post be scheduled?
With Meta's own scheduling, between 10 minutes and 30 days from the time of the API request, by Meta's Pages guide; its reference pages state other ceilings, 75 days on the feed edge and 6 months for a video. Through easyCoexistence the window runs from 1 minute to 90 days for text, links, photos and videos alike, because the post waits in easyCoexistence's queue rather than at Meta, and a time outside it is refused before anything is queued.
How do you schedule a post through MCP?
Give publish_facebook_post a scheduled_at in ISO 8601 with a timezone, next to the post itself. From Claude or ChatGPT, saying the date, the time and the timezone is enough: the assistant writes scheduled_at, easyCoexistence checks the post and queues it, and the result carries scheduled: true and the queued post with its ID, which the other queue tools take as post_id. A photo post for 9 a.m., three hours behind UTC:
{
"account_id": "<ACCOUNT_ID>",
"message": "Doors open at 9 on Saturday.",
"image_url": "https://example.com/flyer.jpg",
"scheduled_at": "2026-11-14T09:00:00-03:00"
}What happens to the photo or video before the post goes out?
easyCoexistence copies it into its own storage when the post is scheduled, so the original link only has to work at that moment. A web page instead of a file, a missing file, the wrong type, or an image over 30 MB or a video over 1 GB is refused then, not on the day of the post. Facebook's own limit for a photo is lower, 10 MB, and Meta applies it when the post goes out, so keep a Page photo under 10 MB. The copy is kept until a day after the post goes out.
What happens at the scheduled time?
easyCoexistence publishes the post to the Page through the feed, photos or videos edge, as an ordinary post, so neither your AI nor your own code has to be running at that hour. If Meta asks it to slow down, the post is tried again after 5 minutes, 30 minutes and 2 hours; any other failure marks it failed and emails the Page's owner, with at most one email per Page in any 3 hours.
How do you check or change a scheduled post?
With the queue's own tools, from Claude, ChatGPT or your own code. list_scheduled_posts returns the posts waiting, soonest first, or one post by post_id; update_scheduled_post moves a post or changes its text while it is still scheduled; cancel_scheduled_post stops it from going out; retry_scheduled_post publishes a failed post again, and asks for confirm when the post may have reached Facebook anyway, so it is not published twice by mistake. To change the photo or video, cancel the post and schedule it anew.
Where do scheduled posts show in the dashboard?
On the Posts screen. Needs attention holds posts that failed in the last 14 days, with Retry, Reconnect and Dismiss; Coming up lists the scheduled posts in time order, with Cancel; Published shows what went out, each with a link to open it on Facebook. The screen is for seeing and controlling posts, which come from your AI or the API.
How does Meta list the posts it holds?
GET /{page-id}/scheduled_posts, read with a Page access token, lists the posts waiting in Meta's own scheduling, and is_published tells a scheduled post from a published one, since reads of /{page-id}/feed return both. Posts queued through easyCoexistence are not there: Meta receives them only at the time set, so list_scheduled_posts is where they show.
How does a platform schedule through the Partner API?
POST /channels/:id/posts with the text, the media or a link and publish_at queues a post for a customer's Page, and POST /media uploads a file first when it is not at a public URL. GET /posts lists the posts, PATCH and DELETE /posts/:id change or cancel one, POST /posts/:id/retry sends a failed one again, and post.published and post.failed events report each outcome.
Common mistakes
- Leaving the offset off scheduled_at. easyCoexistence refuses a time without one, such as 2026-11-16T10:00:00 alone; add -03:00 or Z so the hour cannot be read in another zone.
- Setting scheduled_publish_time under 10 minutes ahead in a direct Graph call. Meta's window opens 10 minutes after the request, while easyCoexistence's queue starts at 1 minute.
- Trusting relative strtotime strings such as +2 weeks without a check. Meta suggests reading scheduled_publish_time back after writing it, to confirm the date is the intended one.
- Changing a scheduled post's photo with update_scheduled_post. It moves the post and changes its text only; cancel the post and schedule it again with the new file.
US$ 9 to US$ 0.75 per connection per month, falling as you add connections, with the first 3 days free.
easyCoexistence is a multichannel API and MCP server that connects AI agents such as Claude and ChatGPT to WhatsApp, Instagram, TikTok, Facebook and more. On WhatsApp it uses Coexistence: the business keeps using its number in the WhatsApp Business app while the AI works through Meta's official API.
Frequently asked questions
What format does scheduled_publish_time take?
A UNIX timestamp in seconds, an ISO 8601 string or a strtotime() string.
Which timezone does scheduled_at use?
The one written in it: scheduled_at is ISO 8601 with an offset such as -03:00 or Z, and easyCoexistence refuses a time without one, such as 2026-11-16T10:00:00 alone.
Can photos and videos be scheduled too?
Yes. Meta's photos and videos edges take published set to false with scheduled_publish_time, and publish_facebook_post queues a photo or a video the same way as text.
Can a scheduled Facebook photo be larger than 10 MB?
Not on a Page. easyCoexistence's queue accepts images up to 30 MB when the post is scheduled, but Facebook's own photo limit is 10 MB, which Meta applies when the post goes out.
Keep reading
Connect your first channel in two minutes.
No platform reviews to wait for. Connect WhatsApp, Instagram, TikTok or another channel, then ask your AI to post, reply or report, and watch it work.
- 3 days free
- Cancel any time
- Official APIs only
- Monitored 24/7
Verified on