Triggers
Publish and pause
Release a reviewed trigger in the current environment and stop it when needed.
Gooshi uses two user-facing states:
- Draft: configured but not enforcing payment on the wrapped endpoint.
- Published in current environment: active for matching calls in the environment shown by the workspace.
Before publishing
Review:
- MCP server and tool.
- Condition and boundary cases.
- Payment type, amount, and currency.
- Connected payment account.
- User-facing messages.
- A successful wrapped-endpoint test.
Publish only when every item belongs to the intended MCP Owner Workspace and current environment.
Pause a trigger
If behavior, pricing, or the upstream tool changes unexpectedly, turn publication off in the trigger editor and save. Verify with a new client session, then investigate before publishing again.
Keep a record of the change and its reason for your team. If you cannot pause a rule safely, include the MCP server and trigger names in a support request.