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
- Data model
The tables behind Workflow Automation Engine
Workflow Automation Engine ships with 15 tables, grouped here by the feature that uses them. Every record your team works with lives in one of them, and you can add fields and tables in Proto.
- Tables
- 15
- Features
- 6, plus shared settings
- Change it
- Add fields and tables in Proto
How the model is organised
Definitions and ownership
Automation definitions links to Organizations, People and action connectors.
Execution
Automation executions links to automation definitions; operation runs and execution attempts retain the durable trace; operation steps belongs to a run.
Review and correction
Review decisions, evidence documents, state history and follow up actions refer to a definition and the people responsible.
Connections
Source mappings belongs to action connectors. Exchange rates and Users are separate platform records in this data set.
Every table, by feature
- Definitions and ownership4
- Validation and review6
- Durable execution5
- Steps and attempts4
- Connectors and mappings6
- Corrections and evidence7
- Shared and settings2
- Automation definitions
Defines one automated process teams can trigger, showing its steps, status, and latest run outcome.
Linked to Organizations, People, Action connectors - Organizations
Represents a company using the system, keeping its data, location, and settings separate.
- People
Represents a person on the team, used to assign work and track who's responsible for what.
Linked to Organizations - Action connectors
Defines a connection to an outside service, used to control which integrations are active.
Linked to Organizations
- Automation definitions
Defines one automated process teams can trigger, showing its steps, status, and latest run outcome.
Linked to Organizations, People, Action connectors - Review decisions
Captures a reviewer's approval or rejection of an item, along with the reason behind the call.
Linked to Automation definitions, People - Operation runs
Represents one run of an operation, used to track its progress, timing, and outcome.
Linked to Automation definitions - Operation steps
Represents one step in a run, letting teams see progress and spot exactly where it failed.
Linked to Operation runs - State history
Logs each time a record's status changed, so teams can trace how and when it moved along.
Linked to Automation definitions, People - Evidence documents
Holds a supporting document for a review, so teams can back their decisions up with proof.
Linked to Automation definitions, People
- Automation definitions
Defines one automated process teams can trigger, showing its steps, status, and latest run outcome.
Linked to Organizations, People, Action connectors - Automation executions
Represents one run of an automation, showing what happened, the quantities involved, and the result.
Linked to Automation definitions - Operation runs
Represents one run of an operation, used to track its progress, timing, and outcome.
Linked to Automation definitions - Operation steps
Represents one step in a run, letting teams see progress and spot exactly where it failed.
Linked to Operation runs - Execution attempts
Tracks one attempt to run an operation, helping teams see retries, timing, and failures.
Linked to Automation definitions
- Operation steps
Represents one step in a run, letting teams see progress and spot exactly where it failed.
Linked to Operation runs - Operation runs
Represents one run of an operation, used to track its progress, timing, and outcome.
Linked to Automation definitions - Execution attempts
Tracks one attempt to run an operation, helping teams see retries, timing, and failures.
Linked to Automation definitions - Automation definitions
Defines one automated process teams can trigger, showing its steps, status, and latest run outcome.
Linked to Organizations, People, Action connectors
- Action connectors
Defines a connection to an outside service, used to control which integrations are active.
Linked to Organizations - Source mappings
Defines how a field from an outside system maps into this app, keeping integrations consistent.
Linked to Action connectors - Organizations
Represents a company using the system, keeping its data, location, and settings separate.
- Automation definitions
Defines one automated process teams can trigger, showing its steps, status, and latest run outcome.
Linked to Organizations, People, Action connectors - Execution attempts
Tracks one attempt to run an operation, helping teams see retries, timing, and failures.
Linked to Automation definitions - Operation steps
Represents one step in a run, letting teams see progress and spot exactly where it failed.
Linked to Operation runs
- Automation definitions
Defines one automated process teams can trigger, showing its steps, status, and latest run outcome.
Linked to Organizations, People, Action connectors - Follow up actions
Tracks a follow-up task raised after a review, so the team knows who owes what and by when.
Linked to Automation definitions, People - State history
Logs each time a record's status changed, so teams can trace how and when it moved along.
Linked to Automation definitions, People - Evidence documents
Holds a supporting document for a review, so teams can back their decisions up with proof.
Linked to Automation definitions, People - Review decisions
Captures a reviewer's approval or rejection of an item, along with the reason behind the call.
Linked to Automation definitions, People - Operation runs
Represents one run of an operation, used to track its progress, timing, and outcome.
Linked to Automation definitions - Operation steps
Represents one step in a run, letting teams see progress and spot exactly where it failed.
Linked to Operation runs
Keys and references
Use automation definitions.Number to identify the business definition, automation executions.source record id to identify the source request and operation runs.operation key to trace a durable operation. Review decisions.source revision and operation runs.source revision identify the version involved. Operation steps.Run connects the step to its run. Keep provider references and receipt evidence with the attempts and steps that received them.
Migration order
- Bring in Organizations and People, then confirm Users access.
- Set up action connectors and source mappings with their organization and effective context.
- Load automation definitions with the intended owner and connector.
- Bring over review evidence and decisions tied to source revisions.
- Migrate executions, operation runs, steps and attempts in their original relationships.
- Add state history and follow-up work without rewriting earlier outcomes.
Set up Workflow Automation Engine your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.