< articles

Facebook Groups API is gone: how AI agents can still post to your groups

If you have tried to get an agent to post to a Facebook group recently, you have probably run into a wall like this one:

Unsupported post request. Object with ID '...' does not exist, cannot be loaded due to missing permissions, or does not support this operation.

That exact error keeps showing up in n8n threads and on Meta's own developer forum. Your code is not the problem, and nor is your token. What has changed is that the API route to a group no longer exists. Below we cover what happened, what still works, and how an agent (Claude Code, Cursor, OpenClaw, Hermes, Grok Bot, or an n8n workflow) can still get a post into a group you are already a member of.

What Meta actually removed

On 23 January 2024 Meta shipped Graph API v19.0. Its release post was blunt: "The Facebook Groups API is deprecated in v19 and in 90 days will be removed from all versions." That covered both Groups API permissions, publish_to_groups and groups_access_member_info, along with the "Groups API" reviewable feature.

The v19.0 changelog added one more change that people tend to overlook: Meta also "deprecated the ability for group admins to install apps on the group, even if they have an admin or developer role on the app." The removal date for every API version was 22 April 2024.

So being the group admin does not help, and neither does passing app review. No permission exists for an app to request, and no group-level app install is left to fall back on. Meta's blog mentions just one surviving use case, a Page messaging feature, which now runs through a Page Access Token instead of the Groups API. It does not let you publish to a group.

That is why the older n8n and Make tutorials, and many "post to Facebook group" scripts, now fail with the error above.

What still works through the official API

Facebook Pages. Meta's Pages API still lets an app publish to a Page. You need a Page access token and permissions such as pages_manage_posts and pages_read_engagement, as the Pages API posts docs describe. If your audience can live on a Page instead of a group, this is the clean, fully supported route, and any agent framework with an HTTP tool can call it.

The catch is that a Page is not a group. A group is where the conversation happens: a local business owners' circle, a meetup community, a niche hobby group. You cannot get there by posting to your Page.

The options for groups, honestly compared

1. The agent drafts, and you paste. Ask your agent for the post, review it, and paste it into the group yourself. It takes no tooling and it is always within the rules. It is also where most people start, and it is fine if you post once a month. It gets old quickly if groups are a real channel for you.

2. A browser in the cloud or a sandbox. Some agents come with their own browser, running on a remote machine. To post to a group from there, you would sign in to your personal Facebook account inside that browser and leave a session on it. That means a login from a device and network you do not normally use, and a live session on a machine you do not control. Weigh that before you do it. Meta's Community Standards include a spam policy, and your personal account carries your name.

3. Your own browser as the posting layer. This is the route we built Claw Post for. Your agent never gets a Facebook password or a Graph API token. Instead, it calls our hosted MCP server. Our Chrome extension, paired with your account and running in your own desktop Chrome, then publishes the post there, using the Facebook session you already have. The post goes out as you, from the browser you normally use.

How it works with Claw Post

The setup is the same whichever agent you use:

  1. Create a Claw Post account at clawpost.net.
  2. Add the Claw Post extension to your desktop Chrome and pair it from the Dashboard.
  3. Add our MCP server to your agent as a remote server: https://mcp.clawpost.net/mcp. Sign in when the OAuth prompt appears.
  4. Ask the agent to run get_account_status to confirm the extension is paired.

After that, a group post is just a prompt:

Draft a short post for the Facebook group at https://www.facebook.com/groups/your-group announcing our meetup on Thursday. Show me the text first. After I approve it, post it with Claw Post and give me the link.

Behind the scenes, the agent calls create_post with the group URL (using platformPayload.groupUrl or platformPayload.groupId), and your Chrome publishes the post in that group. The agent can then call get_post_status to fetch the live post URL.

Keep a few things in mind:

  • Groups you belong to or want to join. On your request, your Chrome can join a Facebook group and then post there. We do not read or monitor groups.
  • The group's rules still apply. If a group has admins review new posts, yours goes through that review, the same as if you had typed it yourself.
  • Chrome has to be open. Posting runs in your desktop Chrome with the extension paired, so keep it open when your agent posts.
  • You stay in the loop. Tell your agent to show you each post before it publishes. Many agents let you require approval for write actions, so use that.

"Can my agent watch a group for new posts?"

This question comes up almost as often as posting. With the Groups API gone, no official read route is left either. In a recent n8n community thread about monitoring groups, members said there is no stable API path for groups anymore, and suggested a workaround that stays within the rules: turn on Facebook's email notifications for new posts in the group, then trigger your workflow from that inbox. That is worth trying before anything more fragile. Claw Post is a posting layer and does not do this part.

Good habits for posting to groups from an agent

A group is not a broadcast channel, and these communities notice when someone treats it like one.

  • Write for each group. Do not paste the same text into ten groups. Meta's spam policy exists for exactly that pattern, and group members report it faster than any filter catches it.
  • Read the group rules first. Many groups ban links, promotions, or posts on certain days.
  • Post less than you think. One useful post a week in the right group beats daily posts nobody asked for.
  • Approve every post. Keep the final "yes" with a human, especially on your personal account.

Summary

  • Meta removed the Facebook Groups API from every version on 22 April 2024. publish_to_groups is gone, and group admins can no longer install apps.
  • Pages still have an official API, but groups do not.
  • For groups, your choices are to paste posts yourself, run a remote browser holding your login, or let your own Chrome do the posting.
  • We built Claw Post for that last route. Your agent calls our MCP, and your own logged-in desktop Chrome posts to groups you already belong to, after you approve each post.

Related: if your agent runs on a cloud computer and keeps hitting captchas or block pages, read why your AI agent gets blocked on Reddit from a cloud browser.

Our API docs are at clawpost.net/api-docs.

Sources