Skip to content
FlowHubFluxonLab
GitHub
GitHubfree

Display project data on a smashing dashboard

by jasonadapted from n8n official workflow galleryUpdated Aug 2026
RequiresGitHubGitHubHTTP RequestHTTP Request
Share Post Share
CrCronSeDashboard ConfigurationDashboard Confi…HRRetrieve Docker DataRetrieve Docker…HRDocker PullsHRDocker StarsHRRetrieve npm DataRetrieve npm Da…HRGitHub WatchersHRGitHub ForksHRGitHub Open IssuesGitHub Open Iss…HRGitHub StarsHRnpm MaintenanceHRnpm PopularityHRnpm QualityHRnpm FinalHRProduct Hunt RatingProduct Hunt Ra…HRProduct Hunt ReviewsProduct Hunt Re…HRProduct Hunt VotesProduct Hunt Vo…HRProduct Hunt CommentsProduct Hunt Co…GitHubHRRetrieve Product Hunt DataRetrieve Produc…FuMassage npm DataFuMassage Product Hunt DataMassage Product…FuMassage Docker DataMassage Docker …FuMassage GitHub DataMassage GitHub …1234567891011121314151617181920212223
1/5
STEPS · 23
Runs on a schedule

This workflow will gather data every minute from the GitHub (https://github.com), Docker (https://www.docker.com/), npm (https://www.npmjs.com/) and Product Hunt (https://www.producthunt.com/) website APIs and display select information on a Smashing (https://smashing.github.io/) dashboard. For convenience sake, the dashboard piece can be easily downloaded as a docker container (https://hub.docker.com/r/tephlon/n8n_dashboard) and installed into your docker environment.

Tags

n8nreference-onlygithub
Connects
githubGitHubWHTTP Request
CategoryGitHub
Triggermanual
Complexitycomplex
Nodes24
AddedSep 29, 2020

Related workflows

See all GitHub
githubW
free

Save your workflows into a GitHub repository

Basics Provides a mechanism to save all your workflows into a github repository and path (of your choosing). These can then be shared through your entire org and used to track changes (if you make any sad 'oopsies'. Flow Obtains and creates listing of currently configured workflows. Iterates through each workflow looking at the following Github source (if present) Actual workflow code (from N8N) Workflow code is sorted and compared for any changes If changed (or new) the workflows are saved / archived into github. Configuration Most of the configuration is done in the Globals node which houses the repo detail for github nodes. The only other dependency is that it by default looks for a GitHub credential, if you use something other than that precise wording you will need to change the credential used on the respective nodes. We gave it 'Manage' rights, but that was only so that it was able to override a requirement for checks to complete? Most would probably only need 'Write' privileges. Background Well, so we initially started using N8N just as a kubernetes-based service housed with its DB running inside the pod. Worked great for getting to know N8N and we jut kept all our workflow

by Brian Burnett
githubW
free

Backup workflows to GitHub

Note: This workflow uses the internal API which is not official. This workflow might break in the future. The workflow executes every night at 23:59. You can configure a different time bin the Cron node. Configure the GitHub nodes with your username, repo name, and the file path. In the HTTP Request nodes (making a request to localhost:5678), create Basic Auth credentials with your n8n instance username and password.

by Harshil Agrawal
CgithubW
free

Back Up Your n8n Workflows To Github

This workflow will backup your workflows to Github. It uses the public api to export all of the workflow data using the n8n node. It then loops over the data checks in Github to see if a file exists that uses the workflow name. Once checked it will then update the file on Github if it exists, Create a new file if it doesn't exist and if it's the same it will ignore the file. Config Options repo_owner - Github owner repo_name - Github repository name repo_path - Path within the Github repository >This workflow has been updated to use the n8n node and the code node so requires at least version 0.198.0 of n8n

by Jonathan