These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Workflow Automation Engine
- Who it's for
- Service operations
Service operations
A service operations team often receives requests from another system and needs a dependable way to act on them. Use a definition for the instructions, a source record identifier for the incoming request and a durable run for the action taken. The review decision belongs to the exact revision the team intends to use.
How Workflow Automation Engine is set up for you
Prepare a service action
The Automation Owner records the connector, trigger information, input schema and retry policy for the request type. A named Reviewer examines the validation trace before a live run.
Watch the action
The Operations Operator follows the execution, run, step and attempt records. A provider receipt helps the team confirm what happened outside the app.
Handle an uncertain result
If a timeout occurs, inspect the provider reference and step receipt before repeating the request. Keep the operation key stable enough to find the earlier attempt.
Correct a bad outcome
Retain the earlier revision and its run, then use a correction run, compensating step and assigned follow-up to verify the result.
A service operations team often receives requests from another system and needs a dependable way to act on them. Use a definition for the instructions, a source record identifier for the incoming request and a durable run for the action taken. The review decision belongs to the exact revision the team intends to use.
Choose one request type with a known source identifier and a provider response that staff can inspect. Set up its organization and connector, then validate one revision. Rehearse an approval and a return decision with different people. Run one accepted source request and compare its local result with the outside receipt. Finally, test a failed attempt and a correction. The goal is a trace your team can explain from the incoming request through the final verified outcome.
[Plan the pilot](/workflow-automation-engine/implementation) and [inspect durable execution](/workflow-automation-engine/processes/durable-execution).
Features to start with
Roles on the team
- Automation Owner
- Prepares definitions and follows their results and corrections.
- Reviewer
- Makes the independent decision on a validated definition revision.
- Operations Operator
- Starts reviewed runs and investigates attempts and receipts.
- Integration Steward
- Maintains the connection and field mapping context for outside services.
- Audit Reader
- Reads decisions, state changes, evidence and execution traces.
Set up Workflow Automation Engine your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.