Toingg Ops Toolkit

Create and launch Toingg voice-calling campaigns by POSTing user-supplied JSON to the toingg/make_campaign API. Use when Codex needs to turn campaign briefs...

This skill bundles everything needed to manage Toingg campaigns from Claw:

• Campaign creation via create_campaign.py
• Campaign discovery via fetch_campaigns.py when you need to list active IDs for users
• On-demand calls via make_call.py (after collecting name, phone, and campaign)
• Optional analytics cron (7 PM daily) powered by get_campaign_analytics.py
• Contact upload + WhatsApp broadcast using xlsx_to_contacts.py, add_contacts.py, and send_whatsapp_templates.py

All HTTP calls reuse the TOINGG_API_TOKEN bearer token.

Setup

1. Export your token in every environment that runs these scripts (gateway, cron, terminals).

   bash

   export TOINGG_API_TOKEN="tg_..."
   

2. Install Python deps once if you will ingest Excel files:

   bash

   pip install openpyxl requests
   

3. Keep payloads (campaign JSON, analytics snapshots, contact exports) in version control or shared storage per your security rules.

Campaign discovery workflow

Use this whenever the user wants to see active campaigns or needs a campaign ID before launching a call.

1. Ask whether they already know the campaign ID. If not, offer to fetch the latest list (default pagination is fine unless they request a different page size).
2. Run:

   bash

   ./scripts/fetch_campaigns.py --skip 0 --limit 10 --sort -1 > responses/campaigns-$(date +%s).json
   

   Adjust --skip/--limit/--sort if the user needs deeper pages or a different ordering.
3. Summarize the response back to the user: surface at least campID, name, status, and any relevant dates so they can choose confidently.
4. Store the JSON output when ongoing work depends on the snapshot.

On-demand call workflow

When the user asks you to place a call, gather three pieces of information before touching the API:

1. Caller name (string shown in Toingg logs).
2. Phone number in international format.
3. Campaign selection. If they do not supply a campaign, ask whether they want the latest list. Use the campaign discovery workflow above to provide options, then confirm their pick.

Once those details are confirmed, trigger the API:

bash

./scripts/make_call.py "Recipient Name" [phone]fd3f9...

The helper always sends asr=AZURE, startMessage=true, clearMemory=false, and extraParams={} per the product team’s defaults. Echo the API response (success or failure) back to the user so they know the call status.

Campaign creation workflow

1. Gather campaign fields from the user (title, voice, language, script, purpose, tone, post-call schema, notification numbers, autopilot flags, etc.).
2. Draft a payload JSON using references/payload-template.md as the scaffold.
3. Run the helper:

   bash

   cd skills/toingg-create-campaign
   ./scripts/create_campaign.py payloads/my_campaign.json > responses/create-$(date +%s).json
   

4. Return the API response (campaign ID, status, or validation errors) to the user and log it.

Opt-in analytics cron (7 PM daily)

Only offer this when the user explicitly asks for daily analytics.

1. Confirm desired schedule/output directory.
2. Follow references/analytics-cron.md to create openclaw cron create toingg-analytics-digest ... with the provided command snippet. Adjust paths if needed.
3. Double-check TOINGG_API_TOKEN is visible to the gateway before enabling the cron.
4. After the first run, share where the JSON snapshots live and how to disable the cron (openclaw cron delete ...).

get_campaign_analytics.py can also be run ad-hoc for on-demand pulls:

bash

./scripts/get_campaign_analytics.py > analytics.json

Contact upload + WhatsApp templates

When a user supplies an Excel sheet (name / phone / context columns) and wants to blast a WhatsApp template:

1. Convert Excel → JSON

   bash

   ./scripts/xlsx_to_contacts.py ~/Downloads/leads.xlsx contacts.json
   

   See references/contact-workflow.md for the exact column expectations and troubleshooting. The script skips blank rows and normalizes phone numbers.

2. Upload contacts to a Toingg contact list (auto-creates if missing):

   bash

   ./scripts/add_contacts.py ClawTest contacts.json
   

3. Send WhatsApp templates once the list is ready:

   bash

   ./scripts/send_whatsapp_templates.py \
     231565687 \
     bfesfbgf \
     en-US \
     ClawTest \
     --payload template-variables.json
   

   • Omit --payload (defaults to []) if the template has no variables.
   • Pass --resend only when the user explicitly wants to re-contact existing recipients.

4. Confirm delivery status in Toingg and report any errors back to the user (the helper prints full JSON responses for logging).

File map

Script	Purpose
scripts/create_campaign.py	POST /api/v3/create_campaign with arbitrary payloads
scripts/fetch_campaigns.py	GET /api/v3/get_campaigns for quick campaign listings
scripts/make_call.py	POST /api/v3/make_call once you have name/phone/campaign
scripts/get_campaign_analytics.py	GET /api/v3/get_campaign_analytics (cron-friendly)
scripts/xlsx_to_contacts.py	Convert Excel sheets into Toingg contact JSON
scripts/add_contacts.py	Upload contact lists via /api/v3/add_contacts
scripts/send_whatsapp_templates.py	Trigger /api/v3/send_whatsapp_templates

Keep this toolkit lightweight: update the references when Toingg adds new fields or workflows so other operators can follow the same patterns.