[feat] Add gateway trigger subscriptions and deliveries UI#4744
[feat] Add gateway trigger subscriptions and deliveries UI#4744jp-agenta wants to merge 1 commit into
Conversation
Mirrors the webhook-subscription settings UI for inbound triggers. - Subscriptions section under Settings > Triggers, listing a shared connection's subscriptions with create/edit drawers. - TriggerSubscriptionDrawer binds a workflow revision via the shared EntityPicker + workflowRevisionAdapter, sending the destination as a references dict (workflow_revision) in the /retrieve shape; inputs mapping edited as JSON. Connection locked in edit mode (FK anchor). - TriggerDeliveriesDrawer shows delivery history per subscription. - useTriggerSubscriptions / useTriggerSubscription / useTriggerDeliveries hooks plus entities api wiring; triggerReferenceSchema added. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
Important Review skippedDraft detected. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 Generate unit tests (beta)
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. Comment |
|
Superseded by #4749, which consolidates the entire gateway-triggers work (api + web + hosting + docs) into a single PR. |
Context
The backend can store trigger subscriptions and (with the api lane) dispatch them, but there is no UI to create or inspect them. Users need to pick a shared connection, choose which provider event to watch, bind a workflow, and later see whether deliveries succeeded.
What this adds
A Triggers settings area that mirrors the existing webhook-subscription UI.
Under Settings > Triggers, a subscriptions section lists a shared connection's subscriptions with create and edit drawers. The
TriggerSubscriptionDrawerbinds a workflow revision through the sharedEntityPicker+workflowRevisionAdapter, and sends the destination as areferencesdict keyedworkflow_revisionin the/retrieveshape the backend expects:The inputs mapping is edited as JSON in the shared editor. In edit mode the connection is locked, since it is the FK anchor of the subscription. The
TriggerDeliveriesDrawershows delivery history for a subscription so you can confirm events are landing and see failures.Data fetching goes through three new hooks (
useTriggerSubscriptions,useTriggerSubscription,useTriggerDeliveries) plus the entities api wiring, and atriggerReferenceSchemavalidates the reference shape.Tests / notes
gatewayTriggerApi.test.tspasses (13/13).pnpm lint-fixclean onweb/.What to QA