A useful workflow has clear inputs, a reviewable output, and a way to tell whether it succeeded. Start with one run before adding a schedule or external action.
Choose a practical starting point
- Content production: Turn approved material into channel-specific drafts.
- SEO review: Inspect a bounded set of public pages and prioritize evidence-backed improvements.
- Project handoff: Assemble status, deliverables, decisions, and open questions.
These guides are adaptable task briefs. They are not claims that every example is an installed template or an already-tested automation.
Give the task a complete brief
Include the desired outcome, source material, audience, constraints, and review point. Specify whether the result should remain a draft or whether a particular external action is intended.
Use these sources to prepare [deliverable] for [audience]. Include evidence for important claims, show missing information, and stop at the review point described below.
Review the first run
Open the deliverable, check its evidence, and compare it with the brief. If something is wrong, identify the specific gap and ask for a focused revision.
For project objectives, Review and complete an objective shows the live-tested approval transition. Do not use a completed status as a substitute for inspecting the output.
Keep the working recipe
Save the accepted brief, source expectations, output structure, and review checklist with the project. Change the inputs deliberately for the next run. Recheck facts and access rather than assuming a previous result makes every future run safe or correct.
Choose what starts the next run
| Desired start | Mechanism | Configuration route |
|---|---|---|
| An objective is created or reaches a selected status | Project Flow | Dashboard → Objectives → Project flow; conditions autosave |
| The manager has been inactive, or should review once/daily | Heartbeats | Workflows → Heartbeats; user-managed idle and scheduled checks |
| One specific action at one future time | Scheduled task | Ask the responsible agent and verify the saved task |
| A repeated task on a timetable | Recurring schedule | Ask the responsible agent and verify the saved definition |
| Eligible input needs a defined process | Trigger | Configure the project agent, source scope and instructions |
A project channel is an ongoing messaging route and does not require a trigger. Heartbeats are manager checks; agents can inspect them but current tools do not create or change them. Do not apply the agent-created cron procedure to every automatic mechanism.
For timed work, define the time zone, allowed actions, destination, and stopping condition. For objective-driven work, define the state handoff and review policy. Check the actual run and result independently of the saved configuration.
Check Plans and usage, especially if work may continue on paid balance. Recurring execution should solve a recurring need rather than simply repeat an unclear prompt.