Workflows
PocketClaw is built around a few jobs it does completely rather than a builder you assemble yourself. Each one reads across the tools you have connected and stops before anything leaves your account.
What it does
The morning brief
PocketClaw checks your email, calendar, errors, and tasks before you wake up, then briefs you on what actually needs you today and drafts the replies. Nothing sends until you approve.
Inbox triage
PocketClaw reads what came into your inbox, answers what it can, and drafts the rest in your voice. You review and approve. Works with Gmail, Outlook, Zendesk, and Intercom.
From customer issue to root cause
A customer reports a bug. PocketClaw finds the matching error, counts who else is affected, names the change that caused it, files the fix task, and drafts the customer reply.
What every workflow shares
Each one reads across every tool you have connected rather than working inside a single app. That is what lets PocketClaw match a customer complaint against a real error and the change that caused it, or tell you which of the meetings on your calendar you have not prepared for.
Each one also stops before the last step. PocketClaw does the reading, the cross-checking, and the drafting, then shows you what it prepared. Replies, filed tasks, and anything else that leaves your account wait for your approval.
Workflows and automations are not the same thing
A workflow is a job PocketClaw knows how to do. An automation is a workflow put on a schedule. You set one up by describing the routine in chat, and PocketClaw turns that description into a schedule without a canvas or a branching editor. Every run lands in its own thread so you can see what it checked, what it found, and what it prepared.
You can also just ask for any of this once, in the moment, with no schedule involved.