Recipe Send Alerts to Your Team

Recipe: Send Alerts to Your Team

Use when: an actionable CCAM condition should reach Slack, Discord, Teams, email, a generic webhook, or another supported provider.

Procedure

1. Name the condition and owner in one sentence: “Platform on-call investigates remote sources in error for longer than X.”

2. Observe normal behavior and select the matching alert rule type.

3. Create a narrow rule with a cooldown that prevents repeated noise.

4. List provider requirements:

   npx ccam webhooks providers

5. Put target configuration and secrets in a restricted JSON file.

6. Create the target using the current ccam webhooks create --help syntax.

7. Send a synthetic test:

   npx ccam webhooks test <webhook-id>
   npx ccam webhooks deliveries <webhook-id>

8. Trigger or safely simulate the real rule and verify message context.

9. Document acknowledgement and escalation behavior.

A useful notification contains

• rule name and severity;
• affected source/session when available;
• first trigger time and current duration/count;
• concise reason;
• link or identifier for investigation;
• owner or response instruction.

Security

Webhook URLs and signing secrets are credentials. Do not place them in shell history or issues. CCAM masks stored URLs and does not return secrets; retain the source secret securely for rotation.

See Alerts and Webhook Recipes.