Individual skill

customerio-common-errors

Diagnose and fix Customer.io common errors. Use when troubleshooting API errors, delivery failures, campaign issues, or SDK exceptions. Trigger: "customer.io error", "customer.io not working", "debug customer.io", "customer.io 401", "customer.io 429".

plugins/saas-packs/customerio-pack/skills/customerio-common-errors/SKILL.md

Read pinned source

Source commit 0500b275e963c027f6b410e8c49c0446945c574e

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
No
Observed behavior
Not checked yet
Last checked
Nov 12, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
2,917
Repository last updated
Nov 12, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt
# Customer.io Common Errors

## Output

- A classified Customer.io integration failure with redacted request/response evidence and an accountable owner.
- A bounded remediation or escalation that preserves message integrity, consent, and rate controls.

## Error Handling

| Condition | Safe response |
|---|---|
| Authentication or authorization fails | Verify the scoped secret reference and workspace/region; rotate/revoke through the secret manager if exposure is suspected. |
| Delivery event is missing | Check identifier, consent, suppression, and event ordering before replaying anything. |
| Rate limit or transient error occurs | Apply documented backoff and idempotency; do not flood retries or disable limits. |
| Payload contains sensitive attributes | Redact diagnostics and validate the data contract before retrying. |
Back to top