See developer growth stats in one place. The workflow pulls live numbers from GitHub, npm, Docker Hub, and Product Hunt, then updates your internal dashboard on a set schedule. Teams use it to track community, package health, and launch traction without switching tools.

A scheduled job runs every minute. A configuration step stores your dashboard URL, auth token, and IDs for each source. The workflow calls Docker Hub for pulls and stars, npms.io for maintenance, popularity, and quality, the GitHub API for stars, forks, watchers, and open issues, and Product Hunt for rating, reviews, votes, and comments. Function nodes clean and format each response. Then HTTP posts send the right values to each widget endpoint with the auth token.

Setup is simple. Add your GitHub credential and a Product Hunt access token, then fill the configuration node with your package, repo, and post IDs. Expect faster reporting and fewer errors because numbers update every minute with no manual copy and paste. This fits growth reviews, weekly standups, investor updates, and open source project health checks.

• Scheduled run with a cron trigger that checks and updates every minute
• Central configuration for dashboard URL, auth token, and all source IDs
• Docker Hub data fetch for pull and star counts using HTTP requests
• npm package insights from npms.io for maintenance, popularity, and quality
• GitHub repository metrics for stars, forks, watchers, and open issues
• Product Hunt stats for rating, reviews, votes, and comments
• Function nodes that clean and format raw responses into dashboard ready values
• Secure updates to widget endpoints using an auth token in each POST

• Reduce manual metric checks from 30 minutes to 2 minutes per day
• Unify four data sources in one dashboard view
• Improve reporting accuracy by removing copy and paste errors
• Get near real time updates every minute for faster decisions
• Scale to more repos and packages by changing IDs in one place

1. Import the template into n8n: Create a new workflow in n8n > Click the three dots menu > Select 'Import from File' > Choose the downloaded JSON file.
2. You'll need accounts with GitHub, Product Hunt, Docker Hub and npms.io. See the Tools Required section above for links to create accounts with these services.
3. Open the Dashboard Configuration node and fill the fields: dashboardHostname, dashboardAuthToken, product_hunt_post_id, npm_package, docker_name, docker_repository, and your GitHub owner and repo values.
4. Connect GitHub: double click the GitHub node, open the Credential to connect with dropdown, click Create new credential, then follow the on screen steps to authorize your GitHub account.
5. Set up Product Hunt access: double click the Retrieve Product Hunt Data node, add your access token in the Authorization header if required. Create the token from the API page in your Product Hunt account.
6. No login is needed for public Docker Hub and npms.io reads. Keep the User Agent header as set in the HTTP Request nodes.
7. Test each source: select the Retrieve Docker Data node and click Execute Node. Repeat for Retrieve npm Data, GitHub, and Retrieve Product Hunt Data to confirm valid responses.
8. Validate dashboard posting: run the workflow once and check that each widget endpoint returns a 200 response in the execution logs.
9. Open your dashboard and confirm values update for Docker, npm, GitHub, and Product Hunt widgets.
10. Adjust the Cron node if you want a different schedule. Save and activate the workflow.
11. Troubleshoot common errors: 401 means the dashboardAuthToken or Product Hunt token is wrong. 404 often means a bad repo, package, or post ID. Fix the value in the configuration node and test again.