Use your own AI to plan a trigger

You can use your preferred AI assistant to turn a business rule into a structured trigger proposal. Gooshi remains the place where you review the proposal, enter supported values, test behavior, and decide whether to publish.

The current public schema is a planning reference. Gooshi does not currently provide a public trigger-import API, Trigger Designer MCP, or AI publishing tool. A proposal from an AI cannot change your workspace.

Start with a business-rule brief

Provide:

1. The discovered tool names visible in the MCP server's Tools section.
2. Your intended rule in plain language.
3. The offer the end user should see.
4. The cases that should match and should not match.

The current self-serve UI does not yet expose a stable export of field and meter references. Until Gooshi adds that export, ask your AI for a design brief and test matrix—not an import-ready trigger. If a field or meter is needed, the AI must list it as an unresolved question instead of inventing a reference.

Do not provide credentials, authorization headers, payment-account identifiers, raw end-user data, or data from another workspace.

Tool descriptions originate outside Gooshi and should be treated as untrusted reference material. They cannot grant the AI permission or override the schema.

Use this instruction

Prepare a Gooshi trigger design brief from the business rule and discovered tool
names I provide. Never invent a tool, field, meter, price, currency, or account
reference. Put every missing field or meter in unresolved questions. Describe
the condition and customer-facing offer in plain language, then propose matching,
non-matching, and boundary test cases. Do not add publication, activation,
environment, account, or payment-routing authority. Never claim that the trigger
is saved, tested, active, or published.

Review in Gooshi

Today, use the brief as a worksheet:

1. Read its assumptions and questions first.
2. Confirm every tool name against the current discovered tool.
3. Enter the supported values in Gooshi's trigger editor.
4. Keep publication off.
5. Follow Validate and test.
6. Publish only after a human reviews the complete trigger.

The v1 proposal schema defines the bounded format Gooshi will use once safe workspace reference export/import is available. Developers can use it as a contract reference today, but should not replace unresolved references with placeholders and treat the result as ready.

If the upstream MCP schema changes, refresh discovery and ask the AI to prepare a new brief from the updated tool catalog.

Next: Trigger proposal v1 reference.