new-term-radar
Daily radar for new AI terms: names of new models, products and repos, caught on X, Hugging Face, GitHub and sitemaps before keyword tools list them.
Messaggistica WhatsApp per lead da ActiveCampaign
Translation pending
MarketingTypeScript · JavaScriptGitHub @brunoiacopo02OnlineOwner unconfirmed
Have you tried it? One tap is enough. No sign-in needed.
No updates detected yet. GitHub releases will appear here.
Owners of public repositories under a personal GitHub account can sign in to verify ownership and manage the introduction themselves. No administrator approval is needed.
Sign in, generate a verification file, and commit it to this repository’s default branch within 30 minutes. Files on other branches or forks do not count. Then check the file below to manage the project without administrator approval. Keep the file to retain your access.
If needed, you will go to sign-in. After signing in, return here and press your chosen verification button again.
Run /nomorevibe verify in your project folder to verify ownership and manage the introduction yourself.
Verify in one minuteAsk about other verification options
Loading the full README. The saved excerpt is shown below.
Webapp che riceve nuovi lead da ActiveCampaign via webhook, invia immediatamente un template WhatsApp tramite Twilio, e gestisce le risposte in un'inbox stile WhatsApp con notifiche real-time. Spec completa: docs/superpowers/specs/2026-05-01-whatsapp-lead-design.md Piano implementativo: docs/superpowers/plans/2026-05-01-whatsapp-lead-messaging.mdRead the full README ↗
Webapp che riceve nuovi lead da ActiveCampaign via webhook, invia immediatamente un template WhatsApp tramite Twilio, e gestisce le risposte in un'inbox stile WhatsApp con notifiche real-time.
Spec completa: docs/superpowers/specs/2026-05-01-whatsapp-lead-design.md
Piano implementativo: docs/superpowers/plans/2026-05-01-whatsapp-lead-messaging.md
bun install
cp .env.example .env.local # poi compila i valori
bun dev # http://localhost:3000
Per testare i webhook in locale serve un tunnel pubblico:
bunx ngrok http 3000
# usa l'URL ngrok come NEXT_PUBLIC_APP_URL e nei webhook
Vedi .env.example. In production tutte sono settate su Vercel.
| Variabile | Scopo |
|---|---|
NEXT_PUBLIC_SUPABASE_URL | Project URL Supabase |
NEXT_PUBLIC_SUPABASE_ANON_KEY | Anon key (browser) |
SUPABASE_SERVICE_ROLE_KEY | Service role (server only — webhooks) |
TWILIO_ACCOUNT_SID | Twilio Account SID |
TWILIO_AUTH_TOKEN | Twilio Auth Token |
TWILIO_WHATSAPP_NUMBER | Numero WA approvato Meta (whatsapp:+...) |
TWILIO_VALIDATE_SIGNATURE | true in prod, false solo dev locale |
AC_API_KEY | API key AC (riservato per estensioni future) |
AC_ACCOUNT_URL | URL account AC (es. nomeaccount.api-us1.com) |
AC_WEBHOOK_SECRET | Token segreto in URL del webhook AC |
NEXT_PUBLIC_APP_URL | URL base prod (https://...vercel.app) |
Auto-deploy via Vercel a ogni push su main. Branch diversi → preview deployment.
https://<dominio-vercel>/api/webhooks/activecampaign?secret=<AC_WEBHOOK_SECRET>
# Trova il SID del numero WA
curl -u $TWILIO_ACCOUNT_SID:$TWILIO_AUTH_TOKEN \
"https://api.twilio.com/2010-04-01/Accounts/$TWILIO_ACCOUNT_SID/IncomingPhoneNumbers.json"
# Configura inbound + status callback
curl -u $TWILIO_ACCOUNT_SID:$TWILIO_AUTH_TOKEN \
-X POST "https://api.twilio.com/2010-04-01/Accounts/$TWILIO_ACCOUNT_SID/IncomingPhoneNumbers/<NUMBER_SID>.json" \
--data-urlencode "SmsUrl=https://<dominio-vercel>/api/webhooks/twilio" \
--data-urlencode "SmsMethod=POST" \
--data-urlencode "StatusCallback=https://<dominio-vercel>/api/webhooks/twilio"
Se il numero è dentro un Messaging Service:
curl -u $TWILIO_ACCOUNT_SID:$TWILIO_AUTH_TOKEN \
-X POST "https://messaging.twilio.com/v1/Services/<SERVICE_SID>" \
--data-urlencode "InboundRequestUrl=https://<dominio-vercel>/api/webhooks/twilio" \
--data-urlencode "StatusCallback=https://<dominio-vercel>/api/webhooks/twilio"
Supabase Dashboard → Authentication → Users → Add user (email + password, "auto confirm").
UI /campagne → Nuova campagna → compila Nome, Lista AC trigger (nome esatto o ID), Template Content SID (HX...), variabili template, Attiva → Crea.
/log tab "Eventi sistema" → record ac_webhook ricevuto/log tab "Invii" → riga con stato queued → sent → delivered/inbox mostra la conversazione + bolla in entrataDati personali trattati: nome, cognome, email, numero di telefono, contenuto messaggi WhatsApp. V1 non espone UI per export/delete: per richieste GDPR contattare l'amministratore — operazione manuale via SQL su Supabase (delete from leads where ..., cascade automatica su conversations + messages).
bun test # unit (Vitest)
bun run typecheck # tsc --noEmit
bun run build # next build
bun run test:e2e # Playwright (richiede E2E_EMAIL + E2E_PASSWORD)