Schedule Recurring Posts to Facebook Groups

Use ReachOwl post schedulers to automatically publish content to multiple Facebook groups on a recurring interval or fixed schedule.

The ReachOwl Post Scheduler lets you queue content to be published across multiple Facebook groups on a repeating interval or fixed schedule. This guide covers setting up a scheduler, pausing it, removing specific queued posts, and cloning an existing scheduler.

1. Get group URLs

   Start by listing the groups synced to your workspace so you can target the right ones.

   Request

   curl -X GET "{{baseUrl}}/api/v1/groups" \
     -H "Authorization: Bearer {token}"
   

   Copy the group_url values you want to schedule posts for.

2. Get an executor ID

   Post schedulers require an active browser executor. List app states and pick an id.

   Request

   curl -X GET "{{baseUrl}}/api/v1/app-states" \
     -H "Authorization: Bearer {token}"
   

   Save one active executor id for the next step.

3. Create a post scheduler

   Create the scheduler with a recurring interval, target groups, and post content. The example below posts every 20 minutes.

   Request

   curl -X POST "{{baseUrl}}/api/v1/post-scheduler" \
     -H "Authorization: Bearer {token}" \
     -H "Content-Type: application/json" \
     -d '{
       "name": "Weekly Tips",
       "executor_id": 101,
       "team_id": 3,
       "group_urls": [
         "https://facebook.com/groups/digimarketpro",
         "https://facebook.com/groups/startupfounders"
       ],
       "schedule_type": "interval",
       "interval": 20,
       "posts": [
         {"text": "Here is today's tip for growing your audience!"}
       ]
     }'
   
4. Pause the scheduler

   Change the scheduler status by sending a PATCH request to the scheduler ID.

   Request

   curl -X PATCH "{{baseUrl}}/api/v1/post-scheduler/88" \
     -H "Authorization: Bearer {token}" \
     -H "Content-Type: application/json" \
     -d '{"status": 0}'
   

   Use status: 1 to resume later.

5. Delete queue rows

   Remove specific queued posts by passing an array of queue IDs in a PATCH update.

   Request

   curl -X PATCH "{{baseUrl}}/api/v1/post-scheduler/88" \
     -H "Authorization: Bearer {token}" \
     -H "Content-Type: application/json" \
     -d '{
       "delete_queue_ids": [201, 202]
     }'
   
6. Clone a post scheduler

   Duplicate an existing scheduler, including its groups and posts, by using the clone_from field on creation.

   Request

   curl -X POST "{{baseUrl}}/api/v1/post-scheduler" \
     -H "Authorization: Bearer {token}" \
     -H "Content-Type: application/json" \
     -d '{
       "name": "Weekly Tips - Copy",
       "clone_from": 88,
       "team_id": 3
     }'
   

When schedule_type is set to interval, the interval value is interpreted in minutes. There is no separate scheduling endpoint. Create and update requests handle all scheduling behavior.