toingg-create-campaign_skill

Overview

This skill creates and launches Toingg voice-calling campaigns by POSTing user-supplied JSON to the Toingg create_campaign API. It wraps the create_campaign.py helper to handle authentication and HTTP communication, letting you turn a campaign brief into a live campaign quickly. The script prints the API response so you can capture the new campaign ID or diagnose errors.

How this skill works

You provide a validated JSON payload that matches Toingg's campaign schema (title, voice, language, script, tone, notifications, autopilot flags, etc.). The script reads TOINGG_API_TOKEN from the environment, posts the payload to the API endpoint, and returns the JSON response. It does not modify campaign fields; it only handles auth, request, timeout, and response output.

When to use it

• When you have a complete campaign brief that must be turned into a live Toingg campaign.
• When automating campaign launches from a CI job or operator workflow.
• When validating and posting structured campaign payloads after review.
• When you need a reproducible CLI step to create campaigns and capture responses.

Best practices

• Export TOINGG_API_TOKEN as an environment variable before running the script.
• Start from the official payload template and remove unused keys to keep payloads minimal.
• Validate required keys (title, voice, language, purpose, script) before POSTing.
• Avoid embedding secrets in the payload; only the bearer token should be in env.
• Capture the script output to a file to preserve response details and campaign ID.

Example use cases

• Operator composes a campaign JSON from a brief and runs create_campaign.py to launch voice outreach.
• A CI pipeline builds a payload from templates and posts it as a step in an automated deployment.
• Support team reproduces a customer campaign by editing a saved payload and re-running the script.
• QA verifies schema changes by crafting payload variants and checking API validation errors.