Questions, answered

Click Get started, then use Proto to configure Workflow Automation Engine for your business. Pilot one definition, one reviewed revision and a source request whose outside result your team can verify.

It ties the automation to an organization, owner and connector. It also keeps trigger information, input schema, retry policy, version and current status.

A named Reviewer records the decision on the source revision, with a reason and evidence reference. Agree who can review each organization’s work when setting up access.

Open the execution and its linked operation run. Check the attempt and step records for timing, result references and outside receipts.

Check the operation key, provider reference and any step receipt with the outside service before deciding whether another attempt is safe.

The correction workflow retains the earlier revision, records a correction run and compensating step, creates a successor and opens a verification follow-up.

Action connectors and field mappings identify the service context for a definition. Configure each provider’s account and credentials with its owner.

State history records changes against a definition with actor, revision, operation key and reason. Decisions, evidence documents, runs and follow-ups retain their own records.

Validate a revision, record both an approved and returned review, run one known source request, investigate a failed attempt and verify a correction against the outside service.