VAULT / Chat & Messaging / 1904-telegram-limit-process-webhook

Telegram → Limit: Process Webhook

Starts on an incoming webhook, then runs 54 nodes across Aggregate, Gmail, Gmailtrigger, Google Drive, Google Sheets.

60
Needs hardening

🧩 Nodes (54)

AggregateGmailGmailtriggerGoogle DriveGoogle SheetsHttprequestIfLimitMerge

🔑 Credentials needed

  • Gmail OAuth2
  • GoogleDrive OAuth2 API
  • GoogleSheets OAuth2 API
  • HttpHeaderAuth
  • OpenAi API
  • Telegram API

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

  • ✗Connections integrity. 16 dangling connections — will not run as shipped.
  • ✓Error handling. Error paths exist (Error Trigger / onError / stop-and-error).
  • ✓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.