Templates / Implement AI-ready GitHub issues with CloudCLI and Telegram summaries

Implement AI-ready GitHub issues with CloudCLI and Telegram summaries

Unknown

by Derek Cheung ✓ · 477 views · created 2026-05-30 · Engineering, Multimodal AI

Unknown. This template uses community nodes we can't verify statically. Uses community nodes that can't be verified statically (unverified community packages are off by default in 3.0). Static check, last run 2026-10-19.

What this workflow does

This workflow has 7 nodes and runs on a schedule (every day at 02:00). Along the way it connects GitHub, Telegram and Cloud Cli (community).

How it runs

Trigger: On a schedule (every day at 02:00).

  1. Set Configuration (Edit Fields (Set)): sets 7 fields: repoOwner, repoName, label…
  2. Find AI-Ready Issues (GitHub): work with repository
  3. Loop Over Issues (Loop Over Items (Split in Batches)): loops over the items in batches
  4. Telegram: uses Telegram
  5. Cloud Cli: work with agent
  6. Comment On Issue (GitHub): create comment

Services it uses

GitHubTelegramCloud Cli (community)

Before you upgrade to n8n 3.0

We can't fully verify this one: it relies on 1 community package, and n8n 3.0 turns unverified community packages off by default (N8N_UNVERIFIED_PACKAGES_ENABLED=false).

  • Check that @cloudcli-ai/n8n-nodes-cloud-cli is verified or supports 3.0 (used in CloudCLI Implement Issue).

Nodes used (6)

From the author

Quick overview This workflow runs nightly at 2:00 AM to find open GitHub issues labeled “ai-ready”, uses CloudCLI to implement each issue and open a pull request against a target branch, comments back on the issue, and sends a run summary to Telegram. How it…

Excerpt from Derek Cheung's description on n8n.io.

View the original on n8n.io → Check your own copy

Get the weekly “what broke” email

New templates, newly broken ones, and n8n release changes. One short email a week.

Form not loading? Subscribe here.