Orchestrator

Create job flows, run them with explicit input, and inspect execution state, task logs, sharing, and schedules.

Open Orchestrator

Create and run a job flow

  1. Choose Create Job Flow or start from Templates. Name the flow and configure its states and connected resources.
  2. Review each task’s parameters, credentials, and error path before saving.
  3. Start an execution with the intended input. Open Executions to inspect the run and its logs.
  4. Configure a schedule or webhook only after the manual execution produces the expected result.

Definitions and triggers

Job flows use a definition containing StartAt and States. Execution requests identify the saved flow with stateMachineId. Supported task behavior follows the selected state and its configured action.

For workflow-specific webhooks, copy the endpoint generated by that saved workflow. Cloud-storage ingestion webhooks and workflow triggers serve different purposes; verify the selected subscription and event filter.

Choose the pipeline tool

Use Platform Data Pipelines for repository-based Python, PySpark, notebook, and SQL DAGs. Use Orchestrator for the state-machine workflow you configure in its designer.

API endpoints

Use your Genorbex deployment’s origin followed by the path below. Replace IDs with resources accessible to your account. Authentication and permissions are checked by each endpoint.

GET /api/orchestrator/job-flows

Lists job flows the user can view.

Authentication: Genorbex account token and service/resource access; API-key support follows the endpoint’s authentication guard.

POST /api/orchestrator/job-flows

Creates a job flow with a state-machine definition.

Authentication: Genorbex account token and service/resource access; API-key support follows the endpoint’s authentication guard.

Example JSON body

{
  "name": "Example flow",
  "definition": {
    "StartAt": "Complete",
    "States": {
      "Complete": {
        "Type": "Succeed"
      }
    }
  }
}

POST /api/orchestrator/executions

Starts a saved flow for an authorized user.

Authentication: Genorbex account token and service/resource access; API-key support follows the endpoint’s authentication guard.

Example JSON body

{
  "stateMachineId": "YOUR_JOB_FLOW_ID",
  "input": {}
}

GET /api/orchestrator/executions

Lists execution records for the permitted scope.

Authentication: Genorbex account token and service/resource access; API-key support follows the endpoint’s authentication guard.

Need help with your setup? Visit the Help Center or contact Genorbex.