Platform / Workflows

The admin nobody owns, running without anyone owning it.

Every firm has work that is nobody's job and everybody's problem. This is where it goes.

Request a demo
Automations›New high-budget project kick-off
Active Save draft Publish

When

A project is created Event trigger · fires once per project
Change

If — optional, all conditions must match

Where Project budget is greater than 2,000,000 ×
+ Add condition

Then — steps run in order

1
Add entry in SharePoint spreadsheet Append a row to a connected workbook
⌄

Column mapping

Project ← Meridian Foods — Phase II
Client ← Meridian Foods Group
Budget ← $2,400,000
Owner ← Dana Whitfield
Created ← 12 Aug 2026, 09:14

Fields come from the trigger. Anything the project record holds can be written.

2
Send email Notify people inside or outside the org
⌄
Org role Admin
+ Add recipient

Recipients resolve to active org members. Arbitrary addresses are not allowed.

New project: Meridian Foods — Phase II

New project kicked off

Name: Meridian Foods — Phase II

Budget: $2,400,000

Client: Meridian Foods Group

Owner: Dana Whitfield

+ Add step
Run history Every execution, with what it did and why it did not.
  • Meridian Foods — Phase II 12 Aug · 09:14 2 steps · 1.8s
    Succeeded
  • Baker Hughes — Chart Integration P2 11 Aug · 16:02 2 steps · 2.1s
    Succeeded
  • Keystone Clinics — Revenue Cycle 09 Aug · 11:47 SharePoint 403 on attempt 1 · succeeded on attempt 2
    Retried
  • Gridline Advisory — Phase I 07 Aug · 08:31 2 steps · 1.6s
    Succeeded
  • HarborPoint — Freight Transformation 04 Aug · 14:20 Budget $250,000 did not meet the condition
    Skipped

A failed step retries on its own schedule and keeps the run open. Nothing is silently dropped, and a run that was correctly skipped says so rather than disappearing.

A trigger, optional conditions, and steps that run in order. Every run is logged, including the ones the conditions skipped.

In the product

How Octayne handles it.

  • Event, schedule and manual triggers
  • Conditions on any field
  • Deterministic and agentic steps
  • Org-level connections
  • Templating from trigger data
  • Run history and retries
  • Role-based permissions on every action
Event triggers

A project created, a budget threshold crossed, an invoice past its send date, a timesheet approved.

Schedules and manual runs

Weekly, monthly, or on a button — the same workflow, started a different way.

Conditions

Run only when it matters. Everything else is skipped and says so in the log.

Deterministic steps

Write a row, send a message, update a field, call a webhook. Same input, same result, every time.

Agentic steps

Hand a step to an agent when it needs judgement — draft the summary, assess the variance — inside the same run.

Connections

SharePoint, Outlook, Jira, Salesforce and QuickBooks, authorized once at the org level.

Templating from the trigger

Any field on the record that fired it can be written into a step.

Run history

Every execution with its inputs, its steps, its failures and its retries.

It runs on the record, not on a copy

A workflow reads the same engagement record the agents and the reports read. There is no export, no sync window, and no second version of the truth to reconcile.

Deterministic where it can be, agentic where it must be

Writing a row does not need a model. Judging whether a variance is worth escalating does. A single run can contain both, and the log says which step did what.

A skipped run is still a run

Conditions that do not match are recorded rather than silently dropped, because 'it did not fire' and 'it fired and did nothing' are different problems.

Inputs and outputs

What it uses, and what you get.

What it uses The systems and records it reads from.
  • Platform events
  • Schedules
  • The engagement record
  • Connected systems
  • Roles and permissions
What you get out What a partner can act on Monday morning.
  • Work that happens without being chased
  • Notifications that reach the right role
  • Registers that stay current
  • An auditable record of every run

The agentic layer

Agents that work here.

Intelligence Analyst Answers in plain language from live firm data, and composes the board pack — dashboards, models and decks — on request. Revenue Billing Agent Assembles the invoice from approved time and cost, resolves the exceptions, and holds the draft until it reconciles to the contract.

Elsewhere in the platform

Projects & Delivery Workstreams, planner, budget-to-actuals Time & Cost Time, expense, vendor and subcontractor Revenue & Cash Billing, collections, WIP and unbilled

Next step

See it run against one of your live engagements.

Bring an engagement that worried you. We will show you where the margin went, and the week Octayne would have told you.

Request a demo See pricing