Skip to content

Vouch Request: HTTP webhook trigger + run cost analytics #3353

Closed as not planned

Description

@mvanhorn

Why do you want to contribute?

I want to add two features to trigger.dev:

  1. HTTP webhook trigger endpoint - an authenticated POST endpoint (/api/v1/tasks/:taskId/trigger) that lets external services trigger tasks without the SDK. Stripe, GitHub, Slack webhooks could trigger tasks directly instead of requiring glue code. Issue Vouch Request: Incoming webhook trigger #3295 is a vouch request for a similar idea. Inngest's event ingestion model shows the demand for this pattern.

  2. Run cost & duration analytics dashboard - a new analytics section in the project dashboard showing per-task duration stats (avg, p95, p99), estimated compute cost, and trends over time. ClickHouse already stores the run data. I'd build this on top of the existing clickhouseEventRepository patterns and the ChartBar component.

Both changes follow the server-only .server-changes/ pattern (no package changes needed for the webhook endpoint, and the analytics dashboard is webapp-only).

Prior contributions or relevant experience

I maintain several open source TypeScript projects and have contributed to repos using similar patterns (Remix routes, Zod validation, ClickHouse queries). I've read the CONTRIBUTING.md, the .claude/rules/ conventions, and the V1/V2 engine architecture docs to make sure contributions fit the existing codebase.

GitHub: https://github.com/mvanhorn

Activity

  1. matt-aitken commented on Oct 7, 2026

    @matt-aitken
    Member

    We have a new Vouch policy, please see the discussion here: #5010

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions