Connects to the tools you use
Set up connections through ERP.AI and Proto workflows, with every change logged.
- Workflow Automation Engine
- Source system
- Action provider
Workflow Automation Engine organizes automation definitions by organization, owner, revision and connector. An owner prepares a definition; validation records a durable run and step trace, moves the definition to Validated and opens an independent review decision.
Follow-up actions in one list
Reviewer decides whether the validated source revision is approved, returned or rejected.
Every feature works on the same records. Pick one to see the screen your team works in.
Keep every automation revision tied to an owner, organization and connector.
Approval conditions
| Number | Name | Revision | Owner | Definition | |
|---|---|---|---|---|---|
| AD-40835 | New customer account approval | 270 | Sofia Hassan | Customer records connector | |
| AD-98071 | Invoice exception routing | 790 | Priya Desai | Support queue connector | |
| AD-31490 | Weekly inventory reconciliation | 290 | Elliot Park | Purchasing gateway connector | |
| AD-79144 | Contract renewal reminder | 450 | Mira Costa | Identity directory connector | |
| AD-90306 | Employee access request | 120 | Caleb Singh | Contract archive connector |
Trace validation work and keep the review decision on the exact revision.
Approval conditions
| Source | Source revision | Reviewer | Decision | Evidence reference | |
|---|---|---|---|---|---|
| Contract renewal reminder | 500 | Mira Costa | Pending | REVIEW-20261015-11 | |
| Contract renewal reminder | 570 | Sofia Hassan | Pending | REVIEW-20261015-12 | |
| Support escalation handoff | 70 | Leila Moreno | Pending | QA-20261014-21 | |
| Invoice exception routing | 780 | Leila Moreno | Pending | QA-20261014-22 | |
| New customer account approval | 110 | Mira Costa | Pending | AUDIT-20261013-09 |
Connect each execution to its source record, revision and lasting run result.
Automation executions
| Parent | Source record id | Outcome | Started at | Execution result | |
|---|---|---|---|---|---|
| Contract renewal reminder | CUSTOMER-68142 | Pending | 12 Oct | Account approved and recorded | |
| Purchase order acknowledgment | INVOICE-92014 | Accepted | 14 Oct | Invoice sent for finance review | |
| Invoice exception routing | STOCK-RECON-406 | Pending | 29 Oct | Inventory balances reconciled | |
| Invoice exception routing | CONTRACT-18420 | Accepted | 30 Oct | Renewal notice delivered | |
| Invoice exception routing | ACCESS-REQ-7913 | Pending | 30 Oct | Access request completed |
Inspect operation steps, provider receipts and failed attempts.
Execution attempts
| Source | Operation key | Attempt number | Status | Failure reason | Provider reference | |
|---|---|---|---|---|---|---|
| Contract renewal reminder | account-approval-20261015-01 | 270 | Failed | Required account field missing | PROV-771021 | |
| New customer account approval | invoice-route-20261015-02 | 670 | Failed | Invoice status mapping rejected | PROV-771022 | |
| Daily data quality check | inventory-recon-20261014-01 | 830 | Failed | Inventory source did not respond | PROV-771023 | |
| New customer account approval | renewal-notice-20261014-03 | 760 | Failed | Renewal contact address absent | PROV-771024 | |
| Weekly inventory reconciliation | access-request-20261013-04 | 570 | Failed | Manager approval expired | PROV-771025 |
Keep connection ownership and field mappings clear for each automation.
Action connectors
| Name | Code | Organization | Effective from | Effective to | Policy reference | |
|---|---|---|---|---|---|---|
| Ledger account connector | LEDGER-ACCT | Riverstone Purchasing | 29 Oct | 02 Nov | POL-ACCESS-2026-04 | |
| Customer records connector | CUSTOMER-RECORDS | Cedarline Operations | 22 Oct | 29 Oct | POL-FINANCE-2026-02 | |
| Inventory service connector | STOCK-SERVICE | Juniper Office Group | 23 Oct | 31 Oct | POL-STOCK-2026-01 | |
| Contract archive connector | CONTRACT-ARCHIVE | North Vale Supply | 17 Oct | 20 Oct | POL-CONTRACT-2026-03 | |
| Identity directory connector | IDENTITY-DIR | Cedarline Operations | 29 Oct | 03 Nov | POL-IDENTITY-2026-05 |
Retain past revisions and trace the correction that replaces them.
Automation definitions
| Number | Name | Status | Revision | Started at | Execution result | |
|---|---|---|---|---|---|---|
| AD-68498 | New customer account approval | Draft | 240 | 17 Oct | Account approved and recorded | |
| AD-57294 | Invoice exception routing | Validated | 910 | 20 Oct | Invoice sent for finance review | |
| AD-75495 | Weekly inventory reconciliation | Approved | 390 | 23 Oct | Inventory balances reconciled | |
| AD-18889 | Contract renewal reminder | Active | 20 | 25 Oct | Renewal notice delivered | |
| AD-29555 | Employee access request | Retired | 690 | 23 Oct | Access request completed |
Definition to verified result ships ready to use. One step needs a named approval before the work moves on: Decide review (Reviewer).
Record the organization, owner, connector and intended revision.
Run validation and retain the operation and step trace.
A separate Reviewer records a decision on that revision.
Persist the source execution, operation, attempt and step.
Compare the outside receipt with the run result.
Check any compensating action and close its assigned follow-up.
Open any follow-up action to see the roles that work on it, its process stages and its approvals on one page.
Source, Assigned to, Due date and Resolution.
Records linked to this follow-up action.
Each role sees what its permissions allow.
Every status change, in order.
Decide review, with who decides.
New customer account approval · Open
Signed in as Reviewer
| Decision | Approver | |
|---|---|---|
| Decide reviewA separate Reviewer records a decision on that revision. | Reviewer |
Everyone opens Workflow Automation Engine to the work that is theirs. Pick a role to see what it starts with.
Owns organization setup, access and connector configuration.
Prepares definitions and follows their results and corrections.
This is the first screen this role sees.
Automation definitions · Automation Owner
| Number | Name | Revision | Owner | Definition | |
|---|---|---|---|---|---|
| AD-40835 | New customer account approval | 270 | Sofia Hassan | Customer records connector | |
| AD-98071 | Invoice exception routing | 790 | Priya Desai | Support queue connector | |
| AD-31490 | Weekly inventory reconciliation | 290 | Elliot Park | Purchasing gateway connector | |
| AD-79144 | Contract renewal reminder | 450 | Mira Costa | Identity directory connector | |
| AD-90306 | Employee access request | 120 | Caleb Singh | Contract archive connector |
Makes the independent decision on a validated definition revision.
This is the first screen this role sees.
Follow-up actions · Reviewer
Starts reviewed runs and investigates attempts and receipts.
This is the first screen this role sees.
Automation definitions · Operations Operator
Maintains the connection and field mapping context for outside services.
This is the first screen this role sees.
Execution attempts · Integration Steward
| Source | Operation key | Attempt number | Status | Failure reason | Provider reference | |
|---|---|---|---|---|---|---|
| Contract renewal reminder | account-approval-20261015-01 | 270 | Failed | Required account field missing | PROV-771021 | |
| New customer account approval | invoice-route-20261015-02 | 670 | Failed | Invoice status mapping rejected | PROV-771022 | |
| Daily data quality check | inventory-recon-20261014-01 | 830 | Failed | Inventory source did not respond | PROV-771023 | |
| New customer account approval | renewal-notice-20261014-03 | 760 | Failed | Renewal contact address absent | PROV-771024 | |
| Weekly inventory reconciliation | access-request-20261013-04 | 570 | Failed | Manager approval expired | PROV-771025 |
Reads decisions, state changes, evidence and execution traces.
This is the first screen this role sees.
Operation steps · Audit Reader
Answer which revisions were decided, run and corrected.
This quarter
How far records got this quarter
| Stage | Reached | Step | |
|---|---|---|---|
| Open | 47 | ||
| In progress | 14 | 30% | |
| Completed | 2 | 14% | |
| Cancelled | 1 | 50% |
Sample counts per stage
Group definitions by organization and current status to plan review and execution work.
Show each source revision, reviewer, decision, date and reason.
Join a definition to its operation runs, status and result reference.
Group failed attempts by operation key and failure reason.
Follow each operation run to its steps, external receipt and recorded evidence.
Show assigned follow-ups, due dates, status and resolution.
List connector definitions with their source and target field mappings.
Trace a definition's state history with actor, revision, operation key and reason.
See how Workflow Automation Engine fits your kind of team.
Each stage of definition to verified result names the role that acts and the status it records, so a change is never anonymous.
Each stage, the role that acts and the status it records
Ask Proto to prepare traceable review and execution checks.
Set up connections through ERP.AI and Proto workflows, with every change logged.
Every record lives in a table you can see, extend and export. Add fields or whole tables in Proto.
Browse all 15 tablesStart with one team and one process, then add the rest once the basics are running.
Name the organization, Automation Owner, Reviewer, Operations Operator and Integration Steward for the first automation.
Choose a source record identifier, connector, input schema, definition version and field mapping that can be checked against the source system.
Run revision validation, inspect its operation and step trace, then have a separate Reviewer record the decision.
Execute one reviewed revision, compare the run, attempt and step receipt with the action provider, and investigate an uncertain response before any retry.
Create a successor revision through the correction workflow and leave the follow-up open until the compensating outcome is verified.
$0per user
The base account and everyday work in the ERP.AI app are free, for every user.
| Usage | Per $1 |
|---|---|
| Record reads (list, filter, get) | 20,000 |
| Search or aggregate queries | 4,000 |
| Record writes | 4,000 |
| Imported or synced records | 200,000 |
| Workflow runs | 2,000 |
| AI agent runs | 2,000 |
| Scheduled jobs or webhooks | 20,000 |
| File uploads (MB) | 2,000 |
| CSV or PDF exports | 100 |
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.
Start free, then use Proto to change fields, steps and approvals before your team goes live.