An approval step gives you a deliberate checkpoint inside an Agent. When a run reaches that point, ProfitJam pauses it and places it in For Review. Nothing after the checkpoint runs until you approve it; rejecting it stops that run.

Add approval to a new Agent

The quickest route is to start from an Available template that already says it needs your approval. Select the template, choose Set up, answer its questions, and select Create agent.

For a custom Agent:

1. Open Agents and select Create.
2. Describe what starts the Agent and the ordered job it should perform.
3. State exactly where it must pause for approval.
4. Include the short instruction you want the reviewer to see.
5. Select Set it up.

For example: "When a paid order arrives, prepare the follow-up, then pause before sending. Show the instruction: Check the recipient and message, then approve to continue."

Tempo checks the request against the Agent building blocks currently available. When it can build the request, it creates a draft Agent. If a trigger or step is not available, it explains the missing part instead of silently creating a partial Agent.

Open Agents → Installed and select Activate when the draft is ready to run.

Important: The current Agents screen does not have a visual step editor. To add an approval to an existing Agent or change its approval instruction, create a replacement draft with the revised request before activating it.

Review a waiting run

Open Agents → For Review. The tab count shows how many Agent runs are waiting. Each card shows:

• the Agent name;
• how long the run has been waiting; and
• the instruction configured for that approval step.

The approval card is a checkpoint, not a preview of work produced by an earlier step. Read the instruction and check any relevant record or destination before making the decision.

You can add an optional note or reason, then choose:

• Approve to complete the checkpoint and resume that same run at its next ordered step.
• Reject to stop the current run and mark it as failed.

The optional note records context with the decision. It does not edit generated work, ask the Agent to revise it, or send the run down another branch.

Check what happened

After a decision, open Agents → Installed and select the Agent to view Run history. The run and its individual steps show whether they are waiting, completed, or failed.

Approval applies only to that one run. The active Agent remains available for the next matching event, and each future run pauses independently when it reaches the same checkpoint.

Common questions

Why is nothing showing in For Review?

An approval appears only after an active Agent starts a run and reaches its approval step. Check that the Agent is Active, cause or wait for its matching trigger, then review its latest run under Installed.

Does approving here approve a social post, blog post, or email draft?

No. For Review controls Agent run steps. It is not a general approval queue for content. Approval lets that Agent continue to whatever step was configured next.

Can Reject send the run down a different route?

No. Reject stops and fails that run. Approval steps do not create yes/no branches.

Can I change the instruction on a waiting card?

You can add an optional decision note, but that does not change the configured instruction. Create a revised draft Agent when the checkpoint itself needs different wording or placement.