Zapier

How it works

Sloth Lee's webhook subscriptions speak HTTP POST. Zapier's Webhooks by Zapier trigger speaks the same. Wire the two together and any Zap that accepts a webhook input becomes a Sloth Lee output.

Read the Webhooks setup guide first — same secret, same signature verification.

Recipes that work today

1. Ban → Slack #moderation

1. Sloth Lee dashboard: subscribe a webhook to mod_action, point it at the Zapier catch URL.
2. Zapier: trigger = "Catch Hook" (Webhooks by Zapier).
3. Filter: only continue if data.action == "ban".
4. Action: send a Slack channel message with a templated body — actor, target, reason, server name.

2. Ticket opened → Trello card

1. Subscribe to ticket_open.
2. Zapier action: create a card on your Trello "Support" board.
3. Map ticket subject → card title; ticket body → card description; ticket URL → comment.

3. Anomaly alert → Pagerduty

1. Subscribe to anomaly_alert + bot_offline.
2. Zapier action: create a Pagerduty incident on severity ≥ major.
3. Use the data.severity field for the Pagerduty severity mapping.

4. New member → Google Sheets row

1. Subscribe to member_join.
2. Zapier action: append a row to a Google Sheet with timestamp, server name, member ID.
3. Useful for retention analysis if you don't want to use the dashboard's built-in churn scoring.

Limits to know

• Zapier's free tier limits Zap runs per month — high-volume groves should batch via Make or n8n instead.
• Sloth Lee's webhook dispatcher retries on Zapier 5xx but not on Zapier's "no remaining tasks this month" 429s — those are signal, not noise.