[feat] Add trigger subscriptions and deliveries

[jp-agenta]

Context

With the triggers domain and catalog in place, this lane adds the two-table heart of the feature: subscriptions (a bound provider event plus a workflow to run) and deliveries (the record of each event that arrived). They are modeled directly on the existing webhook_subscriptions and webhook_deliveries tables.

Changes

Adds subscription CRUD and delivery reads:

• trigger_subscriptions table: flags (enabled/valid) plus data, the Composio ti_* id, the trigger_config, the inputs_fields mapping template, the destination references/selector, the bound workflow ref, and a foreign key to the shared gateway_connections row. Many subscriptions can share one connection. The tables are domain-prefixed (trigger_*) to avoid colliding with the EE billing subscriptions table, matching the webhook_* naming.
• trigger_deliveries table: the resolved inputs, workflow references, result/error, and an event_id dedup column unique per subscription. The dedup column is the idempotency store; there is no external one.
• Subscription routes (/triggers/subscriptions/{,query,{id},{id}/refresh,{id}/revoke}) drive the Composio ti_* lifecycle through the adapter. Delivery routes (/triggers/deliveries/{,{id},query}) are read-only.
• The DAO exposes get_subscription_by_trigger_id, write_delivery, and dedup_seen(event_id) for the later ingress lane to consume.

Deleting or revoking a subscription touches only the provider ti_*. It never revokes the shared connection, so other subscriptions and tools on that connection keep working.

Mapping is inputs-only for now: the inputs_fields template is resolved with the promoted resolver from the WP2 lane. Schema validation of the mapped inputs is left as a follow-up.

Tests / notes

• Subscription/delivery acceptance tests run in both OSS and EE. The DB-only read/query/404 paths run unconditionally and prove the migration landed; the create-disable-delete path (and the assertion that the connection survives a subscription delete) is gated on COMPOSIO_API_KEY, matching the catalog and connections suites.
• The migration oss000000003 is in the shared core_oss chain on top of the WP0 rename, so it runs in both editions.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
agenta-documentation	Ready	Preview, Comment	Jun 19, 2026 9:00am

[coderabbitai]

Important

Review skipped

Draft detected.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 74a6d24a-afb7-4030-8b77-3c5af28f706b

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch wp3-subscriptions

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[jp-agenta]

Superseded by #4749, which consolidates the entire gateway-triggers work (api + web + hosting + docs) into a single PR.