Docs · Workflows
Work that spans days, not messages.
"Collect availability from five people, then book" cannot live in one chat message. Cedric runs it as a workflow: it waits, catches replies, nudges, and finishes the job.
- A workflow keeps going across days, weekends, and restarts. Nothing depends on a chat staying open.
- It waits on named people: a reply in DM counts automatically, and quiet ones get nudged.
- When chat is the wrong shape for the answers, Cedric sends a short private form and the submissions flow back into the run.
- Every run is visible in the Action center: what is pending, what waits on you, what finished, what could not.
- Runs are bounded by design. A workflow can stall and tell you; it cannot loop forever or run away.
Why a message is not enough
Real delegated work has gaps in it: waiting for the third person to answer, for the client to fill the brief, for Thursday. A chat thread forgets; whoever owns the task becomes the reminder system.
A workflow holds the state instead. Cedric picks the job up each time something happens, does the next step, and parks again. The finish line, not the thread, is the contract.
Kevin
Maya
Devin
Hannah
TomásThe loop: five interviewers asked on Monday, the quiet two nudged on Tuesday, and the loop booked the moment the last reply landed.
Waiting on people
Five calendars, one booking, zero chasing by you.
Yara Nasser9:14 AM
@Cedric collect availability from the five interviewers, then book the loop.
CedricAPP9:15 AM
Running. I've asked all five in DM; three have answered. I'll nudge the quiet two tomorrow morning, and the run wakes the moment the last reply lands.
Replies find the run
When an awaited person answers, their reply is credited to the workflow automatically. Nobody forwards messages.
Nudges are built in
The quiet ones get a polite reminder with context, then an escalation to you if it stays quiet. You set the tone once.
It survives everything
The run is durable state, not an open chat. Friday's workflow finishes on Monday without anyone reviving it.
Forms
When the answers need boxes, not bubbles.
Lucia Moreau10:02 AM
@Cedric collect the campaign brief from the new client.
CedricAPP10:03 AM
Drafted a short form: goals, audience, budget range, deadline, existing assets. It lives at a private link, and each submission lands back in this thread with the workflow moving to the next step.
A private link, not a login
The form is a clean page at an unguessable address. The client fills it in a browser; no account, no attachments over email.
Submissions become progress
An answer is an event the workflow was waiting for. The run wakes, processes it, and moves on without anyone copying data across.
Works on every platform
Forms are the universal fallback: whatever chat platform your team or client lives on, a link works.
Where a run lives on the dashboard
The Action center shows every run in one of five states, decisions included.
| Tab | What lives there |
|---|---|
| Pending | Approvals, live runs, and scheduled work, one line each with the decision right there |
| Waiting on you | Runs stopped for a person: a question with a reply box, or a prepared draft with Send and Discard |
| Completed | Runs whose deed actually happened, not just runs that ended |
| Couldn't run | Failures with the reason stated and a Retry |
| Previous runs | The finished history, kept browsable |
FAQ
The run nudges, then escalates to you, then parks with its state intact. Nothing silently dies and nothing spams forever.
No. Runs are bounded: limited resumes, limited retries, and an automatic stop on silence. A runaway loop is structurally impossible.
A schedule is time-driven: the report every Friday. A workflow is people-and-events-driven: it moves when replies and submissions arrive. See [recurring work and automations](/docs/recurring-work-and-automations).
Yes: pause it from the Action center or just tell Cedric. Anything the run wants to send outward still waits for approval, exactly like everything else.
Ready when you are
Hand off the whole job.
Not just the first step: the waiting, the chasing, and the finish. $50 in free credits, no card needed.
$50 in free credits, no card needed.