Block 1 - Sticky Note
- Type / Role
- n8n-nodes-base.stickyNote - stickyNote
- Config choices
- Version 1
This workflow is provided as-is. Please review and test before using in production.
Who is this for? This workflow is ideal for: Developers who want to stay updated on issues without constantly checking GitHub. Managers tracking issue progress in a Telegram group. DevOps teams tha...
n8n-nodes-base.stickynote, n8n-nodes-base.telegram, n8n-nodes-base.filter, n8n-nodes-base.set, n8n-nodes-base.scheduletrigger, n8n-nodes-base.github
This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by Prakash.
Original n8n.io sourceThis workflow is ideal for:
Keeping track of GitHub issues manually can be tedious. Teams often miss critical updates because notifications are buried in emails or dashboards. This workflow automates the process by fetching new or open GitHub issues and instantly sending notifications to a specified Telegram chat.
This workflow connects GitHub and Telegram to provide real-time issue notifications:
Before setting up the workflow, ensure you have:
repo or public_repo permissions. Set Up GitHub Node
Format Issue Details
Send Message to Telegram
Schedule the Workflow (Optional)
This catalog entry is organized from the workflow JSON. The node-level section below shows the executable blocks available for review before importing the template.
| Workflow | Get GitHub issue updates and send notifications to Telegram |
|---|---|
| Complexity | intermediate |
| Nodes | 9 |
| Categories | Project Management |
| Author | Prakash |
| Published | 26 Feb 2025 |
Use the JSON export at /data/workflows/3021/3021.json as the source template for this automation.
Open n8n, import the downloaded JSON, and review each node before activating the workflow.
Replace placeholder credentials, API keys, webhook URLs, account IDs, and environment-specific values with your own settings.
Run the workflow manually or in a staging workspace, inspect node output, and confirm downstream systems receive the expected data.
Enable the workflow only after testing, then monitor executions, errors, and rate limits during the first production runs.
Review imported nodes carefully before activation. This catalog entry is intended to help you inspect the workflow structure, understand required services, and find related templates faster.
Node names, credentials, schedules, webhook paths, and external service limits may need adjustment for your workspace.
Who is this for? This workflow is ideal for: Developers who want to stay updated on issues without constantly checking GitHub. Managers tracking issue progress in a Telegram group. DevOps teams tha...
Review the workflow JSON, configure any required credentials in n8n, and test the automation in a safe workspace before using it in production.
Yes. Use the block-by-block analysis and the downloadable JSON to inspect each node, then adjust credentials, prompts, schedules, filters, or destinations for your Project Management use case.