← All N8N workflows
Messaging & emailFilterGithubSchedule TriggerEdit FieldsTelegram

FetchGithubIssues

Configured with Filter, Github, Schedule Trigger, Telegram. Review the connections and setup before adapting this template.

Workflow preview
MessagingSend Message to @userTelegramRoutingCheck for commentsFilterTransformMap title, url,created, commentsEdit FieldsTriggerRun every 10 minutesSchedule TriggerIntegrationGet Github IssuesGithub

Node categories in this workflow

  • Messaging
  • Routing
  • Transform
  • Trigger
  • Integration

Icons describe general node roles, inferred from node types. Inspect the parameters for the configured action.

Drag to pan; use + and − to zoom. Reconstructed from the exported node positions; nothing runs here. Dashed lines represent non-main connections. Full node names and notes appear below.

How it works

The exported workflow contains the following configured nodes. Their connections are shown above; inspect the JSON for the complete logic, expressions, and external actions.

Workflow node names, types, and operations
NodeCategoryTypeOperation
Send Message to @userMessagingTelegramSee node parameters
Check for commentsRoutingFilterSee node parameters
Map title, url, created, commentsTransformEdit FieldsSee node parameters
Run every 10 minutesTriggerSchedule TriggerSee node parameters
Get Github IssuesIntegrationGithubrepository

Setup

  1. Download the JSON and import it into an isolated n8n instance. Leave the workflow inactive.
  2. Connect your own credentials through n8n’s credential store. Replace REPLACE_WITH_* values with your resource identifiers.
  3. Inspect API destinations, Code nodes, database queries, file paths, and outbound actions.
  4. Run with synthetic data and harmless destinations. Enable triggers only after checking the actual outputs.

Requirements

An n8n instance with the listed node types and compatible versions. Service-connected workflows may require accounts, credentials, or paid APIs.

Credential types declared in the source

  • githubApi
  • telegramApi

Workflow notes

Get Github Issues HTTP Request

Get Github Issues HTTP Request

  • Edit the OWNER and REPO NAME in the respective fields
  • The request is configured with query parameters of state, since and labels
Extract Fields

Extract Fields

Extract fields like title, comments, created_at, etc from the github api response

Filter on Fields

Filter on Fields

Filter issues based on number of comments

Send message to Telegram User

Send message to Telegram User

  • This node is configured to send issue title and url to your user id
  • Create a new telegram bot using the instructions here and configure bot token in the telegram credential
  • Chat ID can be your username or your username ID
FetchGithubIssues

FetchGithubIssues

Purpose and structure

This folder contains the FetchGithubIssues workflow. Its executable nodes use filter, github, scheduleTrigger, set, telegram. The table and connection map below are derived from the JSON, not an inferred guarantee of behavior.

Setup

Import inactive. Configure your own credentials and replace REPLACE_WITH_* values. Review external destinations and Code nodes before running.

Entry points

Run every 10 minutes

Verification

Sanitized source candidate; not runtime-tested. This overview is generated from node metadata. Read the folder README for the connection map, credential types, and license.

Attribution

https://github.com/Zie619/n8n-workflows/blob/94007c1445d9258a7da116646b79473e7c7c3282/workflows/Telegram/1945_Telegram_Schedule_Import_Scheduled.json MIT; preserve source notices.

More in Messaging & email