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:

• name: human-readable name of the workflow
• description: purpose of the workflow
• fields: global data used throughout steps
• steps: ordered list of workflow actions

Each step may contain:

• name, action, group, level
• input_fields and output_fields
• Execution properties like optional, required_manual, possible_ai

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

• Manual vs Automated
• Parallel and Conditional Execution
• Decorators (e.g. timeout, businessHoursCheck)

Integration

Wire live products into Robo Connector today using these webhook and Linker API entry points.

• AccordFlow webhookGA — send envelope lifecycle events to POST /api/integration/accordflow with X-Timestamp, X-Signature (HMAC), and optional Idempotency-Key headers. Replay historical deliveries with /api/integration/accordflow/replay. See required headers and JSON payload example in the cross-service guide: AccordFlow webhook payload & headers.
• Linker identity + entitlement upsertPilot — attach users and licenses with POST /linker/v1/identity/upsert using your product-bound X-Robo-Connector-Key. Include email, license_id, product (e.g., ACCORDFLOW), status, tier, and seat counts. Example payload and headers: Identity upsert example.
• Entitlement verificationGA — confirm access before serving requests. Call GET /linker/v1/entitlement/summary?email= to check active/trial states, or POST /linker/v1/license/verify with X-Robo-Connector-Key for license checks. Required headers and sample requests live in: Entitlement summary headers and License verification example.

Regulation (Coming Soon)

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

Risk (Coming Soon)

Risk is already linked to the workflow system, so it can drive more than analytics and notifications.

We are closing gaps in:

• Escalation system: consistent routing, approvals, and handoffs into BPM flows.
• Automation handlers: standardized actions and retries for risk-triggered automations.
• Event capture: stronger signal ingestion, deduplication, and audit-ready timelines.

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.