Claude Facebook Automation: How to Schedule Posts with Claude Cowork

Claude Facebook automation is useful when the content already exists and the repetitive part is choosing a file, writing the caption, selecting the account, and scheduling the post.

The first workflow in this guide uses a finished Terrific Tools demo video. Claude finds it in a named Genviral folder and schedules it for the OnlineDopamine Facebook account one week ahead.

The second workflow moves the tested process into Claude Cowork. That version cycles through 31 Pantry AI videos and schedules two posts per day for Facebook, with Instagram as an optional second destination.

Claude handles the instructions and decisions. Genviral's MCP server handles the media library, connected accounts, scheduling, and Facebook publishing through the permissions you approve.

What this Claude Facebook automation does

You give Claude three exact identifiers: the Genviral workspace, the media folder, and the destination Facebook account. You then specify the video, caption objective, publish date, and time zone.

In the Terrific Tools example, the selected video shows the desktop app converting medical images into PNG or JPEG files. Claude uses that context to write the post instead of guessing what the product does.

The post is scheduled one week ahead at 5 PM in New York. It then appears in the Genviral calendar, where the media, copy, and scheduling details can still be edited before publication.

That review step caught a real problem in the walkthrough: the Facebook copy was too long and needed to be shortened. Scheduling first gave us time to fix it.

How this differs from the Instagram workflow

The Claude Instagram automation guide starts with a recipe and asks Claude to generate an image that follows a visual reference.

Because this Facebook workflow begins with finished videos, the work shifts to finding the correct file, writing platform-appropriate copy, choosing the account, and reading the converted time correctly.

Facebook also adds a useful cross-posting case. The Pantry AI Cowork task schedules the same videos for Facebook and Instagram, while keeping the destination accounts explicit.

What you need

Prepare these six things before asking Claude to post:

1. A Claude account that can add a custom connector
2. A paid Claude plan for Cowork projects and scheduled tasks
3. A Genviral account
4. A Facebook account connected in Genviral
5. A named media folder containing finished videos
6. Several real Facebook captions and hashtag sets

Post manually for the first week if the page does not have an established format yet. You need real examples before Claude can reproduce your caption style without falling back to generic AI copy.

Step 1: Add Genviral as a Claude connector

Open Claude, go to Customize, and choose Connectors. Add a custom connector with this remote MCP endpoint:

https://mcp.genviral.io/mcp

Name it Genviral, continue through the setup, and approve the OAuth connection.

Anthropic's connector documentation explains how custom remote MCP connectors work in Claude and Cowork.

Only connect servers you trust and review what each permission allows. This connector can expose tools that read media or schedule real posts on your behalf.

Step 2: Enable the permissions you need

Open the Genviral connector settings under Manage Connectors and review the available tools.

For this workflow, Claude needs permission to view folders and media, inspect connected accounts, and create scheduled posts. Enable Upload Media if files may arrive from your device or another connected source.

Upload Media is disabled by default. That does not matter when every video is already in Genviral, but it will block a workflow that needs to move a file from Drive, Dropbox, or your computer.

You do not need to approve every generation tool when the job only schedules finished videos. Give Claude the access required for this task and understand the actions before enabling them.

Step 3: Connect and confirm the Facebook account

Open Social Posts, choose Manage Accounts, and connect Facebook. Complete the authorization flow for the account you want Claude to use.

If you have multiple workspaces, switch to the correct workspace before connecting the account. Then ask Claude to list the Facebook destinations it can see there.

Confirm the workspace and destination name before creating the test. This prevents a useful post for one project from appearing on an unrelated Facebook presence.

Step 4: Put finished videos in a named folder

Upload the finished videos into one folder instead of asking Claude to search the entire media library. The first video uses a folder named terrific.tools and a file described as the medical image video.

For a recurring workflow, use ordered filenames that expose the sequence:

Pantry AI Vids/
├── FB-01-kimbap.mp4
├── FB-02-pesto-pasta.mp4
├── FB-03-roast-chicken.mp4
└── FB-04-tomato-pasta.mp4

In the Cowork walkthrough, Claude found the workspace and folder but initially missed the videos. A screenshot showing the filenames and a direct instruction to search for the prefix fixed the discovery problem.

Claude relied on filenames and metadata in this setup. Name the file after what it contains instead of using camera exports such as IMG_4827.mp4.

Step 5: Schedule one Facebook test post

Your first prompt should describe one scheduled post, not an unattended recurring task. Include the workspace, folder, filename, destination, content objective, date, and IANA time zone.

You can adapt this prompt:

Use the Genviral connector in my personal workspace.
 
Schedule a Facebook post for the OnlineDopamine account using the medical
image video in the terrific.tools folder.
 
The video shows the Terrific Tools desktop app converting medical images
into regular PNG and JPEG files. Write a concise Facebook caption that
explains that use case without overstating it.
 
Do not publish immediately. Schedule it for one week from today at 5:00 PM
America/New_York, then show me the selected account, video, caption, and time.

The content objective gives Claude enough context to write useful copy. The explicit instruction not to publish gives you time to correct whatever it gets wrong.

Step 6: Review the Facebook-specific failure points

Open the scheduled post in Genviral and inspect the result rather than treating task completion as approval.

Check:

• the Facebook destination
• the selected video and preview
• the caption and hashtags
• the post length
• the scheduled date
• the source and displayed time zones

The walkthrough exposed a caption-length problem. Use the Facebook Character Counter when a generated caption is too long, then shorten the copy before the post goes live.

It also exposed a time-zone display detail. A post requested for 5 PM New York appeared at 5 AM in Bali because the calendar displayed the viewer's local time.

