OpenRuna
Sign in
← Workflows

Github Releases

24 nodes · limit, splitInBatches, schedule, slack, dateTime, informationExtractor

Engine
n8n
Nodes
24
Trigger
scheduled/triggered
Source file
1695_Limit_Code_Automation_Scheduled.json

Workflow flow

IntegrationsLimitSplitInBatchesScheduleSlackDateTimeInformationExtractorLmChatGoogleGeminiRedisRssFeedReadSetCodeIF+2 more
100%
TRIGGER

Cron Trigger

Schedule

Gemini

@n8n/n8n-nodes-langchain.lmChatGoogleGemini

GitHub Config

Code

If New

IF

Send Message

Slack

Edit Fields

Set

If No Error

IF

Information Extractor

@n8n/n8n-nodes-langchain.informationExtractor

Redis Set Id

Redis

Limit

Limit

Loop

SplitInBatches

Null

Set

Send Error

Slack

If Not Empty

IF

Date Format

DateTime

Code for Slack Tpl

Code

RSS for Release

RssFeedRead

Redis Get

Redis

18 steps · flows top to bottom, branches left to right

Browse by integration

Browse all integrations →

Import into n8n

  1. Download the n8n JSON file (full or sanitized).
  2. In n8n: Workflows → Import from file.
  3. Open each node and reconnect credentials to your accounts.
  4. Test with manual execution before enabling triggers.

Sanitized JSON removes credential IDs — safer for sharing. Flow graph JSON is OpenRuna's lightweight format for diagrams and other tools, not n8n import.

View source corpus ↗

Overview

Free n8n workflow: Github Releases. 24 nodes across limit, splitInBatches, schedule, slack, dateTime, informationExtractor, lmChatGoogleGemini, redis, with a downloadable JSON and a visual flow diagram on OpenRuna.

What this workflow does

This n8n workflow, "Github Releases", wires together limit, splitInBatches, schedule, slack, dateTime, informationExtractor, lmChatGoogleGemini, redis in 24 nodes. 24 nodes · limit, splitInBatches, schedule, slack, dateTime, informationExtractor A scheduled/triggered entry point kicks it off, and each node passes data to the next until the run completes. OpenRuna shows the full flow diagram, an integration breakdown, and a one-click JSON export for n8n's "Import from file". Use it to learn integration patterns, fork it for your own use case, or deploy it quickly after reconnecting credentials.

Use cases

  • Import "Github Releases" into n8n, reconnect credentials for limit, splitInBatches, schedule, slack, dateTime, informationExtractor, lmChatGoogleGemini, redis, and run the same automation in your own workspace.
  • Use it as a starting template when wiring limit, splitInBatches, schedule, slack, dateTime, informationExtractor, lmChatGoogleGemini, redis — adjust node parameters to your accounts and record IDs.
  • Study how data moves from limit to splitInBatches before building your own variant.
  • Share it with your team as a documented reference for scheduled/triggered automations in the limit stack.

Example output

Imported into n8n, "Github Releases" exposes 24 configured nodes. Trigger type: scheduled/triggered. Integrations: limit, splitInBatches, schedule, slack, dateTime, informationExtractor, lmChatGoogleGemini, redis. Reconnect the limit credential first, then walk the remaining nodes top to bottom. Run it once in test mode to verify any branch logic (Switch/IF nodes) before enabling production triggers.

Tips by platform

Claude

Ask Claude to turn the "Github Releases" JSON into a plain-English runbook, node by node. It can flag where limit rate limits or missing retries might bite before you go live.

ChatGPT

Drop the workflow JSON or this OpenRuna page URL into ChatGPT and ask for a step-by-step runbook: triggers, branches, and which fields to customise for limit, splitInBatches, schedule, slack, dateTime, informationExtractor, lmChatGoogleGemini, redis. Handy for onboarding teammates new to n8n.

Cursor

In Cursor, ask Agent mode to parameterise "Github Releases" — extract limit IDs and secrets into environment variables without changing the 24-node structure.

Frequently asked questions

How do I import "Github Releases" into n8n?
Click Download n8n JSON on this page, then in n8n choose Workflows → Import from file and select the downloaded file. Reconnect credentials on each node — the export carries credential IDs from the original author's instance, not working secrets.
Which integrations does "Github Releases" use?
It uses: limit, splitInBatches, schedule, slack, dateTime, informationExtractor, lmChatGoogleGemini, redis. The flow diagram above shows how each service connects across the 24 nodes. Filter OpenRuna by integration to find related workflows and tools.
Can I import a sanitized export without credentials?
Yes. Use "Download sanitized JSON" to strip credential references before sharing internally. You will still add your own limit and splitInBatches credentials in n8n after import.
What trigger type does "Github Releases" use?
Trigger type: scheduled/triggered. After import, confirm the trigger node (webhook, schedule, or app event) matches your environment, then activate the workflow when you are ready to run it.
Is "Github Releases" free to use?
OpenRuna catalogs community n8n workflows under open licenses. Check the source corpus link for the original license; commercial use may require verifying the third-party API terms for limit, splitInBatches, schedule, slack, dateTime, informationExtractor, lmChatGoogleGemini, redis.

Related resources