Module 7 · Automation
Automation & Integrations
Some steps are better done by software: looking up a record, creating a ticket, sending a notice. Automation will let a procedure take those actions, while a person stays in control of anything consequential.
Example
Where automation fits
This is the intended design. No integrations are live yet, and none will be listed as available until they are built and tested.
- Automation Trigger: new starter added in HR system
- Step Hiring manager confirms equipment needs
- Approval Manager approves the order
- Automation Create the order in the IT systemRetried on failure; logged
- Outcome Starter and manager notified
Capabilities
What’s included
Each item is marked with its real status. “In the demo” works today in the public Studio demo, which runs in your browser with sample data. “Planned” is on the roadmap and not available yet.
Triggers and actions
- In-app notifications when a procedure changesIn the demo
- Event-triggered workflowsPlanned
- APIs and webhooksPlanned
- Email and collaboration integrationsPlanned
- Create and update records in connected systemsPlanned
- Data lookups and calculationsPlanned
Reliability and control
- Human approval for consequential actionsPlanned
- Retry handlingPlanned
- Execution logsPlanned
- Integration health and failure alertsPlanned
In the demo works today in the public Studio demo (runs in your browser, sample data)In development being built now, not yet availablePlanned on the roadmap, not available yet
Related
Works together with
Tell us which systems your procedures depend on.
The Studio demo runs in your browser with sample data. No account needed.