Description
Overview
This automated workflow fetches and distributes the top 5 ranked Product Hunt projects posted within the last 24 hours, operating as a scheduled orchestration pipeline. Designed for developers and community managers, the workflow solves the problem of manually tracking trending Product Hunt entries by leveraging a time-based cron trigger to initiate hourly data retrieval.
It uses a GraphQL query node to request posts filtered by posting time and order, ensuring deterministic retrieval of the latest high-ranking projects. The workflow outputs structured project details directly to a Discord channel via webhook integration.
Key Benefits
- Hourly automation workflow eliminates manual monitoring of Product Hunt trends.
- No-code integration with GraphQL API enables precise data extraction and filtering.
- Event-driven analysis ensures only posts from the last 24 hours are considered.
- Structured message formatting simplifies consumption of top projects in Discord.
Product Overview
This automation workflow initiates every hour using a cron trigger to ensure timely updates. It executes a GraphQL query against the Product Hunt API to retrieve posts created within the last 24 hours, ordered by ranking, limited to the top 5 entries. The query dynamically calculates the date range at runtime, specifying “postedAfter” and “postedBefore” parameters in UTC format to filter posts accurately.
After obtaining the posts, the workflow processes the nested response by extracting the “edges” array containing individual post nodes. Each post node provides fields such as name, tagline, description, votesCount, and reviewsRating. The workflow then isolates key information—name, description, and vote count—using a Set node configured to keep only these fields.
Finally, the workflow dispatches formatted messages to a Discord channel via a webhook node, sending one message per project with standardized fields. This workflow relies on bearer token authentication for the GraphQL API and does not implement custom error handling; it defaults to platform retry behaviors if errors occur. There is no data persistence beyond transient processing within the execution.
Features and Outcomes
Core Automation
The core automation workflow triggers hourly to perform event-driven analysis of Product Hunt projects. It evaluates posts posted within the last 24 hours and filters them by ranking using a GraphQL query node.
- Deterministic hourly trigger ensures consistent data refresh.
- Single-pass evaluation of top 5 ranked posts within the time window.
- Structured extraction of project name, description, and vote count.
Integrations and Intake
This no-code integration pipeline connects directly to the Product Hunt GraphQL API, authenticated via a bearer token in the Authorization header. It ingests JSON-formatted query responses containing nested post data.
- GraphQL API integration for precise, filtered data retrieval.
- Cron node schedules hourly execution to maintain data relevance.
- Discord webhook delivers formatted messages for downstream consumption.
Outputs and Consumption
Outputs are formatted as plain text messages containing project name, description, and vote count. Messages are sent synchronously via Discord webhook, enabling immediate consumption in chat channels.
- Discord webhook outputs one message per top-ranked project.
- Message format includes clear labels for Name, Description, and Votes.
- Data is transient; no long-term storage or persistence is involved.
Workflow — End-to-End Execution
Step 1: Trigger
The workflow initiates once every hour using a cron node configured with an “everyHour” trigger mode. This scheduled event drives the entire data retrieval and delivery process.
Step 2: Processing
The GraphQL node sends a query to the Product Hunt API using dynamic date parameters to fetch posts from the last 24 hours, ordered by ranking. The response is parsed by the Item Lists node, which extracts the array of post edges. The Set node then maps relevant fields—name, description, votesCount—into a simplified structure for message formatting.
Step 3: Analysis
The workflow applies deterministic selection criteria by filtering posts posted after a calculated timestamp exactly 24 hours before execution. Posts are ordered by ranking and limited to the first five entries. No additional heuristics or machine learning models are used.
Step 4: Delivery
Each processed post is sent as an individual formatted message to a Discord channel through a webhook node. The messages are dispatched sequentially and synchronously during workflow execution, containing labeled fields for easy readability.
Use Cases
Scenario 1
A community manager needs to keep their Discord group informed about emerging Product Hunt projects without manual effort. By deploying this automation workflow, the manager receives hourly updates of the top 5 recent projects, enabling timely discussions and engagement.
Scenario 2
A developer wants to monitor competitive product launches daily. This orchestration pipeline provides a consistent feed of high-ranking Product Hunt posts from the past 24 hours, ensuring the developer is aligned with market trends through automated messages.
Scenario 3
A startup team requires an automated digest of trending tech projects to inform internal innovation meetings. This workflow collects and formats top-ranked posts every hour and delivers them directly to their Discord channel, streamlining information sharing.
How to use
To deploy this workflow in n8n, import the workflow JSON and configure the Discord webhook URL with valid credentials. Replace the GraphQL node’s Authorization header with a valid Product Hunt API bearer token. The cron node requires no modification for hourly scheduling.
Once enabled, the workflow will run automatically every hour, querying the Product Hunt API and sending formatted messages to Discord. Users can expect to see updates listing project names, descriptions, and vote counts with minimal setup.
Comparison — Manual Process vs. Automation Workflow
| Attribute | Manual/Alternative | This Workflow |
|---|---|---|
| Steps required | Multiple manual searches and message formatting steps | Single automated hourly process from data retrieval to delivery |
| Consistency | Variable due to human error and timing inconsistencies | Consistent hourly execution with deterministic post selection |
| Scalability | Limited by manual effort and time constraints | Scales automatically to hourly intervals without additional input |
| Maintenance | Requires ongoing manual effort and monitoring | Low maintenance; relies on stable API and webhook connectivity |
Technical Specifications
| Environment | n8n automation platform |
|---|---|
| Tools / APIs | Product Hunt GraphQL API, Discord Webhook |
| Execution Model | Scheduled (cron) synchronous workflow |
| Input Formats | GraphQL JSON response |
| Output Formats | Plain text messages via Discord webhook |
| Data Handling | Transient processing; no data persistence |
| Known Constraints | Requires valid API bearer token and Discord webhook URL |
| Credentials | Bearer token for Product Hunt API, webhook URL for Discord |
Implementation Requirements
- Valid Product Hunt API bearer token configured in GraphQL node header.
- Discord webhook URL configured in Discord node for message delivery.
- n8n instance with internet access to connect to API endpoints and webhook.
Configuration & Validation
- Confirm the cron node is set to trigger every hour without modification.
- Verify the GraphQL query uses dynamic date parameters and correct authorization header.
- Test workflow execution to ensure messages are posted correctly in the Discord channel.
Data Provenance
- Trigger node: Cron (everyHour) initiates timed execution.
- Data source: GraphQL node queries Product Hunt API with bearer token authorization.
- Output: Discord node sends formatted post details as text messages via webhook.
FAQ
How is the automated Product Hunt top posts workflow triggered?
The workflow is triggered by a cron node configured to run every hour, initiating the data retrieval and dispatch process automatically on a fixed schedule.
Which tools or models does the orchestration pipeline use?
The pipeline uses a GraphQL node to query the Product Hunt API with a structured query and a Discord node to send formatted messages. No additional models or machine learning components are involved.
What does the response look like for client consumption?
The workflow outputs plain text messages to Discord, each containing a project’s name, description, and vote count formatted for readability and easy consumption.
Is any data persisted by the workflow?
No data persistence is performed. All processing is transient within the workflow execution, and no project data is stored beyond message dispatch.
How are errors handled in this integration flow?
The workflow relies on n8n’s default error handling and retry mechanisms. No custom error handling or backoff strategies are explicitly configured.
Conclusion
This hourly automation workflow provides a deterministic method to track and share the top 5 ranked Product Hunt projects posted in the last 24 hours. By integrating scheduled triggers, a GraphQL API query, and Discord webhook delivery, it offers consistent updates without manual intervention. While it depends on the availability and responsiveness of the external API and webhook endpoints, the workflow ensures reliable, transient processing and formatted output for immediate consumption. This solution is suitable for teams and communities seeking systematic and structured updates on emerging products with minimal maintenance overhead.
Reviews
There are no reviews yet.