Automated CrewAI Execution and Cost Log
Every night, WebRun opens CrewAI, lists the day's executions across your deployed crews with their status, duration, tokens used and estimated cost, appends one row per run to an Airtable log, and writes a short trend note in Notion comparing today against the past week.
How do I track what my CrewAI crews ran and what it cost?
WebRun logs your CrewAI usage every night. It reads each deployed crew's executions for the day with their status, duration, tokens used and estimated cost, appends one row per run to Airtable, and writes a Notion note comparing every crew against its seven day average, so cost becomes a trend.
- Every crew run is on record, not just the ones that failed
- Token spend and estimated cost build into a trend you can chart
- A crew that suddenly runs twice as often is visible the same night
Built for automation owners · AI engineering teams · platform teams · ops leads
What does WebRun do on every run?
The exact actions WebRun takes, in order - in plain language, so you can adjust anything.
-
WebRun signs in and gets to work
Opens
app.crewai.comin a real browser with your saved login - no setup, no API keys. -
1
CrewAI - list the day's executions
crewai.com
WebRun opens CrewAI to list the day's executions. - Open CrewAI and go through each deployed crew in turn
- List every execution started since the last run, successes and failures alike
- Record the crew name, start time, duration, execution status, tokens used and estimated cost for each
- Skip executions already written to the log so nothing is counted twice
Done when Every execution from the past 24 hours is captured with its crew, status, duration, tokens and estimated cost.
-
2
Airtable - append one row per run
airtable.com
WebRun opens Airtable to append one row per run. - Append one row per execution to your CrewAI usage table
- Fill the date, crew, status, duration, tokens used and estimated cost columns
- Roll the day up into a summary row per crew so totals are easy to chart later
Done when Airtable holds a row for every execution today plus a per crew daily total.
-
3
Notion - write the trend note
notion.so
WebRun opens Notion to write the trend note. - Write tonight's note into your Notion automation-log page
- Give the day's totals: executions run, how many succeeded, total duration and estimated cost
- Compare each crew against its seven day average and call out anything that ran far more or far less than usual
- Link the Airtable log for the full row level detail
Done when Notion has a dated note with today's totals and how each crew compares to its recent average.
How is each run configured?
Secure by default
Connect once, stays signed in
WebRun signs in once and keeps each session in a persistent environment, so every run picks up right where it left off.
Every action is checked against this policy before it runs.
Questions, answered
Will it start, stop or change any of my crews?
No. WebRun only reads the execution history in CrewAI. It never kicks off a run, cancels one, or edits a crew or its deployment, so the log is built entirely from what already happened.
Does it log successful runs too, or only failures?
Every execution is logged, successes included. That is the point of the nightly record: usage and cost only make sense as a trend, and a failure-only alert never shows you how much a healthy crew is consuming.
What if the same execution appears on two nights?
Each run is matched against what is already in the Airtable log before anything is written, so an execution that spans midnight or a night that runs twice will not create duplicate rows or double counted costs.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.