Audun
I’m an automagician who loves turning complex systems into simple, powerful workflows. Here to help you automate smarter and work easier.
Templates by Audun
Monitor data breaches in real-time with Have I Been Pwned
[](https://xqus.relezy.com/haveibeenpwnedcom-breaches) Who is this for? Security professionals Developers Individuals interested in data breach awareness Use Case Automated monitoring for new breaches Proactive identity protection Demonstration of simple cache mechanism What this workflow does Checks the Have I Been Pwned API every 15 minutes for the latest breaches. Compares new breach data against previously notified breaches. Demonstrates a simple cache mechanism to track previously seen breaches. How the Cache Functionality Works Read from Cache: Retrieves the last known breach from cache.json to avoid redundant alerts for the same breach. Compare Against Current Breach: The workflow checks if the latest fetched breach differs from the cached one. Update the Cache: If a new breach is detected, it updates cache.json with the latest breach data. Setup instructions The endpoint used in this workflow does not require an API key. Add your desired alert mechanism in the red box attached to the New breach node. How to customize this workflow to your needs Modify Notification Settings: Tailor where alerts are sent (email, Slack, etc.). Add the desired node after the New breach node. This node contains all the data from the breach so it is eaisily available. You can choose from a variety of n8n nodes to send alerts when a new breach is detected. Below are a few common options you might consider adding after the New breach node: Email Node What it does: Sends an email notification to one or more recipients. Use case: Great for simple alerts to your inbox or a team distribution list. Customization: You can include breach details in the subject or body of the email, using data from the New breach node. Slack Node What it does: Sends a message to a Slack channel or user. Use case: Perfect for real-time alerts to your team in Slack. Customization: You can post breach details directly in a channel or DM. You can also format the message (bold, code blocks, etc.). Microsoft Teams Node What it does: Sends a message to a Teams channel. Use case: For organizations that use Microsoft Teams for communication. Customization: Similar to Slack, you can customize the message content and include all relevant breach information. Discord Node What it does: Sends an alert message to a Discord channel. Use case: Useful for teams or communities that coordinate via Discord. Customization: Add formatted messages with breach details for easy viewing. Telegram Node What it does: Sends messages to a Telegram chat or group. Use case: Good for mobile notifications and fast alerts. Customization: You can include breach summaries or detailed information, and even use bots to automate this. Webhook Node (as a sender) What it does: Sends breach data to another service via a webhook. Use case: If you have an external system or app that handles alerts, you can push the data directly to it. Customization: Send JSON payloads with detailed breach information to trigger actions in other systems. SMS Nodes (like Twilio) What it does: Sends an SMS notification to one or more phone numbers. Use case: For urgent alerts that need to be seen immediately. Customization: Keep messages concise, including key breach details like the time, type of breach, and affected system. Adjust Check Frequency: Change the interval in the Schedule Trigger node (e.g., hourly or daily).
By AudunExtract internal links from a webpage
[](https://xqus.relezy.com/extract-internal-links-from-webpage) Who Is This For? Web developers SEO specialists Digital marketers What Problem Is This Workflow Solving? Automates the extraction of internal links from a webpage Eliminates the manual and error-prone process of collecting links Facilitates analysis of website structure and optimization What This Workflow Does Uses HTTP request node to fetch HTML content from a specified webpage Parses the HTML to identify and extract internal links Compiles a list of URLs directing to pages within the same domain Setup Configure the Set Base URL node: Set the url field to the URL you want to analyze. How to Customize This Workflow to Your Needs Change the target URL in the Set Base URL node to analyze different webpages. Add nodes to: Filter or categorize the extracted links Export the list to a database or CSV Send links via email or integrate with other tools This workflow can be used as a base for workflows to manage the process of extracting internal links, aiding in website optimization and SEO efforts.
By AudunExtract & process specific links from sitemap.xml
Description This workflow reads a sitemap.xml file, extracts all URLs, and allows you to filter out specific types of links—such as PDF files, images, or any other content—based on your needs. Who Is This For? SEO Specialists looking to analyze specific URLs in their sitemap. Developers who need to extract links for automated processing. Content Managers filtering out downloadable assets like PDFs or images. How It Works Fetch sitemap.xml – The workflow reads the sitemap file from a given URL. Extract URLs – Parses all the URLs listed in the sitemap. Filter URLs – Use a simple filter to extract only the links you need (e.g., *.pdf). Export or Process – The filtered list can be sent via email, stored in a database, or used in another workflow. Customization Edit the Set sitemap URL block and edit the sitemapUrl value to the sitemap you want to fetch. Edit the Filter URLs block and edit the filter conditions to meet your needs.
By AudunGenerate images from text prompts with Google Imagen 3 via Replicate API
Who is this for? This n8n workflow is designed for developers, digital artists, and content creators who want to leverage the power of AI-generated images using the Replicate API. What problem is this workflow solving? / Use case The workflow automates the process of generating images from textual prompts using the Replicate API. It allows users to generate, check the status of, and retrieve images with minimal manual intervention. What this workflow does Initialize Workflow: Triggered by a manual click, the workflow starts with a prompt for image generation. Set Image Generation Parameters: The user can define a prompt and other parameters, which will be sent to the Replicate API for processing. Create Prediction: The workflow sends a request to generate an image based on the provided input. Check Prediction Status: After a short waiting period, the workflow checks the status of the image generation process. Handle Errors: If the status indicates an error (e.g., "failed" or "canceled"), the workflow stops and reports an error. Retrieve Image URL: If the image generation is successful, it retrieves and outputs the URL of the generated image. Setup Replicate API Key: Go to the Replicate website and sign up for an account if you don’t have one. Generate an API key from your Replicate dashboard. Configure HTTP Credentials: In n8n, navigate to the "Credentials" section and create a new HTTP Header Authentication credential. Set the name to Authorization, and enter Bearer YOURREPLICATEAPIKEY in the value field, replacing YOURREPLICATEAPIKEY with your actual API key. How to customize this workflow to your needs Edit the Prompt Text: Change the text in the "Set prompt" node to customize the image you want to generate. This can be adjusted to include dynamic input from other parts of your n8n workflow. Change Image Generation Settings: In the "Create prediction" node, you may modify any parameters such as aspect ratio, safety filter level, or even the model being used by changing the URL. Add More Logic: If you want to add more complex logic or branching conditions based on the image generation results, modify the "Check for success" and "Check for errors" nodes accordingly. Modify Wait Duration: Depending on your application, you may want to adjust the waiting times in the "Wait" and "Pause" nodes to optimize processing time based on expected image generation speed.
By AudunSecure API endpoint with bearer token authentication and field validation
A reusable and production-ready n8n workflow that secures public webhooks using Bearer Token authentication and dynamic request validation. --- ✨ What It Does Verifies Bearer Token Compares the Authorization header with a configured secret token. Validates Required Fields Checks that all expected fields are present in the incoming request body. Returns Standardized JSON Responses 401 Unauthorized if token is missing or invalid 400 Bad Request if required fields are missing 200 OK with a custom success payload --- 👤 Who It’s For Developers exposing n8n workflows as APIs No-code/low-code builders integrating with external forms or tools Anyone needing simple authentication and validation on incoming webhooks --- 💡 Why Use It 🔒 Secure: Prevents unauthorized access to your public workflows 🧼 Clean: Centralized configuration for token and required fields ⚙️ Flexible: Easy to extend and customize for any use case --- 🛠 Setup Instructions Configure Values in the Configuration Node Set your secret token: config.bearerToken = YOUR_TOKEN Define required request fields by key: Example: config.requiredFields.message = true; config.requiredFields.email = true; ✅ Only the keys matter – values can be anything. Plug in Your Business Logic Replace the "Add workflow nodes here" with your own logic. Customize the Success Response Edit the Create Response node to shape your success payload. --- 🧪 Use Cases Securing public form submissions Creating internal API endpoints Validating data from external services --- 📌 Use this as a base for building secure, API-style workflows in n8n. --- 👋 Hello! I'm Audun / xqus If my n8n workflows saved you time or sparked ideas, consider sending a little support my way. It helps me keep building cool stuff — and maybe grab a coffee ☕ along the way!
By AudunSend structured logs to BetterStack from any workflow using HTTP request
Send structured logs to BetterStack from any workflow using HTTP Request Who is this for? This workflow is perfect for automation builders, developers, and DevOps teams using n8n who want to send structured log messages to BetterStack Logs. Whether you're monitoring mission-critical workflows or simply want centralized visibility into process execution, this reusable log template makes integration easy. What problem is this workflow solving? Logging failures or events across multiple workflows typically requires duplicated logic. This workflow solves that by acting as a shared log sender, letting you forward consistent log entries from any other workflow using the Execute Workflow node. What this workflow does Accepts level (e.g., "info", "warn", "error") and message fields via Execute Workflow Trigger Sends the structured log to your BetterStack ingestion endpoint via HTTP Request Uses HTTP Header Auth for secure delivery Includes a manual trigger for testing and a sample call to demonstrate usage Comes with clear sticky notes to help you get started Setup Copy your BetterStack Logs ingestion URL. Create a Header Auth credential in n8n with your Authorization: Bearer YOURAPIKEY. Replace the URL in the HTTP Request node with your BetterStack endpoint. Optionally modify the test data or log levels for custom scenarios. Use Execute Workflow in any of your workflows to send logs here.
By AudunProcess Ko-fi donations, subscriptions & shop orders with webhook verification
Who is this for? This workflow is tailored for content creators, artists, and developers who use Ko-fi to receive financial support through donations, subscriptions, or product sales. Use case This workflow automates the process of receiving and categorizing payment notifications from Ko-fi, ensuring that creators can focus on their work rather than administrative tasks. What this workflow does Webhook Reception: The workflow listens for incoming payment notifications from Ko-fi via a configured webhook. Token Verification: It validates incoming requests to ensure they originate from Ko-fi using a verification token for enhanced security. Type Differentiation: It categorizes payments into types—donations, subscriptions, and shop orders—allowing for tailored handling for each payment type. Custom Response Options: Depending on the payment type received, the workflow activates specific actions or processes, enabling seamless integration with other applications or services. Setup Webhook Configuration: Access the Webhook node within the workflow and take note of your unique webhook URL. Visit your Ko-fi webhooks management page at Ko-fi Webhooks Management and input this URL. Verification Token Setup: In your Ko-fi account, locate the verification token in the advanced settings. Input this token in the Prepare node of your n8n workflow. Enable the Workflow: Activate the workflow in n8n to start listening for incoming webhook notifications. Testing: Use the test feature in the Ko-fi webhooks settings to send a test webhook to ensure everything is functioning as expected. How to customize this workflow to your needs Add Actions for Each Payment Type: You can modify the Donation, Subscription, and Shop Order nodes to include actions such as sending emails, logging payments within a database, or triggering notifications. Enhance Security Measures: You can further refine the Check token node to include additional checks or to log all incoming webhook requests for monitoring. Integration with Other Services: Consider linking this workflow with messaging platforms (e.g., Slack, Discord) or CRM tools to keep your supporters informed or to manage relationships more effectively. Custom Fields: If needed, adjust the fields captured in the Subscription and Shop Order nodes to include more data or different parameters based on your specific use case.
By AudunCreate or find Stripe customers and automatically generate invoices
Save hours of manual billing work with this Stripe automation workflow! Designed for entrepreneurs, SaaS founders, and online business owners, this template checks if a customer already exists in Stripe based on their email. If no customer is found, it automatically creates a new one, generates a draft invoice, adds a product line item using a Stripe Price ID, and finalizes the invoice — making it ready for payment. This workflow helps ensure clean customer data and efficient billing without manual input. How it works Search Stripe for an existing customer based on the provided email address. If no customer is found, create a new one in Stripe automatically. Generate a draft invoice associated with the customer. Add a line item to the invoice using a Stripe Price ID. Finalize the invoice to make it ready to send or collect payment. Set up steps Stripe account setup: Ensure you have a valid Stripe account. Create a restricted Stripe API key with permissions to read and write Customers, Invoices, and Invoice Items. Connect Stripe to n8n: Set up an HTTP Basic Auth credential in n8n using your Stripe secret API key. No username is needed; the API key goes into the password field. Customize dynamic data: Replace the sample email (test@example.com) with your real dynamic customer email input. Replace the example Price ID (price_fromStripeDashboard) with your actual product Price ID from the Stripe dashboard. Test your workflow: Manually trigger the workflow inside n8n to ensure customers and invoices are being created correctly. Check your Stripe dashboard to confirm that new customers and invoices appear as expected. Deploy to production: Integrate this workflow with a real trigger (e.g., webhook, form submission) to automate the process live. Troubleshooting Invalid API Key: Double-check that your Stripe API key is active and has the necessary permissions. Test it by making a simple API call manually if needed. Invoice Creation Fails: Make sure you are using a valid Price ID from Stripe. The price must be active and available for the correct product. Customer Not Found Error: If the search fails due to formatting issues, ensure emails are valid and the query syntax matches Stripe's customer search format. Authentication Errors: If authentication fails, ensure you have selected HTTP Basic Auth in the HTTP Request nodes and left the username field empty. Stripe prerequisites You must have at least one active Price object created in your Stripe dashboard. Your Stripe account must be live or have access to test mode if you're working in development. Ensure your account has API access enabled for Customers, Invoices, and Products.
By Audun