VAULT / Files & Storage / 0467-webhook-respondtowebhook-send-webho

Webhook → Respondtowebhook: Send Webhook

Starts on an incoming webhook, then runs 17 nodes across Google Drive, Manual Trigger, Noop, Respond to Webhook, Webhook.

25
Rough — fix first

🧩 Nodes (17)

Google DriveManual TriggerNoopRespond to WebhookWebhook

🔑 Credentials needed

  • GoogleDrive OAuth2 API
  • OpenAi API
  • Qdrant API

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

  • ✗Connections integrity. 6 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 Files & Storage

Stopanderror → Webhook: Create Webhook94Datetime → Schedule: Automation Scheduled85Code → Manual: Create Triggered78Awss3 → Compression: Automate Triggered77Box → Automate: Triggered74Code → Schedule: Send Scheduled74
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.