Use case
Every account carries work that must happen on a cadence and never gets prioritised: the weekly scan, the status roll-up, the check nobody has time for. Multiply runs these as workflows on a daily, weekly or monthly schedule, autonomously, and reports back as a normal task — so the recurring work stops depending on someone remembering it.
Today
Not because anyone is careless: because a task with no deadline always loses to a task with one. So the weekly check happens in month one, sporadically in month two, and turns into a scramble before the quarterly review. The cost is invisible until a client asks a question the agency should already have known the answer to.
How it runs
You write the instruction; Multiply runs it on the cadence you set using the agents and tools available to it. There is no separate automation language to learn.
Attach it to the workspace or project it concerns, so it runs with that client’s context rather than generically.
Workflow runs are autonomous — the point is that they happen while nobody is watching. Normal chats and tasks still propose a plan and wait, and a run that genuinely cannot proceed asks a clarifying question rather than hanging.
Runs land as tasks on the project with sources attached, so a result can be read, edited, forwarded or exported like anything else.
The instruction is the whole craft here. A workflow told to report on everything gets ignored within a fortnight; one told to report only when something crosses a threshold you actually care about earns its place. Run one workflow for one client for a month before copying it across the roster — the month tells you whether the instruction was any good, and that is the part worth iterating on.
Two neighbours worth reading: market and competitor monitoring is the most common first workflow, and client reporting is the most common second one.
Related: the product for how the pieces fit together, multi-client operations for running several of these at once, agency operations for the underlying idea, and the other use cases if recurring work is not the job you want to start with.
We will write your first workflow with you, against a real account.
Daily, weekly and monthly. Available to all customers, not behind a trial flag.
Output lands as a task with sources rather than going anywhere client-facing, so a person reads it before it matters. Autonomy here is about the run happening, not about the result being sent.
The pattern that works is one per client per job, added deliberately. The pattern that fails is twenty added in the first week, because nobody reads twenty reports and the whole set gets muted together.
Whatever came to mind reading this is the right first workflow. Bring it to the walkthrough.