VAULT / Chat & Messaging / 1385-webhook-respondtowebhook-automate-w

Webhook → Respondtowebhook: Automate Webhook

Starts on an incoming webhook, then runs 24 nodes across Google Drive, Httprequest, If, Manual Trigger, Noop.

30
Rough — fix first

🧩 Nodes (24)

Google DriveHttprequestIfManual TriggerNoopRespond to WebhookWebhookWhatsapp

🔑 Credentials needed

  • GoogleDrive OAuth2 API
  • HttpHeaderAuth
  • OpenAi API
  • Qdrant API
  • WhatsApp API

🛡️ Vault audit — 30/100 · last checked 2026-10-27

  • ✗Connections integrity. 9 dangling connections — will not run as shipped.
  • ✗Error handling. None. A failing node fails silently or kills the run.
  • ✓Hardening patterns. Guards / branching / batching present.
  • ✓Trigger configured. Has a start trigger.

This one needs work before production. In its Production Pack version we repair the flagged items, inject error handling and ship a setup doc — the raw file below stays free, exactly as-is.

⬇ Download raw JSON (free)Read the matching hardening guide

More in Chat & Messaging

Telegram → Rssfeedread: Automation Scheduled94Telegram → Executecommand: Process Webhook89Webhook → Cron: Automate Scheduled89Filter → Telegram: Send Triggered89Wait → Schedule: Create Scheduled88Nocodb → Telegram: Create Webhook87
License & provenance. Raw workflow from the MIT-licensed community collection (© Zie619). License: included. Our audit score, fixes and docs are our work — the raw JSON is free forever.