Use America/New_York in the instruction and confirm the converted calendar time. A correct conversion can look wrong when you forget which time zone the interface is showing.

If you need help locating queued Facebook content later, see where to find scheduled Facebook posts.

Step 7: Move the tested workflow into Claude Cowork

Once Claude can schedule one correct post, move those instructions into a Cowork project. Keep the workspace, folder, destination accounts, caption examples, and inventory rules together.

The Pantry AI example schedules two posts per day, one in the morning and one in the evening in New York time. It sends the videos to Facebook and Instagram together.

That cadence is the workflow shown in the video, not a universal Facebook recommendation. Start with the frequency you have already tested manually and can review reliably.

Step 8: Teach Cowork your real caption pattern

Paste several captions and hashtag sets you have already published. Explain what should remain fixed and what Cowork may vary for each video.

The Pantry AI examples use lowercase copy and a recognizable caption structure. Giving Claude those examples works better than asking for something friendly, human, or engaging.

Your instructions should cover:

• caption length and capitalization
• opening and call-to-action style
• hashtags to use or avoid
• whether Facebook and Instagram need different copy
• claims Claude must not invent

Real examples replace vague taste instructions with a pattern Claude can follow.

Step 9: Define the media loop and cross-posting rules

Tell Cowork what to do after it reaches the final file. In the Pantry AI workflow, video 31 is followed by video 1 so the account does not stop posting when no new video has been added.

Tell the task to rescan the folder before each run, include newly added filenames in the sequence, and restart only after the current inventory is exhausted.

The loop worked for this Pantry AI Facebook and Instagram setup. Treat that as one tested result, not proof that every page can recycle the same videos indefinitely without performance loss.

Cross-posting also needs explicit destinations. Tell Cowork whether each file should go to Facebook only or to both Facebook and Instagram, then confirm both connected accounts before scheduling.

Step 10: Create the recurring scheduled task

Cowork scheduled tasks can run on a recurring cadence and use the connectors already configured for the project.

Anthropic documents the current setup in its scheduled tasks guide.

Schedule each post half a day or a day ahead during the first runs. The review window lets you inspect the selected file, copy, and destinations before the publish time.

Require a notification after every run. Include the filename, destination accounts, scheduled time, status returned by Genviral, and the next file in the sequence.

Step 11: Separate notifications from verified delivery

The Cowork walkthrough shows a useful limitation. The scheduled task kept raising a warning because it could not confirm the final Facebook publication from the data returned to it.

The posts were still appearing in the example, but the task could not independently verify that result. So your status language needs to separate three things:

1. Genviral accepted or scheduled the post
2. Facebook published the post
3. Claude independently verified the published result

Do not call step one a verified publication. Use the notification as a prompt to check the Genviral calendar or Facebook when final verification is unavailable.

This distinction also makes failures easier to diagnose because you know whether the problem happened during scheduling, Facebook delivery, or result verification.

When Facebook needs to be reconnected

Connected Facebook accounts may require reauthentication. In the walkthrough, the recurring task's warning provided a reason to inspect the account and confirm whether it still had access.

Your failure notification should identify the destination, preserve the media filename, and stop short of claiming success. Reconnect the account, then retry only the failed post instead of restarting the entire inventory.

The Hermes Agent Facebook guide covers the same reauthentication and failure-reporting problem from a durable agent-log perspective.

Can Claude post directly to Facebook?

Claude needs a connected tool that can perform the publishing action. In this workflow, Genviral provides that tool through MCP and manages the Facebook authorization.

Claude does not need your Facebook password. You connect the account in Genviral and approve the MCP permissions Claude may use.

Can Claude post the same video to Facebook and Instagram?

Yes. The Cowork example schedules the Pantry AI videos for both connected destinations. Name both accounts explicitly and review the platform-specific copy before publishing.

If the Instagram post needs a generated image or tighter visual references, use the separate Claude Instagram workflow.

Can Claude understand the videos in my folder?

In this workflow, Claude relied on folder names, filenames, metadata, and a screenshot of the inventory. Do not assume it has watched every video just because it can list the files.

Use descriptive filenames and include a one-sentence content description when the caption depends on details that are not visible in the metadata.

Can the Cowork task run while my computer is off?

Connector-based tasks and files saved to your Claude account can run while your computer is asleep.

If the task uses local files or desktop apps, keep the Claude Desktop app open and the computer available. Store recurring media where the scheduled task can reach it reliably.

Getting started

Use this order for the first Facebook workflow:

1. Add the Genviral MCP connector to Claude
2. Approve the folder, media, account, and scheduling permissions you need
3. Connect and confirm the Facebook destination
4. Upload finished videos into a named folder
5. Rename the files in a clear order
6. Schedule one test post in an explicit time zone
7. Review the video, caption length, account, and converted time
8. Move the working instructions into a Cowork project
9. Add real caption examples and end-of-folder rules
10. Schedule the recurring task ahead of publish time
11. Require notifications without confusing scheduling with verified delivery

If you only need a calendar and manual approval flow, Genviral's Facebook Scheduler is the simpler starting point.

Add Claude when you need media selection, caption reasoning, cross-posting rules, and recurring instructions.

Related guides

• Claude YouTube Automation: Schedule Shorts with Claude Cowork
• How to Connect Claude to Instagram and Automate Posting
• How to Automate Facebook Posting with Hermes Agent
• How to Automate Facebook Posting with OpenClaw
• Where to Find Scheduled Posts on Facebook
• How to Find Drafts on Facebook
• Best Social Media APIs for Posting and Automation