Workflows

A workflow is a reusable, repeatable process that tells an agent what to do, step by step.

Note: "Workflow" is the current product term. Internally — in the codebase, the tRPC API, and the /playbooks route — this entity is still called a playbook. They are the same thing.

If an agent is the worker, a workflow is the job description. You write out what needs to happen — pull data from Stripe, summarize it, email the results — and the agent follows along. Workflows can be as simple as a paragraph of instructions or as detailed as a multi-branch decision tree.

Where workflows fit

The Workflows surface is author-only — it's where you define and edit workflows. Setting one up to run, watching its runs, and scheduling it happen on the Jobs surface; results land in Pulse. A workflow is the app — there is no separate "Apps" concept. Most people author workflows through the guided Your job pane rather than filling in fields by hand.

What It Does

• Defines the work — A workflow captures a repeatable process so you do not have to explain it every time.
• Assigns an agent — Each workflow has a default agent responsible for executing it.
• Runs on demand or on schedule — You can trigger a workflow manually, set it to run on a cron schedule, or kick it off from an event.
• Tracks every execution — Each time a workflow runs, Pencel creates a run with a full step-by-step log.

Key Properties

Property	Description
Name	Workflow title — keep it short and descriptive
Instructions	Natural-language description of what the agent should do
Steps	Optional structured steps (action, decision, approval, parallel)
Default Agent	Which agent runs this workflow by default
Trigger	How the workflow starts (manual or scheduled)
Approval Required	Whether runs need human approval before starting
Status	draft, active, or archived
Outputs	Expected output types (reports, emails, data files, etc.)
Required Tools	Integrations needed for this workflow to work
Inputs	Runtime parameters accepted at launch (text, number, boolean, select, date) — a workflow with inputs simply presents a form when you run it
Guardrails	Criteria the final output must satisfy
Output Schema	Structured definitions for expected outputs
Execution Mode	How the agent interprets the workflow: agentic (default) or guided

Two Ways to Write a Workflow

You have two approaches, and you can mix them.

Freeform Instructions

Write a natural-language description of what the agent should do. The agent interprets the instructions and figures out the best sequence of actions.

Pull the latest revenue numbers from our Stripe dashboard.
Compare them to last quarter's targets.
Write a two-paragraph summary highlighting wins and misses.
Email the summary to the leadership team.

This is the fastest way to get started. It works well for straightforward tasks where the agent has enough context to fill in the gaps.

Structured Steps

Break the workflow into explicit steps with defined types, branching logic, and approval gates. Each step has a type — action, decision, approval, or parallel — and you control exactly what happens at each point.

Structured steps are better when:

• The workflow has conditional branches ("if X, do Y; otherwise do Z")
• Certain steps need human approval before continuing
• Multiple tasks should run at the same time
• You need a precise, auditable sequence

INFO

Most users start with freeform instructions and add structured steps as they refine the workflow over time. You do not need to commit to one approach upfront.

Workflow Status

Status	Meaning
Draft	Work in progress. Cannot be triggered by schedules or events. You can still run it manually for testing.
Active	Ready for production. Schedules and event triggers are live.
Archived	Retired. Will not run, but history is preserved. You can reactivate it later.

TIP

Use draft status while you are iterating on a workflow. This prevents accidental scheduled runs while you are still tweaking the instructions.

Example: Weekly Sales Report

Here is what a simple workflow might look like:

Field	Value
Name	Weekly Sales Report
Default Agent	Sales Analyst
Trigger	Schedule — every Monday at 8:00 AM
Instructions	Pull this week's closed deals from Stripe. Compare to quota. Write a summary with a table of top deals and a paragraph of commentary. Save as a PDF artifact.
Approval Required	No
Required Tools	Stripe connection

What's Next

• Agents vs Workflows — When to chat vs. create a workflow — the role/job mental model
• Steps — Learn about the four step types for structured workflows
• Triggers & Schedules — Control when your workflow runs
• Agents — Configure the agent that executes your workflow