Permanently delete a sweepstakes and all associated data including participants, statistics, and automations. Use fetch_sweepstakes first to get the sweepstakes_token. CRITICAL: This is a DESTRUCTIVE operation that cannot be undone. ALWAYS ask for explicit user confirmation before deleting, showing the sweepstakes name. NEVER delete multiple sweepstakes in batch or loops. If user requests bulk deletion, refuse and ask them to delete one at a time after reviewing each.
# delete_sweepstakes
## When to use
Permanently delete a sweepstakes and all associated data including participants, statistics, and automations. Use fetch_sweepstakes first to get the sweepstakes_token. CRITICAL: This is a DESTRUCTIVE operation that cannot be undone. ALWAYS ask for explicit user confirmation before deleting, showing the sweepstakes name. NEVER delete multiple sweepstakes in batch or loops. If user requests bulk deletion, refuse and ask them to delete one at a time after reviewing each.
## Pre-calls required
1. fetch_sweepstakes if the user gave you a sweepstakes name instead of a token
## Parameters to validate before calling
- sweepstakes_token (string, required) — The unique identifier (token) of the sweepstakes to delete
## Notes
- DESTRUCTIVE — IRREVERSIBLE. Always confirm with the user before calling. Explain what will be lost.
- IRREVERSIBLE — destroys ALL associated data (participants, rules, winners, statistics)
- ALWAYS require explicit user confirmation. Explain exactly what will be lost.
Connector
