Add and run AI actions one at a time

Before you begin#

An OwnPost connection with Full workspace tools and an external client such as Codex or Claude Code. Provider API setup is not required.

Steps#

1. 1

   Open Assistant → AI actions. Choose Add action, describe what the assistant should do, and review the account. Select Ideas, posts or blogs as context when useful. Choose saved drafts only when you want draft creation; reports and suggestions remain results for review.

2. 2

   Saving adds a Queued action. Edit, move, pause or cancel it as needed. Adding an action never launches a client, creates a schedule or calls your configured API provider. API writing can remain your default while actions use agents.

3. 3

   Choose a Run request option, then Prepare run request. Next action runs at most one item. Selected actions and All currently queued freeze an ordered list of IDs, revisions and one account; later additions are excluded. Review the preview, choose Copy run request, and paste it into your connected agent. You can also ask the ownpost skill to run your next OwnPost action or use the optional ownpost-actions skill.

4. 4

   The agent claims and completes one action before taking another from your selected batch. Its authenticated connection name and recorded activity appear with the work. Another client cannot claim another queue action while that claim is active. Personal routines and legacy preparation jobs remain separate.

5. 5

   If the result needs your answer, the action becomes Needs input and the batch stops. Read the question and saved partial progress, then answer in OwnPost or through the connected conversation. This queues the action again; run it separately when ready. Failed or Interrupted work also needs an explicit retry after reviewing what happened. Blog work can retain a checkpoint so the next run knows what is finished and what remains.

6. 6

   Open a completed action to review its report, sources, proposed text and saved draft links. A draft-creation action is complete only after its drafts and result are saved together. A proposed rewrite does not change a post until you choose to apply it. Completion does not publish to X or accept writing-style changes.

7. 7

   For a lost response, refresh the action before retrying so the client can recover its original result. Use Stop and edit to replace running instructions; its earlier attempt can no longer complete. Reconnect or renew access after revocation. Restored unfinished actions are Paused and require a deliberate new run.

Example request#

Add a report action to review recent measured posts and suggest one experiment. Saving queues it for later; when ready, run the next action with your connected assistant and open its saved report in OwnPost.

Use the ownpost-actions skill to run my next queued OwnPost action. Complete at most one action and show its saved result.

Check the result#

Each requested action has a saved result and output links, or a clear question/error explaining the next step. A next-action run stops after one item.

Keep going#