rtylr
rtylr Flow · Work OS


Drag-drop kanban. Tasks linked to the actual invoice, customer, or shift they care about. Automations that fire when a PO is approved or payroll closes, no Zapier, no duct tape. The work OS your team will actually open.

Workspaces/Operations/Weekly sprint
8 tasks
BoardListTimeline
Backlog2
Seasonal menu rollout, Q3
OpsMC
New supplier onboarding: Rossini
ERPJK
+ Add task
In progress3
Friday dinner covers, staffing plan
HRHighSP
Redo brunch prep checklist
KitchenAR
Email blast: Mother’s Day brunch
CRMMC
+ Add task
Review1
Espresso machine repair SLA
VendorJK
+ Add task
Done2
Q1 sales-tax filing
FinanceSP
POS firmware v4.2 rollout
OpsAR
+ Add task
AUTOMATIONS · NO ZAPIER REQUIRED

When this happens.
Then that, automatically.

Every app in rtylr emits events. Every app listens. Click an example, or let it auto-play, to see what real rules look like.

ERPWHEN
Purchase order approved
PO #4821 · Rossini supplies · $2,480
FlowTHEN
Create task on purchasing
Assigned to head of purchasing · due tomorrow
1 / 6

Boards for every team

Kanban, list, timeline, or calendar. Each team picks their view. Same data underneath.

Tasks that link to reality

Attach a task to a customer, a supplier, an invoice, or a shift. When it moves, everything updates.

Automations without Zapier

When a PO is approved → task on purchasing. When payroll closes → reminder on HR. Built in.

TASKS WITH CONTEXT

A task that knows the invoice,
the customer, and the shift.

In rtylr Flow, tasks are first-class citizens linked to other objects in the platform. “Follow up on invoice #4821” opens the invoice. “Cover Sam's Friday closing shift” jumps to the schedule. No tab-switching, no copy-paste, no “wait, which one?”

Linked · InvoiceLinked · CustomerLinked · ShiftLinked · SupplierLinked · Menu itemLinked · Location

Stop losing work
between tools.