Some tasks only need to be handled once, while others repeat every week with roughly the same steps. In Busabase, how should I decide between giving an Agent a task and setting up a workflow? What role should frequency, consistency of the steps, and human review play in that decision?
For work you want done now, give the Agent a task. For steps you want people or agents to follow repeatedly, save the method as a Skill or prompt in the Busabase workspace. You can do both: ask an Agent to process one real case, review the result, refine the instructions, then save the useful steps for next week.
A Workflow node is for describing a repeatable flow with branches, approvals, waits, and actions. The important current limit is that Busabase saves and validates the Workflow definition, but the Workflow canvas does not execute it on its own yet. So a weekly task does not become automatic just because you draw it there. To run it on a schedule today, you need an actual scheduler and an Agent/integration with the right access and notification channel; the team still needs to review consequential changes.
My rule of thumb: start with an Agent task when the inputs or decisions vary; turn a stable, reviewed method into a Skill; model a Workflow when the handoffs and decision points themselves need to be explicit. Decide where human review happens *before* granting direct write access. For example, a weekly customer-update summary can be an Agent task using a shared Skill, with proposed record changes submitted for team review. See the node types and Workflow status and Change Requests. Which part of your weekly job needs to run without someone starting it?
Sign in to join the discussion. Reading is always open; you only need an account to post.
Sign in