Google Sheets report → Telegram

What happens in live mode

Live mode reads Metrics!A2:C101 as unformatted values, validates metric/current/previous rows, calculates changes and sends one bounded report through the native Telegram node. A zero previous value produces n/a rather than invented growth. Invalid rows are counted; an entirely invalid or empty table sends nothing.

The downloaded workflow is unpublished and its Configuration mode is preview. In preview, the service branch is skipped. The website demo below also stays local. Changing a JSON input cannot enable live mode; that setting belongs to the workflow owner.

Inspect the data before connecting.

Edit the synthetic input to see the proposed fields, rows or report text. This is a transformation preview, not a call to HubSpot, Google, a feed or Telegram. No credentials belong in this form.

Ready. Inspect the preview before any live configuration.

Connect and test in your own n8n

Import the file without publishing it. The workflow includes its source, validation, duplicate/empty handling where applicable, and destination nodes. Credentials are intentionally unbound; select your own credentials in n8n rather than editing secrets into Code nodes.

1. Create a Metrics tab with metric, current, previous columns and numeric values. Configure the spreadsheet ID and range. Use a test sheet first.
2. Create a Google Sheets OAuth2 credential with custom https://www.googleapis.com/auth/spreadsheets.readonly scope; select it in Read metrics.
3. Create an n8n Telegram API credential from your own bot token. Select it in Send reviewed report. Start a conversation with the bot or add it to your intended test chat, then configure that exact chat_id.
4. Run the synthetic preview. Verify the numbers and destination, then set mode to live and run manually. Confirm the received message matches the source values.
5. If you later replace the manual trigger with a schedule, choose a time zone and an intentional report frequency. This file never schedules or posts by itself.

SHA-256: d9d8f97cfe85cae5fed3d3b249438bd4cc2abc52538c54a9dbf3bf5198f7694a

Failure, repeat runs and recovery

Each manual live run sends a new report; there is no cross-run delivery ledger. No automatic retry is configured for message sending. If delivery times out, inspect the chat before rerunning. The message is capped at 3,900 characters and the read at 100 rows; missing context and causation are not inferred.

HTTP request nodes have a 10-second timeout and stop on errors. Writes are not automatically retried. Authentication failures, rate limits and ambiguous timeouts require inspection in your own n8n execution view and destination account before rerunning. Do not turn a provider error into an empty successful lookup.

Data handling

Selected metric names and values are sent from Google Sheets to the configured Telegram chat through n8n. Text is HTML-escaped, previews are disabled, and the bot token stays in n8n credentials. Review the chat membership before using confidential metrics.

The export disables saved success/error execution data and manual-execution saving. Your instance logs and provider retention still apply; review those settings for your account. No live account is connected to AI Craft Pad by this page.

Costs and requirements

Requires your n8n instance, Google OAuth access and a Telegram bot/chat. Hosting and platform limits apply. Paid broadcasts and AI APIs are not used.