Implement AI-ready GitHub issues with CloudCLI and Telegram summaries
UnknownUnknown. 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.
Community nodes
These come from third-party npm packages. In n8n 3.0 unverified community packages are off by default (N8N_UNVERIFIED_PACKAGES_ENABLED=false).
@cloudcli-ai/n8n-nodes-cloud-cli(CloudCLI Implement Issue)
Nodes used (6)
- Schedule Trigger
n8n-nodes-base.scheduleTrigger - Edit Fields (Set)
n8n-nodes-base.set - GitHub
n8n-nodes-base.github - Telegram
n8n-nodes-base.telegram - Cloud Cli
@cloudcli-ai/n8n-nodes-cloud-cli.cloudCli - Loop Over Items (Split in Batches)
n8n-nodes-base.splitInBatches
What it does
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 works 1. Runs every night at 2:00 AM on a schedule. 2. Loads the repository, label, base branch, CloudCLI environment URL, and Telegram chat ID from a configuration step. 3. Fetches all open GitHub issues in the configured repository that match the configured label. 4. Processes the issues one by one and sends each issue title and body to CloudCLI to implement the change, create a branch, and open a pull request against the configured base branch. 5. Posts a comment on each GitHub issue noting that CloudCLI opened a pull request and includes the CloudCLI environment link. 6. After all issues are processed, sends a Telegram message summarizing the run and listing the issues handled. Setup 1. Add GitHub credentials with permission to read issues and create issue comments, and ensure the configured repo owner and repo name match your repository. 2. Add CloudCLI credentials, set the CloudCLI environment ID/URL in the configuration, and provide a GitHub token in the CloudCLI node so it can push branches and open pull requests. 3. Add Telegram bot credentials and set your target Telegram chat ID in the configuration. 4. Update the configuration values (label and base branch) to match your triage label (for example, ai-ready) and the branch you want pull requests opened against (for example, main).