Workflows define business procedures step-by-step, including logic, actors, inputs, outputs, and execution mode (manual, AI, robot, service).
Each JSON has fields like:
name
: human-readable name of the workflowdescription
: purpose of the workflowfields
: global data used throughout stepssteps
: ordered list of workflow actionsEach step may contain:
name
, action
, group
, level
input_fields
and output_fields
optional
, required_manual
, possible_ai
{
"name": "Transition to Euro",
"description": "Migrate accounting from PLN to EUR.",
"fields": ["current_account_map", "euro_account_map", "transition_date"],
"steps": [
{
"name": "Analyze Current Structures",
"action": "Review Accounts",
"type": "manual",
"outputs": ["current_account_map.json"]
}
]
}
timeout
, businessHoursCheck
)This section will explain how integration JSONs define API hooks, mappers, authentication requirements, and capability declarations.
Explanation of regulation-based triggers and constraints that adjust workflows, validations, and field mappings.
Structure for identifying and handling risks—manual and AI-assessed—including flags, severity, and escalation procedures.
Optional JSONs to define strategic opportunities linked to workflows, such as grants or operational efficiency gains.
How to define and track certificates, validity dates, and document requirements tied to compliance and workflows.
Support for country-specific tax logic, mapping rules, and workflow linkage for filings, calculations, and reports.
Applications are self-contained use cases using flows + documents + functions. This will explain JSON composition for those.