Configure workflow inputs

Map data sources, parameters, and triggers to your workflows.

A workflow run starts with an input payload. Inputs can be scheduled, event-driven, or triggered manually.

Inputs

Most workflows combine:

  • Data sources — Files, databases, SFTP, or integrations connected in the Platform.
  • Workspace variables — Shared configuration like thresholds, IDs, and feature flags.
  • Request parameters — Per-run values (date ranges, filters, scenario toggles).

Keep inputs explicit and small. Push large datasets through data sources, not request bodies.

Triggers

Workflows can be triggered by:

  • Manual runs from the Platform UI.
  • Schedules (hourly, daily, weekly) for routine updates.
  • Events from your systems (webhooks, integration syncs).

Workspace variables

Use workspace variables for values that should not be hard-coded in agents or clients (API secrets, IDs, default thresholds).

Example keys:

BOOKINGS_LOOKBACK_DAYS=60
DEFAULT_BUILDING_ID=lhr-hq
ALLOCATION_MAX_CHURN=0.05

Use one workspace per environment so you can separate data, variables, and webhooks cleanly.