Start free

Trigger.dev connector · Task run reports

Read & reportRead-only source

See how your Trigger.dev tasks run and what they cost.

Bring Trigger.dev task runs and schedules into your reports and AI assistants, with status, compute time and cost for every run.

  • Count failed runs by task each day
  • Track compute cost per task
  • Ask ChatGPT or Claude which tasks cost the most this month
Trigger.devSheetsSheetsData StudioData StudioChatGPTChatGPTClaudeClaude

Start free Explore the data

Updated November 2026

Trigger.dev reportSample data
Task identifierStatusCompute duration (ms)
send-invoice-emailCOMPLETED1,842
sync-crm-contactsFAILED28,410
generate-report-pdfCOMPLETED9,207
Refreshes on your schedule in Google Sheets

Trigger.dev reporting for one environment

One Trigger.dev environment is the data source. Runs follow your report dates; schedules show the environment as it is now.

Task runs

Read runs created in your report dates with task, status, test flag, compute duration, compute and invocation cost, and dates.

Schedules

See every schedule with task, type, cron expression, timezone, active state and next run.

Failures

Count failed and crashed runs by task to find the ones that need attention.

Cost by task

Add compute and invocation cost by task to see where your spend goes.

Report datasets and details

Reports you can build

2 reporting datasets, each with its own fields. Pick one in the app, then choose your columns.

  • Task runs
  • Cron schedules
What each dataset reports
  • Task runs

    Trigger.dev task runs created in the report dates for the environment of the secret key, with task, status, compute duration in milliseconds, compute and invocation cost in cents, and dates. Development runs have no cost or duration.

  • Cron schedules

    Current Trigger.dev schedules with task, schedule type, cron expression, timezone, active state and next run date. Not filtered by report dates.

Metrics and dimensions

16 report fields across 2 datasets.

Search the available fields. Hover or tap a field to see what it means.

Send Trigger.dev data anywhere

Connect Trigger.dev to ChatGPT or Claude for task run questions

Use Datapipe’s MCP access as your Trigger.dev AI integration. Ask about failures, compute time and cost.

Example

Which Trigger.dev tasks cost the most last month?

Add compute and invocation cost for last month’s runs by task, then sort from highest to lowest.

Start with Trigger.dev

What you need

The secret key of one Trigger.dev environment, from API Keys in your project. Each key covers one environment, so add production and staging separately.

What to know

Read-only. Datapipe never triggers, cancels or replays a run. Development runs have no cost or duration. One report reads up to 20,000 runs.

How it works

  1. Create your free account, then choose Trigger.dev in Data sources.

  2. Paste the secret key of the environment you want.

  3. Choose a report and destination: a sheet, Data Studio, ChatGPT or Claude.

Works well with Trigger.dev

Add both to the same project. Each keeps its own report, so you can check them side by side or ask ChatGPT or Claude a question that needs both.

Questions

Datapipe reads task runs in your report dates and the schedules of one environment.

Yes. Add each environment with its own secret key, then combine the reports.

Runs in the development environment have no cost or duration.

No. It only reads runs and schedules.

Free to start. Paid plans add more data sources and refresh faster.

Free and Starter refresh once a day. Pro refreshes every hour. Agency refreshes every 15 minutes on the first 50 data sources.

One for each Trigger.dev account you add to a project. Adding the same account to another project counts again. Reports and destinations do not use extra data sources.

Keep task runs in view.

Start free, add Trigger.dev and bring its runs into the tools you already use.

Start free See setup requirements