Knowledgebase›Starter Guide

Starter Guide

This guide gives new users a single path to get from raw JSON telemetry to a populated process datasheet inside Toro Pulse.

Current scopeThis guide reflects the current automation-first Toro Pulse build. It focuses on telemetry-backed process datasheets, governed insights, ROI calculations, and manual JSON-assisted setup.

1. What a process datasheet represents

A process datasheet is the operational record for a process inside Toro Pulse. It combines process identity, ROI context, infrastructure signals, KPI values, governance metadata, and AI-oriented analysis inputs into a single page.

2. Primary ingestion path: POST telemetry to the API

Telemetry payloads should be submitted to the ingest API using JSON over HTTPS with a tenant-scoped ingestion API key. Retrieve the current key from Settings → API Access in Toro Pulse.

POST /api/v1/ingest
Content-Type: application/json
Accept: application/json

For implementations that use the telemetry-specific route, also validate against the environment-specific endpoint map in the API reference.

3. Minimal example payload

{
  "Telemetry": {
    "Company": "Contoso Health",
    "Process": "Invoice Intake",
    "SessionID": "9a8dbe0a-1b2c-4d5e-9111-1b3f37d99001",
    "TimestampUtc": "2026-04-01T15:30:00Z",
    "Status": "Completed",
    "TransactionsProcessed": 120,
    "TransactionsFailed": 2,
    "ResourceMachine": "RPA-VM-01"
  }
}

4. Sample template files

5. Manual process datasheet creation

  1. Open the hub workspace main page.
  2. Select the action to create a new process datasheet.
  3. Enter the core process metadata such as process name, owner, department, business area, and any required ROI assumptions.
  4. Save the datasheet so that the process record exists before any optional manual JSON import testing.

6. Drag-and-drop JSON payloads

For manual validation and testing, Toro Pulse supports drag-and-drop JSON ingestion on the datasheet workflow. This is useful when implementation teams want to test sample telemetry without wiring a live automation emitter yet.

  1. Navigate to the relevant process datasheet or import area.
  2. Drag one or more JSON files into the drop zone.
  3. Toro Pulse parses each file and flags invalid JSON before any aggregate rendering occurs.
  4. Valid payloads are added to the working set and can be reviewed before final submission.

7. Where to go next