dbt Cloud

• Run startedRuns when a dbt Cloud job run starts, from a schedule, the API, a pull request or someone clicking Run now.
• Run finishedRuns when a dbt Cloud job run ends, whether it succeeded, failed or was cancelled. Read 'status' to see which.
• Run succeededRuns when a dbt Cloud job run finishes successfully, such as to refresh a dashboard once the models are built.
• Run failedRuns when a dbt Cloud job run fails with an error, such as to alert the team or open a ticket with the error message.
• New jobRuns when a job is created in your dbt Cloud account. Jobs already there when the workflow is turned on don't start it.

• Get accountGet the connected dbt account: its name, plan and how many runs it can run at once.
• List projectsList the account's dbt projects by name, with their warehouse connection and repository ids.
• Get projectGet one dbt project with its warehouse connection and git repository.
• List environmentsList a project's environments: the deployment environments jobs run in and the development environment of the IDE.
• Get environmentGet one environment: its kind, dbt version, custom branch and the connection and credentials it uses.
• List jobsList the account's jobs by name, with their commands, schedule and environment.
• Get jobGet one job: its commands, schedule, settings and environment.
• Create jobCreate a deploy job in an environment that runs your dbt commands, on a schedule or only when started.
• Update jobChange a job's name, commands, schedule or settings. Only the fields you fill in change.
• Delete jobDelete a job. Its past runs stay in the run history.
• Run jobStart a run of a job, optionally on another branch or with other commands. It returns once the run is queued; use 'Wait for run to finish' to wait for it.
• Rerun job from failureRerun a job's most recent failed run from the step that failed, skipping what already succeeded.
• List runsList runs, newest first, for a job, project or environment, and by status, such as every failed run.
• Get runGet a run's status, times, branch and each step with its logs.
• Wait for run to finishWait until a run has succeeded, failed or been cancelled, then return it. The workflow pauses meanwhile, checking every minute.
• Cancel runCancel a run that is queued or running.
• Retry runRerun a failed run from the step that failed, as a new run.
• List run artifactsList the files a run saved, such as manifest.json and run_results.json.
• Get run artifactGet a file a run saved, such as run_results.json with each model's result and timing. A JSON file comes back as data.
• Get latest job artifactGet a file from a job's most recent run, such as its manifest.json, without knowing the run's id.
• Get run stepGet one step of a run, such as dbt build, with its status, timing and logs. Step ids are in a run's run_steps.
• List usersList the people in the account with their emails, by name or licence.
• List connectionsList the account's data warehouse connections, such as Snowflake or BigQuery, and how many environments use each.
• List repositoriesList the git repositories the account's projects are connected to.
• List webhooksList the account's webhooks: where each sends run events, which events, and whether its last delivery worked.

No actions match that.