Dagster

Use Dagster to launch jobs, inspect run status and logs, terminate or delete runs, and reexecute failed runs. List jobs across repositories and start or stop schedules and sensors on the connected instance.

For example, start a job from a workflow, poll its run status, then retrieve logs if it fails. Provide the instance's GraphQL endpoint. Dagster+ requires an API token; authentication for a self-hosted endpoint depends on how you expose it.

Use the block

Connect to a Dagster instance to launch job runs, monitor run status, list available jobs across repositories, terminate or delete runs, reexecute failed runs, fetch run logs, and manage schedules and sensors. API token only required for Dagster+.

Actions

Dagster Launch Run

Launch a job run on a Dagster instance.

Inputs and outputs

Input

Parameter	Type	Required	Description
`host`	string	Yes	Dagster host URL (e.g., https://myorg.dagster.cloud/prod or http://localhost:3000)
`apiKey`	string	No	Dagster+ API token (leave blank for OSS / self-hosted)
`repositoryLocationName`	string	Yes	Repository location (code location) name
`repositoryName`	string	Yes	Repository name within the code location
`jobName`	string	Yes	Name of the job to launch
`runConfigJson`	string	No	Run configuration as a JSON object (optional)
`tags`	string	No	Tags as a JSON array of {key, value} objects (optional)

Output

Parameter	Type	Description
`runId`	string	The globally unique ID of the launched run

Dagster Get Run

Get the status and details of a Dagster run by its ID.

Inputs and outputs

Input

Parameter	Type	Required	Description
`host`	string	Yes	Dagster host URL (e.g., https://myorg.dagster.cloud/prod or http://localhost:3000)
`apiKey`	string	No	Dagster+ API token (leave blank for OSS / self-hosted)
`runId`	string	Yes	The ID of the run to retrieve

Output

Parameter	Type	Description
`runId`	string	Run ID
`jobName`	string	Name of the job this run belongs to
`status`	string	Run status (QUEUED, NOT_STARTED, STARTING, MANAGED, STARTED, SUCCESS, FAILURE, CANCELING, CANCELED)
`mode`	string	Execution mode of the run
`startTime`	number	Run start time as Unix timestamp
`endTime`	number	Run end time as Unix timestamp
`creationTime`	number	Time the run was created as Unix timestamp
`updateTime`	number	Time the run was last updated as Unix timestamp
`parentRunId`	string	ID of the immediate parent run (for re-executions)
`rootRunId`	string	ID of the root run in the re-execution group
`canTerminate`	boolean	Whether the run can currently be terminated
`assetSelection`	json	Asset keys targeted by the run, as slash-joined strings
`runConfigYaml`	string	Run configuration as YAML
`tags`	json	Run tags as array of {key, value} objects

Dagster Get Run Logs

Fetch execution event logs for a Dagster run.

Inputs and outputs

Input

Parameter	Type	Required	Description
`host`	string	Yes	Dagster host URL (e.g., https://myorg.dagster.cloud/prod or http://localhost:3001)
`apiKey`	string	No	Dagster+ API token (leave blank for OSS / self-hosted)
`runId`	string	Yes	The ID of the run to fetch logs for
`afterCursor`	string	No	Cursor for paginating through log events (from a previous response)
`limit`	number	No	Maximum number of log events to return

Output

Parameter	Type	Description
`events`	json	Array of log events (type, message, timestamp, level, stepKey, eventType)
↳ `type`	string	GraphQL typename of the event
↳ `message`	string	Human-readable log message
↳ `timestamp`	string	Event timestamp as a Unix epoch string
↳ `level`	string	Log level (DEBUG, INFO, WARNING, ERROR, CRITICAL)
↳ `stepKey`	string	Step key, if the event is step-scoped
↳ `eventType`	string	Dagster event type enum value
`cursor`	string	Cursor for fetching the next page of log events
`hasMore`	boolean	Whether more log events are available beyond this page

Dagster List Runs

List Dagster runs with optional filters by job name, status, and creation-time range, plus cursor pagination.

Inputs and outputs

Input

Parameter	Type	Required	Description
`host`	string	Yes	Dagster host URL (e.g., https://myorg.dagster.cloud/prod or http://localhost:3001)
`apiKey`	string	No	Dagster+ API token (leave blank for OSS / self-hosted)
`jobName`	string	No	Filter runs by job name (optional)
`statuses`	string	No	Comma-separated run statuses to filter by, e.g. "SUCCESS,FAILURE" (optional)
`createdAfter`	number	No	Only return runs created at or after this Unix timestamp in seconds (optional)
`createdBefore`	number	No	Only return runs created at or before this Unix timestamp in seconds (optional)
`cursor`	string	No	Run ID to page after, from a previous response cursor (optional)
`limit`	number	No	Maximum number of runs to return (default 20)

Output

Parameter	Type	Description
`runs`	json	Array of runs
↳ `runId`	string	Run ID
↳ `jobName`	string	Job name
↳ `status`	string	Run status
↳ `tags`	json	Run tags as array of {key, value} objects
↳ `startTime`	number	Start time as Unix timestamp
↳ `endTime`	number	End time as Unix timestamp
`cursor`	string	Run ID of the last returned run — pass as cursor to fetch the next page
`hasMore`	boolean	Whether more runs are likely available beyond this page

Dagster List Jobs

List all jobs across repositories in a Dagster instance.

Inputs and outputs

Input

Parameter	Type	Required	Description
`host`	string	Yes	Dagster host URL (e.g., https://myorg.dagster.cloud/prod or http://localhost:3001)
`apiKey`	string	No	Dagster+ API token (leave blank for OSS / self-hosted)

Output

Parameter	Type	Description
`jobs`	json	Array of jobs with name and repositoryName
↳ `name`	string	Job name
↳ `repositoryName`	string	Repository name

Dagster Reexecute Run

Reexecute an existing Dagster run, optionally resuming only from failed steps.

Inputs and outputs

Input

Parameter	Type	Required	Description
`host`	string	Yes	Dagster host URL (e.g., https://myorg.dagster.cloud/prod or http://localhost:3001)
`apiKey`	string	No	Dagster+ API token (leave blank for OSS / self-hosted)
`parentRunId`	string	Yes	The ID of the run to reexecute
`strategy`	string	Yes	Reexecution strategy: ALL_STEPS reruns everything, FROM_FAILURE resumes from failed steps, FROM_ASSET_FAILURE resumes from failed assets

Output

Parameter	Type	Description
`runId`	string	The ID of the newly launched reexecution run

Dagster Terminate Run

Terminate an in-progress Dagster run.

Inputs and outputs

Input

Parameter	Type	Required	Description
`host`	string	Yes	Dagster host URL (e.g., https://myorg.dagster.cloud/prod or http://localhost:3001)
`apiKey`	string	No	Dagster+ API token (leave blank for OSS / self-hosted)
`runId`	string	Yes	The ID of the run to terminate

Output

Parameter	Type	Description
`success`	boolean	Whether the run was successfully terminated
`runId`	string	The ID of the terminated run
`message`	string	Error or status message if termination failed

Dagster Delete Run

Permanently delete a Dagster run record.

Inputs and outputs

Input

Parameter	Type	Required	Description
`host`	string	Yes	Dagster host URL (e.g., https://myorg.dagster.cloud/prod or http://localhost:3001)
`apiKey`	string	No	Dagster+ API token (leave blank for OSS / self-hosted)
`runId`	string	Yes	The ID of the run to delete

Output

Parameter	Type	Description
`runId`	string	The ID of the deleted run

Dagster List Schedules

List all schedules in a Dagster repository, optionally filtered by status.

Inputs and outputs

Input

Parameter	Type	Required	Description
`host`	string	Yes	Dagster host URL (e.g., https://myorg.dagster.cloud/prod or http://localhost:3001)
`apiKey`	string	No	Dagster+ API token (leave blank for OSS / self-hosted)
`repositoryLocationName`	string	Yes	Repository location (code location) name
`repositoryName`	string	Yes	Repository name within the code location
`scheduleStatus`	string	No	Filter schedules by status: RUNNING or STOPPED (omit to return all)

Output

Parameter	Type	Description
`schedules`	json	Array of schedules (name, cronSchedule, jobName, status, id, description, executionTimezone)
↳ `name`	string	Schedule name
↳ `cronSchedule`	string	Cron expression for the schedule
↳ `jobName`	string	Job the schedule targets
↳ `status`	string	Schedule status: RUNNING or STOPPED
↳ `id`	string	Instigator state ID — use this to start or stop the schedule
↳ `description`	string	Human-readable schedule description
↳ `executionTimezone`	string	Timezone for cron evaluation

Dagster Start Schedule

Enable (start) a schedule in a Dagster repository.

Inputs and outputs

Input

Parameter	Type	Required	Description
`host`	string	Yes	Dagster host URL (e.g., https://myorg.dagster.cloud/prod or http://localhost:3001)
`apiKey`	string	No	Dagster+ API token (leave blank for OSS / self-hosted)
`repositoryLocationName`	string	Yes	Repository location (code location) name
`repositoryName`	string	Yes	Repository name within the code location
`scheduleName`	string	Yes	Name of the schedule to start

Output

Parameter	Type	Description
`id`	string	Instigator state ID of the schedule
`status`	string	Updated schedule status (RUNNING or STOPPED)

Dagster Stop Schedule

Disable (stop) a running schedule in Dagster.

Inputs and outputs

Input

Parameter	Type	Required	Description
`host`	string	Yes	Dagster host URL (e.g., https://myorg.dagster.cloud/prod or http://localhost:3001)
`apiKey`	string	No	Dagster+ API token (leave blank for OSS / self-hosted)
`instigationStateId`	string	Yes	InstigationState ID of the schedule to stop — available from dagster_list_schedules output

Output

Parameter	Type	Description
`id`	string	Instigator state ID of the schedule
`status`	string	Updated schedule status (RUNNING or STOPPED)

Dagster List Sensors

List all sensors in a Dagster repository, optionally filtered by status.

Inputs and outputs

Input

Parameter	Type	Required	Description
`host`	string	Yes	Dagster host URL (e.g., https://myorg.dagster.cloud/prod or http://localhost:3001)
`apiKey`	string	No	Dagster+ API token (leave blank for OSS / self-hosted)
`repositoryLocationName`	string	Yes	Repository location (code location) name
`repositoryName`	string	Yes	Repository name within the code location
`sensorStatus`	string	No	Filter sensors by status: RUNNING or STOPPED (omit to return all)

Output

Parameter	Type	Description
`sensors`	json	Array of sensors (name, sensorType, status, id, description)
↳ `name`	string	Sensor name
↳ `sensorType`	string	Sensor type (ASSET, AUTO_MATERIALIZE, FRESHNESS_POLICY, MULTI_ASSET, RUN_STATUS, STANDARD, UNKNOWN)
↳ `status`	string	Sensor status: RUNNING or STOPPED
↳ `id`	string	Instigator state ID — use this to start or stop the sensor
↳ `description`	string	Human-readable sensor description

Dagster Start Sensor

Enable (start) a sensor in a Dagster repository.

Inputs and outputs

Input

Parameter	Type	Required	Description
`host`	string	Yes	Dagster host URL (e.g., https://myorg.dagster.cloud/prod or http://localhost:3001)
`apiKey`	string	No	Dagster+ API token (leave blank for OSS / self-hosted)
`repositoryLocationName`	string	Yes	Repository location (code location) name
`repositoryName`	string	Yes	Repository name within the code location
`sensorName`	string	Yes	Name of the sensor to start

Output

Parameter	Type	Description
`id`	string	Instigator state ID of the sensor
`status`	string	Updated sensor status (RUNNING or STOPPED)

Dagster Stop Sensor

Disable (stop) a running sensor in Dagster.

Inputs and outputs

Input

Parameter	Type	Required	Description
`host`	string	Yes	Dagster host URL (e.g., https://myorg.dagster.cloud/prod or http://localhost:3001)
`apiKey`	string	No	Dagster+ API token (leave blank for OSS / self-hosted)
`instigationStateId`	string	Yes	InstigationState ID of the sensor to stop — available from dagster_list_sensors output

Output

Parameter	Type	Description
`id`	string	Instigator state ID of the sensor
`status`	string	Updated sensor status (RUNNING or STOPPED)

Dagster List Assets

List assets tracked by a Dagster instance, optionally filtered by key prefix.

Inputs and outputs

Input

Parameter	Type	Required	Description
`host`	string	Yes	Dagster host URL (e.g., https://myorg.dagster.cloud/prod or http://localhost:3001)
`apiKey`	string	No	Dagster+ API token (leave blank for OSS / self-hosted)
`prefix`	string	No	Slash-delimited asset key prefix to filter by, e.g. "raw" or "raw/events" (optional)
`cursor`	string	No	Asset key cursor from a previous response, for pagination (optional)
`limit`	number	No	Maximum number of assets to return per page (default 100)

Output

Parameter	Type	Description
`assets`	json	Array of assets (assetKey, path)
↳ `assetKey`	string	Slash-joined asset key
↳ `path`	json	Asset key path segments
`cursor`	string	Cursor to pass on the next call to fetch more assets
`hasMore`	boolean	Whether more assets are likely available beyond this page

Dagster Get Asset

Get an asset definition and its latest materialization by asset key.

Inputs and outputs

Input

Parameter	Type	Required	Description
`host`	string	Yes	Dagster host URL (e.g., https://myorg.dagster.cloud/prod or http://localhost:3001)
`apiKey`	string	No	Dagster+ API token (leave blank for OSS / self-hosted)
`assetKey`	string	Yes	Slash-delimited asset key, e.g. "my_asset" or "raw/events"

Output

Parameter	Type	Description
`assetKey`	string	Slash-joined asset key
`path`	json	Asset key path segments
`groupName`	string	Asset group the definition belongs to
`description`	string	Asset description
`jobNames`	json	Names of jobs that can materialize this asset
`computeKind`	string	Compute kind tag (e.g., python, dbt, spark)
`isPartitioned`	boolean	Whether the asset is partitioned
`latestMaterialization`	json	Most recent materialization (runId, timestamp, partition, stepKey)
↳ `runId`	string	Run that produced the materialization
↳ `timestamp`	string	Materialization timestamp (epoch ms string)
↳ `partition`	string	Partition key, if partitioned
↳ `stepKey`	string	Step key that emitted it

Dagster Materialize Assets

Materialize selected assets by launching their asset job with an asset selection.

Inputs and outputs

Input

Parameter	Type	Required	Description
`host`	string	Yes	Dagster host URL (e.g., https://myorg.dagster.cloud/prod or http://localhost:3001)
`apiKey`	string	No	Dagster+ API token (leave blank for OSS / self-hosted)
`repositoryLocationName`	string	Yes	Repository location (code location) name
`repositoryName`	string	Yes	Repository name within the code location
`jobName`	string	Yes	Asset job that contains the assets, e.g. "__ASSET_JOB" or a named asset job
`assetSelection`	string	Yes	Comma- or newline-separated asset keys to materialize, each slash-delimited (e.g. "raw/events, summary")
`tags`	string	No	Tags as a JSON array of {key, value} objects (optional)

Output

Parameter	Type	Description
`runId`	string	The globally unique ID of the launched materialization run

Dagster Report Asset Materialization

Report an external (runless) materialization or observation for an asset.

Inputs and outputs

Input

Parameter	Type	Required	Description
`host`	string	Yes	Dagster host URL (e.g., https://myorg.dagster.cloud/prod or http://localhost:3001)
`apiKey`	string	No	Dagster+ API token (leave blank for OSS / self-hosted)
`assetKey`	string	Yes	Slash-delimited asset key to report against, e.g. "my_asset" or "raw/events"
`eventType`	string	No	Event type to report: ASSET_MATERIALIZATION (default) or ASSET_OBSERVATION
`partitionKeys`	string	No	Comma-separated partition keys to report against (optional)
`description`	string	No	Human-readable description for the reported event (optional)

Output

Parameter	Type	Description
`success`	boolean	Whether the event was reported successfully
`assetKey`	string	Slash-joined asset key the event was reported against

Dagster Wipe Asset

DESTRUCTIVE: permanently wipes ALL materialization history (every partition) for an asset. This cannot be undone.

Inputs and outputs

Input

Parameter	Type	Required	Description
`host`	string	Yes	Dagster host URL (e.g., https://myorg.dagster.cloud/prod or http://localhost:3001)
`apiKey`	string	No	Dagster+ API token (leave blank for OSS / self-hosted)
`assetKey`	string	Yes	Slash-delimited asset key to wipe, e.g. "my_asset" or "raw/events"

Output

Parameter	Type	Description
`success`	boolean	Whether the asset was wiped successfully
`assetKey`	string	Slash-joined asset key that was wiped