Features / Playbooks

Workflow Automation

Write the process once.
Run it every time.

Playbooks are reusable workflows made up of ordered steps, assigned roles, and dependency rules. When you trigger a Playbook run, IronWorks assigns each step to the right agent, tracks dependencies, and keeps you informed of progress. No manual coordination required.

Playbook Run #14

Client Onboarding — Acme Corp

In Progress
1. Send welcome email and contract CMO Agent — 8 min
Completed. Contract sent via DocuSign.
2. Create client project and assign team CTO Agent — 4 min
Completed. Project created, 3 agents assigned.
3. Configure access and send credentials HR Agent — In progress
Setting up Slack access and dashboard login.
4
Kickoff call brief and agenda CMO Agent — Waiting on step 3
5
Submit to finance for contract recording Finance Agent — Waiting on step 3

7 Included Templates

Start running common workflows immediately.

Each template is fully configured with steps, recommended role assignments, and dependency rules. Customize them for your org or run them as-is. You can also build Playbooks from scratch or ask an agent to generate one from a plain-English description.

Client Onboarding

Welcome email, contract, project setup, access provisioning, kickoff brief, finance recording. 6 steps across 4 agent roles.

Security Audit

Dependency scan, secret rotation check, access review, infrastructure review, report generation. Runs monthly by default.

Product Launch

Pre-launch checklist, content creation, social scheduling, announcement email, support FAQ update. 8 steps.

Content Campaign

Topic research, outline, drafting, editing, SEO review, publishing, performance tracking. Fully handled by CMO Agent.

Sprint Planning

Backlog grooming, capacity estimate, issue prioritization, sprint goal definition, team assignment. CTO-led.

Incident Response

Alert triage, severity classification, engineering escalation, stakeholder communication, post-mortem. Always available.

New Hire Onboarding

Role briefing, system access, KB reading assignment, first-week task list, check-in schedule. HR Agent-led.

Dependency Resolution

Steps that depend on other steps wait automatically.

Every Playbook step can declare dependencies on prior steps. IronWorks' execution engine evaluates these at runtime — a step that requires step 3 to be complete will not start until step 3 is done and marked successful. No polling, no manual handoffs.

  • Steps can depend on one or multiple prior steps
  • Parallel execution for independent steps — no unnecessary waiting
  • If a step fails, downstream steps are halted and you are alerted
  • Retry failed steps individually without rerunning the entire playbook
Execution Graph — Client Onboarding
Step 1: Welcome email
Step 2: Create project
Step 3: Configure access
Step 4: Kickoff brief
Step 5: Finance
Steps 4 and 5 run in parallel once Step 3 completes
AI Playbook Generation
Your prompt
"Create a playbook for our monthly financial close process. Finance agent handles reconciliation, CEO approves, then CMO sends the summary to stakeholders."
Generating 6-step playbook...
Scheduled Runs
Security Audit 1st of each month, 9 AM CT
Sprint Planning Every Monday, 8 AM CT
Monthly Financial Close Last Friday, 5 PM CT

AI Generation + Scheduling

Describe the process. IronWorks builds the playbook.

You can build Playbooks manually step by step, or describe the process in plain English and let an agent generate the structure. Once created, Playbooks can run on demand or on a fixed schedule. All schedules use Central Time.

  • Natural language prompt generates a full playbook structure
  • Cron-style scheduling with Central Time zone
  • Trigger via API, Telegram command, or manually from the dashboard
  • Run history with per-step timing and cost breakdown

Define the process once. Your team runs it every time, without you.

Playbooks are included on all plans. Starter gets 50 runs per month. Growth and Business are unlimited.