TASIP-011: Richer trigger setup

[ryw]

Status: Draft — open for input · Category: Enhancement

Summary

Replace free-text trigger entry with schema-driven config forms pulled from each provider, so setting up an event trigger is discoverable and self-documenting instead of memorizing slugs.

Why

Today configuring an event trigger means knowing the exact trigger name and its config shape. That's a papercut that makes a powerful feature feel fragile and expert-only.

Sketch

• Pull the trigger type's schema from the provider and render a real form.
• Validate config against the schema before saving.
• Same idea extends to webhook setup where applicable.
  (Provisional — the shape changes based on the discussion.)

Open questions

• How much provider-schema coverage is realistic?
• Fallback when a provider exposes no schema?
• How to keep forms current as providers change?

How to help

React 👍 if you want this, and comment with your use case, constraints, or pushback. This is a draft Tembo Agent Studio Improvement Proposal (TASIP); your input shapes it before it becomes scheduled work.