OpenQuok plugs for Threads, LinkedIn, and X after publish

Updated
4 min read Rati Montreewat
Blog post content
OpenQuok plugs for Threads, LinkedIn, and X after publish

A plug runs after your post goes live. It does not change the caption you scheduled. It adds a reply, comment, repost, or reshare.

Schedule plug/engagement on Threads/X/Linkedin with OpenQuok

Pick the plug that matches the job. An internal plug is a same-account action on one post. A cross-account plug uses another connected channel on that network. A global plug is a channel rule at Auto Plugs when likes hit your threshold. Compare them on the plugs overview.

These walkthroughs use Threads, LinkedIn, and X. For a Threads connect-and-composer guide, see Schedule Meta Threads posts, replies, and plugs with OpenQuok.

Pick the plug for the job

Follow-up comments are not plugs. They are same-account thread or comment rows in the composer. They run right after the main post. See Threads and comments.

Add follow Up comments in OpenQuok Post Editor

Internal and cross-account plugs wait for those rows (and the thread finisher on Threads or X). Global plugs run later on posts that already published.

Purple Settings and Plug settings both write cross-account plugs on the publishing channel. They call the same backend field. Settings also holds the Threads internal plug. Plug settings does not.

Use case: company Threads, personal comment

You run a company Threads profile and a personal Threads profile in one workspace. You want the company thread live first. Then the personal profile comments.

  1. Connect both Threads channels. Queue the main post and Follow-up comments on the company channel.

  2. For a same-account CTA after the thread, open Settings. Enable Delayed reply (internal plug). The default delay is 120 seconds. Do not add that CTA as another Follow-up comments row.

  3. Enable Add comments by other accounts in Settings or Plug settings. Pick the personal profile. Enter the comment. Delay defaults to 2 minutes. The publisher cannot act on itself.

Open OpenQuok Thread Plug Settings Modal

OpenQuok publishes the company thread first. Then it posts the personal comment. Full composer steps: Schedule Meta Threads posts, replies, and plugs.

Use case: LinkedIn Page update, exec comment or reshare

You publish from a company Page. A founder profile in the same workspace should comment or reshare after go-live.

  1. Connect the Page and the personal LinkedIn channel. Write the Page post. Add text-only Follow-up comments if you need same-account comments.

  2. Open Settings on the Page channel. Enable Add comments by a different account or Add re-posters.

  3. Pick the founder profile. Set comment text (for a comment) and delay.

Open OpenQuok Linkedin Settings Modal

Personal LinkedIn has no global likes-threshold rule. If you want auto-repost after likes, use the LinkedIn Page on Account → Auto Plugs.

Use case: X launch tweet, another profile reposts

You schedule a launch tweet from the brand account. A second connected X profile should amplify it.

  1. Connect both X channels. Write the tweet. Add same-account thread replies in Follow-up comments if you need a thread.

  2. Open Settings on the publishing account. Enable Add re-posters. Pick the other X profile. Set a delay.

On X, a cross-account plug reposts the root tweet. It does not post a reply from another account. Use Follow-up comments for quote-less replies from the publisher.

Open OpenQuok X Settings Modal

Use case: promo reply after likes

You want a CTA only after the post proves it resonates. That is a global plug, not a setting on one draft.

  1. Go to Account → Auto Plugs. Pick X, LinkedIn Page, or Threads.

  2. Turn on Auto plug post. Enter the likes amount. Enter the reply or Page comment text.

  3. On X and LinkedIn Page you can also turn on Auto repost posts. Threads supports auto plug post only. There is no Threads auto-repost.

The worker checks every 6 hours, up to three times. New rules apply to posts published after you save. They do not change posts that are already live.

Order of operations

  1. Publish the main post on each selected channel.

  2. Run Follow-up comments and the thread finisher when you enabled them.

  3. Run the internal plug (Threads delayed engagement reply).

  4. Run cross-account plugs (comment, repost, or reshare from other channels).

  5. Global plugs run later when likes cross your threshold.

Follow-up comments and plug replies count as real posts. Rate limits still apply. Cross-account plugs need two connected channels on that network.

CLI and API

Per-post plugs live on the publishing channel in providerSettingsByIntegrationId.

  • Threads same-account delayed reply: threads.internalEngagementPlug

  • Threads other-account comment: threads.crossAccountPlugs

  • X other-account repost: x.crossAccountPlugs

  • LinkedIn comment or reshare: linkedin.crossAccountPlugs

Recipes: Threads, X, and LinkedIn CLI examples. MCP payloads: MCP examples — X.

Global plugs use openquok plugs:catalog, plugs:list, and plugs:upsert. See CLI usage — Global plugs.

Try it

Start a trial. Connect Threads, LinkedIn, or X. Run one of the jobs above in Settings or Auto Plugs. Plan limits are on Pricing.

Frequently asked questions

Step-by-step summary

OpenQuok plugs for Threads, LinkedIn, and X after publish

  1. 1. Tell plugs apart from follow-up comments

    Follow-up comments are same-account rows in the composer and run right after the main post. Plugs run after that chain (and after the thread finisher on Threads or X). See Threads and comments and the plugs overview.

  2. 2. Schedule the main post first

    Schedule the main caption or parent post on Threads, LinkedIn, or X. Plugs do not change the caption you queued—they add engagement after go-live.

  3. 3. Add an internal plug on Threads when needed

    On the publishing Threads channel, open Settings and enable Delayed reply (internal plug) for a same-account CTA after the thread. Do not duplicate that CTA as another follow-up row. See Internal plugs.

  4. 4. Configure cross-account plugs in Settings or Plug settings

    Enable Add comments by other accounts (Threads), Add comments by a different account or Add re-posters (LinkedIn Page), or Add re-posters on X. Pick another connected profile in the workspace and set delay and copy. On X, cross-account plugs repost the root tweet—they do not reply from another account. See Cross-account plugs.

  5. 5. Set global plugs for likes thresholds

    For a promo reply only after the post gets traction, go to Account → Auto Plugs on X, LinkedIn Page, or Threads. Turn on Auto plug post, set the likes amount and reply text. The worker checks every 6 hours, up to three times; new rules apply to posts published after you save. See Global plugs.

  6. 6. (Alternatively) Use CLI or API for the same plug fields

    Per-post plugs live under providerSettingsByIntegrationId (e.g. threads.internalEngagementPlug, threads.crossAccountPlugs, x.crossAccountPlugs, linkedin.crossAccountPlugs). Global rules use openquok plugs:catalog and plugs:upsert. See CLI usage — Global plugs and the Threads, X, and LinkedIn provider docs.

OpenQuok plugs

Post-publish actions on Threads, LinkedIn, and X: same-account internal plugs, cross-account comments or reposts, and global auto-plugs when likes cross a threshold. You approve drafts on the calendar before anything runs.

Brand: OpenQuok

Learn more

Comments

No comments yet.

Add a comment

Sign in to comment.

0/1000

Start free. Publish with confidence.

Connect your agent, review every draft, and schedule posts across channels before anything goes live.

Discord Support