All integrationsCloud Computing

Prefect

Run your Prefect pipelines: run deployments with parameters, follow and wait for flow runs, cancel, retry and resume them, read their logs, pause deployments, set Variables, and start a workflow when a flow run fails, completes or starts late.

actions
15
triggers
3

Triggers

Start a workflow when something happens in Prefect.

  • Flow run failedRuns when a flow run fails or crashes, of every deployment or the one you choose, with the error. A run retried and failing again starts it again. Runs that failed before the workflow was turned on don't.
  • Flow run completedRuns when a flow run completes, of every deployment or the one you choose. Runs that completed before the workflow was turned on don't start it.
  • Flow run lateRuns when Prefect marks a flow run Late: it was due to start and no worker has started it, such as when the worker is down or the work pool is paused.

Actions

Steps a workflow can run in Prefect.

  • Run deploymentStart a run of a deployment with the parameters you give, now or at a set time, as Prefect's Run button does. It doesn't wait for the run: follow it with Wait for flow run or Get flow run.
  • Get flow runGet a flow run's state, parameters and times, with the message its state carries, such as the error it failed on.
  • Wait for flow runWait until a flow run finishes (completes, fails, crashes or is cancelled) or pauses for someone, up to 15 minutes, then get it. A run still going when the wait is up carries on in Prefect.
  • List flow runsList recent flow runs, the latest first, of every deployment or one, by state, tag and since when. Runs scheduled for later are listed only when you pick the Scheduled state.
  • Cancel flow runCancel a flow run, as Prefect's Cancel button does: one waiting to start is cancelled at once, and the worker stops one that's running. A run that has finished is left as it is.
  • Retry flow runRun a finished flow run of a deployment again with the same parameters, as Prefect's Retry button does, such as after fixing what made it fail.
  • Resume flow runResume a flow run that paused to wait for someone, such as for an approval. A run that isn't paused is left as it is.
  • Get flow run logsGet a flow run's log, its last lines oldest first, with the last error it logged.
  • List deploymentsList deployments by name, with whether each is paused, its schedules, its default parameters and its work pool.
  • Pause deploymentPause a deployment, so its schedules make no runs until it's resumed. Runs going now carry on, and it can still be run by hand.
  • Resume deploymentResume a paused deployment, so its schedules make runs again.
  • List work poolsList work pools, with whether a worker is polling each (Ready) and whether it's paused.
  • Get VariableGet a Prefect Variable's value.
  • Set VariableSet a Prefect Variable that flows read, such as a date to load from or a list of recipients, making it if there's none.
  • Delete VariableDelete a Prefect Variable. One that isn't there is left as it is.

Automate Prefect with Lodol.

Connect Prefect, then hand Lodol the job in Slack, Claude or ChatGPT.

Free plan, no credit card