OpenRuna
Sign in
← Workflows

Dashboard

24 nodes · cron, httpRequest, github

Engine
n8n
Nodes
24
Trigger
scheduled/triggered
Source file
1107_HTTP_GitHub_Automation_Webhook.json

Workflow flow

IntegrationsCronHTTPGitHubSetFunction
100%

Cron

Cron

Dashboard Configuration

Set

Retrieve Docker Data

HTTP

Retrieve npm Data

HTTP

GitHub

GitHub

Retrieve Product Hunt Data

HTTP

Massage npm Data

Function

Massage Product Hunt Data

Function

Massage Docker Data

Function

Massage GitHub Data

Function

Docker Pulls

HTTP

Docker Stars

HTTP

GitHub Watchers

HTTP

GitHub Forks

HTTP

GitHub Open Issues

HTTP

GitHub Stars

HTTP

npm Maintenance

HTTP

npm Popularity

HTTP

npm Quality

HTTP

npm Final

HTTP

Product Hunt Rating

HTTP

Product Hunt Reviews

HTTP

Product Hunt Votes

HTTP

Product Hunt Comments

HTTP

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

Browse by integration

cronhttpRequestgithub
Browse all integrations →
Download n8n JSONDownload sanitized JSONDownload flow graph

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: Dashboard. 24 nodes across cron, httpRequest, github, with a downloadable JSON and a visual flow diagram on OpenRuna.

What this workflow does

This n8n workflow, "Dashboard", wires together cron, httpRequest, github in 24 nodes. 24 nodes · cron, httpRequest, github Execution begins at the scheduled/triggered trigger and flows through the 24 configured nodes. On OpenRuna you get the visual graph, the integration list, and a downloadable JSON ready to import into n8n. Use it to learn integration patterns, fork it for your own use case, or deploy it quickly after reconnecting credentials.

Use cases

  • Fork it to add error handling, retries, or a notification step without designing the 24-node flow from scratch.
  • Benchmark it against your current cron integration to spot missing steps or redundant nodes.
  • Import "Dashboard" into n8n, reconnect credentials for cron, httpRequest, github, and run the same automation in your own workspace.
  • Use it as a starting template when wiring cron, httpRequest, github — adjust node parameters to your accounts and record IDs.

Example output

Imported into n8n, "Dashboard" exposes 24 configured nodes. Trigger type: scheduled/triggered. Integrations: cron, httpRequest, github. Set your credentials on the cron node, then verify each downstream node picks them up. 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 "Dashboard" JSON into a plain-English runbook, node by node. It can flag where cron 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 cron, httpRequest, github. Handy for onboarding teammates new to n8n.

Cursor

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

Frequently asked questions

How do I import "Dashboard" 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 "Dashboard" use?
It uses: cron, httpRequest, github. 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 cron and httpRequest credentials in n8n after import.
What trigger type does "Dashboard" 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 "Dashboard" 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 cron, httpRequest, github.

Related resources