Public Webhook Relay
This workflow receives external POST requests through a public Webhook and automatically forwards them to local processes. It periodically polls for new requests, automatically manages authorization tokens and request statuses, ensuring reliable data transmission. Users can securely receive and process Webhook notifications in a local environment without the need to set up a public server, making it suitable for various scenarios such as development, testing, and data forwarding, significantly improving work efficiency and lowering technical barriers.
Tags
Workflow Name
Public Webhook Relay
Key Features and Highlights
This workflow leverages the public webhook receiving interface provided by webhook.site to automatically forward external POST requests to a local n8n workflow. It supports scheduled polling to check for new requests, automatic management of access tokens and request statuses, ensuring reliable transmission of request data.
- Automatically obtains and stores authorization tokens
- Scheduled polling (default every 10 seconds) to detect new webhook requests
- Filters unprocessed POST requests to avoid duplicate handling
- Forwards request content intact to a specified local webhook endpoint
- Supports local persistent storage (based on the community Key-Value storage node)
- Fully visualized workflow for easy debugging and extensibility
Core Problem Addressed
Solves the challenge of exposing a public webhook endpoint directly from a local environment by using webhook.site as a public entry point. This enables secure relay and forwarding of external requests without the need for complex public server deployment or security configurations, thereby improving development and testing efficiency.
Use Cases
- Receiving external webhook notifications in local development or private intranet environments
- Testing webhook data sent by third-party services without setting up a public server
- Quickly building a webhook relay service integrated into existing n8n automation workflows
- Debugging and forwarding data for enterprise intranet system external interfaces
Main Workflow Steps
- Schedule Trigger: Initiates the workflow on a schedule, defaulting to every 10 seconds
- Reads the locally stored authorization token and checks its existence
- If no token is found, calls the webhook.site API to obtain a new token and stores it
- Uses the token to query the latest request data from webhook.site
- Filters unprocessed POST requests based on timestamp and request method
- Aggregates and processes the filtered request data
- Records the timestamp of the latest processed request for subsequent filtering
- Forwards the request content via HTTP POST to the locally configured webhook URL
- Completes data relay and waits for the next polling cycle
Involved Systems or Services
- webhook.site: Public webhook receiving and storage service
- n8n Community Key-Value Storage Node (@horka.tv/n8n-nodes-storage-kv): Used for local persistent storage of authorization tokens and last processed timestamps
- n8n HTTP Request Node: Handles API calls to webhook.site and request forwarding
- Local n8n workflow webhook endpoint
Target Users and Value
- Automation developers and test engineers: Receive and test external webhook requests without requiring a public network environment
- Enterprise internal development teams: Securely and reliably forward intranet webhook data, minimizing public exposure risks
- Users needing to quickly set up webhook relay services: Enables rapid configuration with reduced technical barriers
- Users aiming to integrate external webhook data into local n8n workflows
This workflow provides a concise and efficient solution for receiving webhooks in local environments by securely relaying requests through webhook.site. Combined with local storage for accurate data management, it suits a variety of automation and testing scenarios, significantly enhancing work efficiency.
Multi-File Download and Merge Example Workflow
This workflow enables the automatic batch download of multiple specified URL files and merges the individual binary file data into a unified data item, simplifying the file processing process. By manually triggering the workflow, users can conveniently download the required resources, avoiding the inefficiencies and error risks associated with downloading files one by one. It is applicable in various scenarios such as marketing, content management, and data analysis, significantly enhancing work efficiency.
Workflow Importer
This workflow enables the automatic import of workflows from local files or remote instances. It supports reading and parsing JSON format files, simplifying the migration process across instances or from local files. Users can select the target workflow and manage credential mapping to ensure the validity and security of the imported credentials. The workflow provides instant feedback, enhancing the user experience, and is particularly suitable for team collaboration, workflow sharing, and batch import scenarios, effectively reducing the risks associated with manual operations.
Sse Automation Triggered
This workflow uses an SSE (Server-Sent Events) trigger to receive event pushes from a specified URL in real-time. It is designed to continuously listen for server events and respond automatically, making it suitable for scenarios that require real-time data updates. The process is straightforward, consisting of only one SSE trigger node, making it ideal for developers, operations personnel, and business teams looking to automate responses to external events. Overall, this workflow helps build real-time monitoring and event-driven automation processes, enhancing response speed and operational efficiency, and can be further expanded to achieve complex automation task chains.
n8n Subworkflow Dependency Graph & Auto-Tagging
This workflow automatically analyzes and constructs a dependency graph between workflows, helping users identify the callers of sub-workflows and automatically tagging them. Through visual charts, users can intuitively understand the call frequency and structure between workflows, reducing maintenance costs and preventing operational errors. At the same time, this workflow is suitable for teams and enterprises managing complex automation processes, enhancing workflow management efficiency and ensuring the stability and healthy development of processes.
Backup to GitHub
This workflow automatically backs up all workflow configurations to a specified GitHub repository, ensuring data security and version control. Triggered either on a schedule or manually, the workflow processes configuration files one by one, checking for differences with the files on GitHub and performing the corresponding create or update operations. This process effectively manages workflows, prevents data loss, and saves storage resources, making it suitable for teams and individuals that require regular backups and version management.
GitHub Repository Update Triggered Smart Lighting Alert
This workflow enables automatic switching of lights to red through a smart home system when updates occur in a GitHub repository. This physical feedback allows team members to instantly notice code changes, avoiding the neglect and delays associated with traditional notification methods, thereby enhancing response efficiency. It is suitable for software development teams, individual developers, and tech enthusiasts, enhancing the integration of work with smart home environments and improving collaboration and management efficiency.
screenshot
This workflow can automatically generate standard screenshots and full-page screenshots of specified web pages, then upload these screenshots to Dropbox and send them via email to designated users. It simplifies the cumbersome process of manually capturing, organizing, and sending emails, enhancing the efficiency of web screenshot capture and sharing. It is suitable for professionals such as product managers, testing engineers, and marketers who need to regularly obtain and distribute web screenshots. With a one-click trigger, it achieves a high level of automation, saving time and labor.
GitHub Star Change Notification
This workflow can monitor the changes in the number of Stars for a specified GitHub repository in real-time, automatically identifying events of new Stars and Star removals. It sends detailed notifications through a Slack channel, including the avatar, username, and link of the triggering user, helping open source project maintainers stay informed about changes in the project's popularity and improving their responsiveness to user interactions. It is suitable for open source teams, community managers, and product operators.