Launch Job Run
dagster.launch_job
ActionBusiness appsconnection required
Calls the Dagster API with the connection's credentials.
Launch a job run via GraphQL.
Connection
- Required
- Yes — the node will not save without one
- Auth type
- Bearer token
- Providers
- Dagster
- Secret shape
- a Dagster+ token (optional for OSS), or {"token": "…"}
- Config it needs
- base_url
- Resolved by
- config.connection_id, else node.connection_id
Configuration
4 fields, 2 required. A dotted path is a nested object and name[] an array of objects — the editor renders the same tree.
| Field | Type | Required | Default | Constraints | Example |
|---|---|---|---|---|---|
location Code location name. | string | Yes | — | — | — |
repository Repository (default __repository__). | string | No | — | — | — |
job Name of the job to act on, as Dagster spells it. | string | Yes | — | — | — |
run_config Run config (JSON). | object | No | — | — | — |
Output
One shape.
result
| Field | Type | Example |
|---|---|---|
id Run id. | string | — |
status | string | — |
{
"id": "",
"status": ""
}Related Dagster nodes
See Launch Job Run run in a workflow.
In a technical demo we add the Dagster connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.