Help Center/Delegated Workspace
Run with Poppy
Preview a plan, approve it, run the next step or all remaining steps, schedule a time, and answer Poppy while it works.
Run with Poppy executes plan steps Poppy can actually do: create a link, add a bio entry, set up a DM automation, write a post, and similar supported actions. Anything Poppy cannot do stays with the Pointerly team and is marked By hand.
Nothing is written until the approval your workspace asked for is given. A preview is a dry run.
Where you'll find it
On an open request, the panel at the bottom of the plan shows how many steps are done and the split button Run with Poppy. The menu on that button chooses what the click does. On a narrow screen the panel is one line; tap it for Run with Poppy.
A single step can also say Run with Poppy. The dialog title is Run with Poppy for one step and Run plan with Poppy for the whole plan.
You see the button when you are allowed to run and there is an open step Poppy can take, or a run already in flight. The Pointerly team can run any executable step. You can run a step yourself only when Run Poppy's steps yourself is on and that step is marked as yours to run.
Before you start
- The request is not Done or Cancelled
- You can change status on Delegated (Manager and above). Editors can file and edit requests, not run steps
- The workspace has AI credits if the step charges one (see What it costs)
- The module the step writes is inside the areas you pay for and the Pointerly access you saved
The button stays off, with a reason, when:
| The panel says | Why |
|---|---|
| Starts after “…” | Another request has to finish first |
| Poppy is already on it | A run is open. One plan has one open run |
| A run is already scheduled | A future run is waiting |
| Still planning | The task list is not ready |
| Every step is done | Nothing left |
| Nothing Poppy can run here | The remaining steps are for the team, or you are not allowed to self-run |
What the preview shows
Each step in the dry run is labeled:
| Label | Meaning |
|---|---|
| Runs | Poppy will do this step in this run |
| By hand | The Pointerly team does it. Poppy will not |
| No access | The step needs a module this connection or this access level cannot change |
| Needs a pick | Poppy needs you to choose an account, a tag, a link, or another option before it can run |
| Not in this run | Left out of this click on purpose |
Make the picks in the dialog. Then confirm.
How a run is approved
Settings → Delegated Workspace → Approve Poppy runs chooses who must sign off before a write:
| Setting | What happens |
|---|---|
| Pointerly approves | The team’s approve click starts the run. This is the default |
| I approve each run | The team’s run waits. You see Pointerly needs your approval, then Approve or Decline |
| Pointerly, then me | The team approves first (Approve and ask the customer), then you do. Run Poppy's steps yourself stays off while this is selected |
When you run Poppy’s steps yourself, your click is the approval. The confirm label is Approve and run, and the run starts now.
A step with a future time does not start at the click. The click is still the approval. The run waits until that time. The card reads Scheduled plus when. Cancel run calls off a run that is waiting for your approval or waiting for its start time. Declining is Decline (Declined toast).
What the button can do
Open the menu on Run with Poppy:
| Choice | What it does |
|---|---|
| Run all remaining steps | Poppy works through every open step it can, in order. The main button label stays Run with Poppy |
| Run the next step | Only the next open step, then you decide |
| Schedule… | You say when in the thread, for example “run it Friday at 9” |
While a run is going, the card is labeled Poppy run. Poppy may stop and ask a question. Answer it on the card, including Something else… when the picks are not right. Your answer resumes the run. Unanswered conflicts show as a count on the panel (Waiting for your answer when it is your turn).
Toasts you may see: Sent to the customer for approval, Approved. Pointerly will run it., Approved. Pointerly will run it shortly, Poppy finished, or Poppy stopped with the reason.
What it costs
| Action | AI credits |
|---|---|
| Sending a request, structuring it, planning on the thread | Free |
| Each step Poppy executes | 1 AI credit of the workspace, including when the team or a scheduled run executes it |
A step that writes a post or a script (write_post / write_script) | The generation only, which AI Content charges itself. One credit total, not two |
| A step that is blocked, skipped, or fails before it writes | Nothing |
| A retry that finishes from output an earlier run already saved | Not charged again |
The preview note on a charged step is Uses 1 AI credit of the workspace. If the workspace cannot pay, the step says Not enough AI credits — buy a pack or enable pay-as-you-go. If credits cannot be checked, nothing runs: Could not check the workspace's AI credits; nothing ran. Try again.
Email and calendar content in a step uses the private AI route for sensitive data. See AI settings and sensitive data.
After the run
Finished steps show on the plan and as deliverables you can open (a link, a bio page, a post’s Open post, and so on). A failed step stays on the request for the team or for a retry. A retry reuses what the run already created instead of making a second copy.
The thread records the public events: a run was requested, you approved or declined, it was scheduled, cancelled, or rescheduled, and each step Poppy completed.