Skip to main content

Follow Back Script Configuration

The follow_back script opens the active account's follower graph on a real device and follows accounts that have not been followed back yet. It is available on TikTok, Instagram, and Threads in the Pro build.

Script Configuration (script_config)​

ParameterTypeRequiredDefaultDescription
usernamestringNoactive accountAccount whose follower graph should be opened
max_follow_countintegerNo20Maximum accounts to follow in this run (1–10,000)
enable_send_messagebooleanNofalseSend a greeting after each successful follow-back
message_contentstringConditional""Greeting text; required when enable_send_message is true
insert_emojibooleanNofalseInsert a random emoji into the greeting
note

The Threads desktop dialog defaults to 20 and exposes the maximum as a setting. The runner stops when the limit is reached or when the follower graph no longer yields new rows.

Example: Threads​

curl -X POST http://localhost:50809/api/v1/task \
  -H "Content-Type: application/json" \
  -d '{
    "serials": ["device_serial_1"],
    "script_name": "follow_back",
    "platform": "threads",
    "script_config": {
      "max_follow_count": 20,
      "enable_send_message": true,
      "message_content": "Thanks for following!",
      "insert_emoji": true
    }
  }'

If username is omitted, Threads uses the currently active account. Supplying usernames at the task level can target a specific account already matched to the device.

Behavior and limitations​

  • Follow-back is based on the platform's visible follower graph and skips rows that are already followed.
  • Sending a greeting is best-effort after a successful follow. A follow can succeed even when the optional message is unavailable for that target.
  • The task performs UI actions on the phone and can be affected by pagination, rate limits, private accounts, or unexpected prompts.

Error Codes​

CodeDescription
40001Invalid follow-back settings, including an empty greeting when messaging is enabled
40003Script is not supported by the selected build or platform
40301API access requires a Pro+ plan

See Also​