Start free
Read & reportRead-only source

See your Trigger.dev numbers in Cloudflare R2.

Review Trigger.dev task run statuses, durations, costs and cron schedules in a read-only data source.

  • Traffic, sources and conversions in a sheet or dashboard, refreshed for you
  • A weekly traffic report nobody has to rebuild
  • Ask ChatGPT or Claude what changed, using live Trigger.dev numbers
Trigger.devCloudflare R2Cloudflare R2

Start free Connect Trigger.dev

Updated November 2026

Trigger.dev reportSample data
Task identifierStatusCompute duration (ms)
sync-invoicesCOMPLETED1,240
640Pending640
210Refunded210
Refreshes on your schedule in Cloudflare R2

Who uses Datapipe with Trigger.dev

Marketers

See which channels and pages bring visitors who convert.

Founders

Get a weekly traffic summary without opening another dashboard.

Agencies

Send each client the same clean traffic report every month.

What you can do with Trigger.dev

Read-only source

Datapipe reads Trigger.dev data for reports. It never changes anything in Trigger.dev.

Full read details

Tasks and schedules are never triggered or modified.

Examples for your team

Read & report

Track background job duration, status and cost

Combine task run durations, failure rates and cron schedules in one report.

  1. Scheduled refresh
  2. Latest Trigger.dev data
  3. Updated report

Before you connect

What you need

An API key or token from your Trigger.dev account.

Read-only

Read access only. Datapipe never changes anything in Trigger.dev.

Limits and exclusions

Read-only. Runs are never triggered or cancelled, each key covers one environment, and development runs have no cost or duration.

Full details and limits

Task runs created in the report dates and current schedules for one Trigger.dev project environment.

Read-only reporting access using your Trigger.dev secret key. Tasks and schedules are never modified.

Read-only. Runs are never triggered or cancelled, each key covers one environment, and development runs have no cost or duration.

Reports you can build

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

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.

Hover or tap a field to see what it means. Custom fields from your own account appear after you connect.

Send Trigger.dev data anywhere

Ask AI about your data

Claude or ChatGPT can read the same numbers. You ask in a normal sentence, and the answer stays with your report.

Summarize Trigger.dev task runs, durations, costs, and active cron schedules.

12,840 task runs completed with a 99.4% success rate and 1,120 ms average duration.

Better than exporting by hand

Start from a goal

How it works

  1. Create a project and choose Trigger.dev in Data sources.

  2. Pick where it goes. This one sends the numbers to Cloudflare R2.

  3. Pick where it goes. Choose task runs or schedules and a destination.

Sample report

Trigger.dev reportSample data
Task identifierStatusCompute duration (ms)Compute cost (cents)Invocation cost (cents)TaskCron expressionTimezone
sync-invoicesCOMPLETED1,240$80.00$80.001,2401,2401,240
640Pending640$125.50$125.50640640640
210Refunded210$42.00$42.00210210210

Sample numbers, so you can see the shape. Your report uses your accounts.

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

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.

No. Name a project, add a data source, then choose a report and destination.

OAuth means you sign in with the service and grant access, without pasting an API key. Datapipe works with multiple partners to provide that sign-in. Some partners already provide it. Some integrations are API-only at present, so you paste a key or token. OAuth is coming soon for some. Some partners do not provide OAuth at all. The setup steps on each integration page say how that source connects. Signing in is only how the connection is made. It is not permission to change records. Where a source supports changes, those writes stay off until the workspace owner turns specific actions on and approves each one. We do not promise OAuth on every source, and we do not share dates.

This integration is read-only in Datapipe. You can report on Trigger.dev, send the reports to your destinations and ask an AI assistant about them. Datapipe never changes anything in Trigger.dev. Read-only reporting access using your Trigger.dev secret key. Tasks and schedules are never modified.

This page lists 16 report fields across 2 datasets. You pick the columns when you build the report.

Task runs created in the report dates and current schedules for one Trigger.dev project environment. Account permissions and the records available from the provider determine which rows can be read.

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.

Yes. The same numbers can go to a sheet, a chart, a warehouse, or an assistant.

Try Trigger.dev with sample data first

Build the report first, then add Trigger.dev when you are ready.

Start free Add data source