Inspect a task's recent runs (and why it failed)
List a task's recent runs, with optional drill-down. Use the defaults first (level=summary) to scan cheaply; add status=error to go straight to the failures; and only then fetch one run's per-step detail with run_id + level=step (+ mb_id for a single step). An empty 'executions' list means no runs in the ~24h retention window, NOT that the task is healthy. To scan what SEVERAL runs received, use level=step with ONE field in include (e.g. include=input), max_field_len
200+ apps to connect·Tested & maintained tasks·Human support in English & Spanish
In detail
What it does and what it's for
How it works
How it fits in an automated task
A Botize task pairs a trigger with one or more actions. This piece is one of them.
Pick a trigger
The event that starts the task, from this app or any other.
This action runs
Botize performs it automatically using the data the trigger delivers.
Turn it on and forget it
The task runs on its own from then on. If something's off, tweak it or we'll help you.
Setup
Customization options
Fields you can adjust when using it in your automation.
Output data
Information provided
When executed, this operation delivers the following data, which can be used in the same automatic task.
Tags
- Execution report (JSON) {{result}}
Learn by watching
Video tutorials
Short videos where you watch a real task being built from start to finish.
Need a hand?
Real people behind it
Email us
info@botize.com
Monday to Friday from 7 a.m. to 1 p.m. (Spain).
Message us on Telegram
t.me/botize
Monday to Friday from 7 a.m. to 1 p.m. (Spain).
Come with an idea.
Leave with an automation.
Create your first task in minutes. Do it once and forget about it forever.
Start automating