Robo Connector – JSON Configuration Guide

Workflow

Workflows define business procedures step-by-step, including logic, actors, inputs, outputs, and execution mode (manual, AI, robot, service).

Each JSON has fields like:

Each step may contain:

Example:

{
  "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"]
    }
  ]
}

Supported Workflow Types

Integration (Coming Soon)

This section will explain how integration JSONs define API hooks, mappers, authentication requirements, and capability declarations.

Regulation (Coming Soon)

Explanation of regulation-based triggers and constraints that adjust workflows, validations, and field mappings.

Risk (Coming Soon)

Structure for identifying and handling risks—manual and AI-assessed—including flags, severity, and escalation procedures.

Opportunity (Coming Soon)

Optional JSONs to define strategic opportunities linked to workflows, such as grants or operational efficiency gains.

Certificate (Coming Soon)

How to define and track certificates, validity dates, and document requirements tied to compliance and workflows.

Tax (Coming Soon)

Support for country-specific tax logic, mapping rules, and workflow linkage for filings, calculations, and reports.

Application (Coming Soon)

Applications are self-contained use cases using flows + documents + functions. This will explain JSON composition for those.