Platform · Workflow & Automation
What you draw is what runs.
Draw the process in standard BPMN, and Plant an App runs it. It starts on any event, every form, API, and AI assistant can reuse it, and it's versioned as it changes.
Model
One picture for business and IT.
The people who know the process and the people who run the systems work from the same diagram. And because it’s the diagram that runs, it’s never out of date.
Decisions and parallel paths.
Branch on any condition, or run steps side by side and continue when all of them finish.
Mistakes caught before saving.
Built-in checks flag disconnected steps, missing labels, and incomplete actions while the process is drawn.
Tested before it’s trusted.
Run the workflow with real inputs and see every output and how long it took, before anyone depends on it.
450+ ready-made actions across data, documents, messaging, integrations, and AI, with C#, JavaScript, or PowerShell when a step needs code.
Reuse
Every workflow becomes a building block.
Save a workflow, and the rest of the platform can use it. Logic lives in one place, however many places need it.
- Forms
- Listings
- APIs
- Scheduled jobs
- Other workflows
- AI assistants
One workflow
One rule, one place to change it
Typed at the edges.
Inputs and outputs have types and defaults. Pass a record’s ID, and the whole record arrives ready to use.
Isolated in the middle.
Each workflow sees only what it’s given and returns only what it declares, so one change can’t ripple into another.
Documented automatically.
Every saved workflow becomes an action with its inputs, outputs, and description, ready for the next builder to find and use.
Change the rule once.Everything that uses it follows.
Adapt
Keep the process stable. Change the rules behind it.
The same process often runs under different rules for each program, region, or customer. Workflow Contracts fix what the process expects, while the rules behind it vary.
Workflow Contract
Approval policy
Request → Decision, Approver
- WorkflowStandard grants
- WorkflowResearch programs
- WorkflowEU-funded projects
One interface, many implementations.
A Workflow Contract fixes the inputs and outputs. Any number of workflows can fulfil it.
Chosen as the process runs.
The right implementation is picked at runtime, so a new rule set is a new workflow, not a change to every form and API that uses it.
Approvals that follow policy.
Who signs off, in what order, above which amount: each program’s rules live in their own workflow, and every request follows the rules that apply to it.
Automate
Runs on events, not reminders.
Work starts the moment something happens, not when someone remembers to check.
A record changes.
Inserted, updated, or deleted, with its values before and after, down to specific columns.
An email arrives.
Filtered by sender, subject, or content. Attachments included.
A schedule comes due.
Once, daily, every few minutes, or on any cron schedule.
Someone signs in.
Or a new account is created.
A partner system calls.
Through an API endpoint you build (the webhook partners need) or a message to a Teams bot.
The server goes quiet.
Heavy work waits for idle capacity. Startup and application errors can start work too.
20 trigger types, all starting work through the same engine.
Operate
Built to fail safely.
Processes that matter have to behave when something goes wrong, and leave a record when it does.
Failures are part of the process.
Errors take a planned path: caught, handled, and reported. Administrators see the detail; everyone else sees a clear message.
Concurrent work stays separate.
Each run starts with its own context and shares no state with any other. Parallel branches merge back only when all of them finish.
Every run leaves a record.
Status, timing, and trigger for each job run, with full detail captured when debugging.
Evolve
Every change is versioned. Every version can come back.
Processes change as often as the organization does. None of that history is lost.
Committed to Git.
Every workflow change is recorded, so there’s always a history of what changed and when.
Restore in one step.
Bring back an earlier version in place of the current one, or alongside it as a new workflow.
Portable by design.
Export, import, and clone workflows and jobs, or copy selected steps from one workflow into another.
Delegate
AI that works through your workflows.
Give an AI model a set of workflows, and it can use them as tools, deciding which to call, and with what, to answer a question or finish a task.
What’s the status of request R-1042?
Calls workflowGet request status (Reference: R-1042)
R-1042 was approved on 12 September, and the approval letter has been sent.
Your logic, not a guess.
The model acts through the same workflows, rules, and permissions as everything else in the application.
As many steps as it takes.
It can call several workflows before it answers.
Your choice of model.
OpenAI, Azure OpenAI, or Claude and Llama on Amazon Bedrock.
450+
ready-made actions
20
trigger types
1
engine behind forms, APIs, jobs, and workflows
Related capabilities
Start with the process your team still has to chase.
The approvals, hand-offs, status checks, and follow-ups that run on email today. Talk to us, and see them run on their own.