add-sms-opt-ins-from-incoming-replies-to-consent-trackerlisted
Install: claude install-skill zapier/awesome-zaps
# Add SMS opt-ins from incoming replies to consent tracker
The Zap's code lives at https://github.com/zapier/awesome-zaps/tree/main/zaps/add-sms-opt-ins-from-incoming-replies-to-consent-tracker. Read the files there if this skill was installed on its own.
## What it does
1. **Trigger:** an SMS reply arrives at a Webhooks by Zapier catch hook (`webhook`, `hook_v2`). Your SMS provider or form posts the reply to it.
2. **Opt-in check (code, no app call):** the first word of the reply must be an opt-in keyword (`YES`, `Y`, `START`, `UNSTOP`, `SUBSCRIBE`, `JOIN`, case-insensitive). Anything else ends the run with no write.
3. **Phone check (code):** the sender number is normalized to E.164. A number with fewer than 8 digits ends the run with no write.
4. **Airtable** creates one record in the consent table: normalized phone, the name typed after the keyword (if any), the raw reply, the opt-in box ticked, and the submission ID from the payload.
The Zap writes a record only when a reply starts with an opt-in keyword, and it never sends a message to the sender.
## Ask the user
Each `REPLACE_…` value is set per person. Resolve names to IDs with the user's own connections; don't ask them to paste an ID you can look up.
| Setting | What goes there |
| --------------------- | ----------------------------------------------------------------------- |
| `AIRTABLE_BASE_ID` | The Airtable base that holds consent r