Playbooks automation
PartnerOS runs on an event bus, and Playbooks is how you program it. Build workflows on a visual node graph: trigger on any event, branch on conditions, wait on timers, and fan out to actions — send an email, generate a document, assign a task, accrue a commission, or fire a webhook.
Partner ops is a thousand tiny manual follow-ups
Send the welcome email. Remind them to sign. Assign the CSM. Accrue the commission. Notify on a stalled deal. Each is trivial; together they're a full-time job that never scales past a few dozen partners.
The flow, end to end
Trigger
An event hits the outbox — a deal is won, a partner onboards, a ticket breaches SLA.
Evaluate
The dispatcher drains the event and evaluates each playbook's trigger and enrollment filter.
Branch
Condition nodes route the enrollment; timer nodes hold it until the wait elapses.
Act
Action nodes execute — and often emit new events, so playbooks compose into larger journeys.
What's in the box
Event-driven triggers
Start a playbook on any platform event — a deal moved, a partner approved, a ticket opened, a document expiring.
Node-graph builder
Compose triggers, conditions, delays, and actions on a visual canvas. No code.
Conditional branching
All / any / not condition trees route each enrollment down the right path.
Timers & delays
Wait hours or days between steps; sweep timers advance enrollments on schedule.
Rich action set
Email, task, document generation, commission accrual, status change, and signed webhooks.
Enrollment filters
Scope who enters a playbook so the right partners get the right journey.
One event bus, drained by a dispatcher, powering everything
Every meaningful change emits an event into an outbox. A background dispatcher drains it, advances timers, and fans work out to workers. Playbooks, commission schedules, webhook deliveries, and SLA escalation are all just consumers of the same rail.
- ✓Durable outbox + polling dispatcher — no lost events
- ✓Background workers for webhooks, payouts, reports, and SLA sweeps
- ✓Actions emit events, so automations chain without glue code
A visual node graph anyone on your team can reason about
Triggers, conditions, delays, and actions are nodes you wire together on a canvas — no code, no YAML. Condition nodes carry all/any/not trees, timer nodes hold an enrollment for hours or days, and an enrollment filter decides exactly which partners ever enter the journey.
- ✓Trigger on any event; an enrollment filter scopes who enters
- ✓All / any / not condition trees route each path
- ✓Delays and timer sweeps advance enrollments on schedule
Deal registration & PRM
Register deals, protect them, and move them across configurable pipelines on a shared board.
Learn moreCommissions & payouts
Rules-based commissions, an auditable ledger, and managed payouts partners can withdraw.
Learn moreAPI & integrations
A generated OpenAPI, scoped machine keys, signed webhooks, and an event-ingest rail.
Learn moreReady to run your partner program in one place?
Book a walkthrough and see recruitment, PRM, automation, payouts, CX, and dashboards working together — on one platform.