clix-api-triggered-campaigns
Helps developers configure API-triggered campaigns in the Clix console and trigger them from backend services with safe auth, payload schemas, dynamic audience filters (trigger.*), and personalization best practices. Use when the user mentions transactional notifications, backend-triggered sends, campaign_id trigger APIs, or "API-triggered campaigns".
npx skills add majiayu000/claude-skill-registry --skill api-triggered-campaigns-clix-so-skills --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# API-Triggered Campaigns (Backend → Clix) Use this skill to set up **API-triggered campaigns** in the Clix console and trigger them from your backend with dynamic data (`trigger.*`) for: - Transactional notifications (orders, password reset, receipts) - Workflow messages (assignments, approvals) - System alerts (moderation, support tickets) - Programmatic sends where marketers/ops should control content + targeting ## What the official docs guarantee (high-signal) - API-triggered campaigns are configured in the console, then triggered via: `POST /api/v1/campaigns/{campaign_id}:trigger` - Authentication uses **secret** headers: - `X-Clix-Project-ID` - `X-Clix-API-Key` - Request `properties` become **`trigger.*`** for: - **Dynamic audience filtering** (console audience rules) - **Personalization** in templates (title/body/deep links) - `audience.broadcast=true` sends to all users eligible under the campaign’s segment definition; `audience.targets` narrows to specific users/devices (still filtered by the segment definition). - Dynamic audience filters are intentionally constrained for performance: **max 3 attributes** in the audience definition. ## MCP-first (source of truth) If Clix
- What the official docs guarantee (high-signal)
- MCP-first (source of truth)
- Workflow (copy + check off)
- 1) Confirm the minimum inputs
- 2) Create a “Trigger Plan” (before touching backend code)
- 3) Configure campaign in the console (API-triggered)
- 4) Implement backend trigger wrapper (best practices)
- 5) Validate the plan (fast feedback loop)
- 6) Verify (Clix + end-to-end)
- Progressive Disclosure
- References
bash <skill-dir>/scripts/validate-api-trigger-plan.sh .clix/api-trigger-plan.json
What does the clix-api-triggered-campaigns skill do?
Helps developers configure API-triggered campaigns in the Clix console and trigger them from backend services with safe auth, payload schemas, dynamic audience filters (trigger.*), and personalization best practices. Use when the user mentions transactional notifications, backend-triggered sends, campaign_id trigger APIs, or "API-triggered campaigns".
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill api-triggered-campaigns-clix-so-skills --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.