Manage Comment Automation

Step-by-step guide to creating a Facebook comment automation in ReachOwl: set your comments, schedule, and daily limit, then control status and review executions.

Use ReachOwl comment automations to automatically post comments on Facebook through your connected accounts. This guide walks you through the full lifecycle: getting an executor, creating a comment automation, controlling its status, reviewing executions, updating it, and deleting it.

1. Get executor IDs

   Comment automations need at least one browser executor. List available executors from your app states and pick an id.

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

   {
     "data": [
       {
         "id": 101,
         "platform": "facebook",
         "status": "active"
       }
     ]
   }
   

   Save the id of an active executor for the next step.

2. Create the comment automation

   Send a POST request to /api/v1/comment-automations with your comment content, executor, schedule, and daily limit.

   curl -X POST "{{baseUrl}}/api/v1/comment-automations" \
     -H "Authorization: Bearer {token}" \
     -H "Content-Type: application/json" \
     -d '{
       "name": "Post Engagement",
       "platform": "facebook",
       "executor_ids": [101],
       "comments": [
         {
           "text": "Great post, {{first_name}}! Thanks for sharing."
         }
       ],
       "schedule": [
         {
           "day": "Monday",
           "start_time": "09:00",
           "end_time": "17:00"
         }
       ],
       "limit": 30,
       "status": 0
     }'
   

   {
     "data": {
       "id": 12,
       "name": "Post Engagement",
       "status": 0,
       "limit": 30
     }
   }
   

   You can personalize comment text with the {{first_name}} placeholder. ReachOwl replaces it with the target’s first name when the comment is posted.

3. Pause or resume

   Update the status through a PATCH request instead of using a dedicated pause endpoint. Send status: 0 to pause or status: 1 to resume.

   Pause

   curl -X PATCH "{{baseUrl}}/api/v1/comment-automations/12" \
     -H "Authorization: Bearer {token}" \
     -H "Content-Type: application/json" \
     -d '{"status": 0}'
   
4. Review executions

   Every run of a comment automation is recorded as an execution. Use the executions endpoint to see what was posted and whether it succeeded.

   curl -X GET "{{baseUrl}}/api/v1/comment-automations/12/executions" \
     -H "Authorization: Bearer {token}"
   

   Check executions after resuming an automation to confirm comments are posting as expected.

5. Update the automation

   Change the schedule, comments, or daily limit with PATCH. Send only the fields you want to change. PUT is also supported and calls the same update handler.

   curl -X PATCH "{{baseUrl}}/api/v1/comment-automations/12" \
     -H "Authorization: Bearer {token}" \
     -H "Content-Type: application/json" \
     -d '{"limit": 50}'
   
6. Delete the automation

   Remove a comment automation you no longer need.

   curl -X DELETE "{{baseUrl}}/api/v1/comment-automations/12" \
     -H "Authorization: Bearer {token}"
   

   Deleting a comment automation cannot be undone. To stop one temporarily, set status to 0 instead.

There are no separate /pause, /resume, or /clone routes for comment automations in the ReachOwl v1 API. Use PATCH with the status field to pause or resume.

Related pages

• Comment automations overview — status, schedule, limits, and executions
• /api-reference/comment-automations/create — create a comment automation
• /api-reference/comment-automations/executions — list executions