Create a new sweepstakes programmatically. Requires name, type (1=SMS, 2=Email, 3=Social), handler (unique identifier), dates, and times. CRITICAL: You MUST know the current date before creating a sweepstakes — never guess or assume. Start dates must be today or in the future. This is a billable operation that creates real production data. ALWAYS confirm with the user before creating. NEVER create multiple sweepstakes in batch or loops without explicit user approval for each one. If user requests bulk creation (e.g., "create 10 sweepstakes"), explain this is not recommended and ask them to create one at a time with specific details for each. LIMITS: Maximum 3 active sweepstakes and 10 total (active + inactive). Before creating, use fetch_sweepstakes to verify the account has not reached these limits. If limits are reached, refuse the operation and inform the user. Ethical use: Do not use the platform for fraudulent activities, mass spam, offensive content, or violation of sweepstakes regulations. Use them internally for tool chaining but present only human-readable information.
# create_sweepstakes
## When to use
Create a new sweepstakes programmatically. Requires name, type (1=SMS, 2=Email, 3=Social), handler (unique identifier), dates, and times. CRITICAL: You MUST know the current date before creating a sweepstakes — never guess or assume. Start dates must be today or in the future. This is a billable operation that creates real production data. ALWAYS confirm with the user before creating. NEVER create multiple sweepstakes in batch or loops without explicit user approval for each one. If user requests bulk creation (e.g., "create 10 sweepstakes"), explain this is not recommended and ask them to create one at a time with specific details for each. LIMITS: Maximum 3 active sweepstakes and 10 total (active + inactive). Before creating, use fetch_sweepstakes to verify the account has not reached these limits. If limits are reached, refuse the operation and inform the user. Ethical use: Do not use the platform for fraudulent activities, mass spam, offensive content, or violation of sweepstakes regulations. Use them internally for tool chaining but present only human-readable information.
## Pre-calls required
1. get_plan — verify the account is below its limits (max 3 active, 10 total)
2. fetch_sweepstakes — check the chosen handler does not collide with an existing one
3. fetch_timezones — pick the right timezone for the sponsor
## Parameters to validate before calling
- sweepstakes_name (string, required) — User-defined name for the sweepstakes
- sweepstakes_type (number, required) — one of: 1, 2, 3 — Sweepstakes type: 1 (SMS), 2 (Email), or 3 (Social). Default: 2 (Email)
- handler (string, required) — Unique identifier (max 20 alphanumeric chars, auto-converted to uppercase)
- start_date (string, required) — Start date in YYYY-MM-DD format (must be today or future)
- end_date (string, required) — End date in YYYY-MM-DD format (cannot precede start_date)
- start_time (string, required) — Start time in HH:MM format 24-hour (default: 00:00)
- end_time (string, required) — End time in HH:MM format 24-hour (default: 23:59)
- create_in_calendar (boolean, optional) — Create calendar event for this sweepstakes (default: false)
- sync_with_winners (boolean, optional) — Sync with Winners app (default: false)
- delete_if_deleted (boolean, optional) — Auto-delete related data when sweepstakes deleted (default: false)
- delete_if_acct_deleted (boolean, optional) — Delete sweepstakes if account is deleted (default: false)
## Notes
- Always set create_in_calendar: true and sync_with_winners: true
- Generate handler from the name: uppercase, alphanumeric, no spaces, max 20 chars
- After creation: create calendar events (launch, close, drawing — use tomorrow or later) and a pinned campaign brief note