by System Admin
Tagged with: , , , ,
by System Admin
Tagged with: , , , ,
by System Admin
Tagged with: , , , ,
by Oneclick AI Squad
This automated n8n workflow provides real-time currency conversion by capturing GET requests via a webhook, parsing exchange rate data from Google Search, and returning a formatted response. The system handles query parameter validation and error cases to ensure reliable conversions. What is Real-Time Currency Conversion? Real-time currency conversion involves fetching the latest exchange rates from Google Search via HTTP requests, processing the data, and delivering a user-friendly conversion result based on a provided query parameter. Good to Know The workflow requires a valid query parameter (q) for conversion requests Google Search parsing depends on the availability and structure of search results Error handling is included for missing query parameters Responses are formatted for easy integration How It Works Webhook* - Captures GET requests with query parameter *q** Check Query Parameter** - Validates that the required query parameter exists Fetch Exchange Rate** - Makes HTTP request to Google search for exchange rates Error Response** - Handles missing query parameter errors Extract Conversion Data** - Processes HTML response to extract conversion data Format Currency Response** - Formats the result into a user-friendly response Send Conversion Response** - Returns the formatted response How to Use Import the workflow into n8n Configure the webhook to receive GET requests with a query parameter (q) Test the workflow with sample conversion queries (e.g., "1 USD to INR") Monitor for error responses and adjust query handling if needed Requirements Webhook configuration Internet access for Google Search requests Customizing This Workflow Adjust the query parameter validation in the Check Query Parameter node to support additional formats Modify the Format Currency Response node to change the output format based on user needs
by System Admin
Tagged with: , , , ,
by System Admin
Tagged with: , , , ,
by System Admin
Tagged with: , , , ,
by Camille Roux
Automatically publish Lightroom photos to Instagram with short, human-sounding AI captions. This workflow pulls the next item from your Data Table queue, generates an on-brand caption from alt text + metadata, uploads via Instagram Graph API, and marks it posted. Use it together with “Lightroom Cloud → Photos Queue (AI Alt Text)” and “Lightroom Image Webhook (Direct JPEG for Instagram).” What it’s for Hands-free Lightroom-to-Instagram posting: schedule, caption with AI, and publish consistently using the Instagram Graph API. Parameters to set Instagram Graph API access token and Instagram Business/Creator account ID Posting schedule (cron/interval) + max posts per run Data Table name & status fields (posted timestamp, IG media ID) Caption rules: tone, max length, hashtags policy, CTA style Image source URL: public endpoint of Workflow 2 (Lightroom Image Webhook) Works best with Workflow 1: Lightroom Cloud → Photos Queue (AI Alt Text) Workflow 2: Lightroom Image Webhook (Direct JPEG for Instagram) Learn more & stay in the loop Want the full story (decisions, trade-offs, and tips) behind this Lightroom Cloud → Instagram automation? 👉 Read the write-up on my blog: camilleroux.com If you enjoy street & urban photography or you’re curious how I use these n8n workflows day-to-day: 👉 Follow my photo account on Instagram: @camillerouxphoto 👉 Follow me on other networks: links available on my site (X, Bluesky, Mastodon, Threads)
by Robin Geuens
Overview Use this workflow to spot internal linking ideas on your site and improve your search performance. It takes your target URLs and keywords, finds related pages, and suggests where to add links. Strong internal linking helps search engines understand your site. How it works You provide a list of target URLs and the keywords you want to rank for The workflow uses the SERP API to search your site for related pages, skipping the target URL It filters the results and pulls relevant URLs It writes the suggestions to a Google Sheet, and adds “N/A” if no good matches are found Setup steps Turn on the Google Sheets API and create a sheet with your domain, target URLs, and keywords Create a SERP API account and get an API key Optional: Set up a Google Programmable Search Engine if you prefer not to use the SERP API Add your SERP API key and Google Sheets credentials to n8n. Run the workflow to generate internal link suggestions in your Google Sheet
by WeblineIndia
CI Artifact Completeness Gate (GitHub Push → Sentry Release Files → Artifact Validation → GitHub Commit Status Update) This workflow acts as a CI/CD quality gate for mobile app crash-symbolication artifacts. Whenever a new commit is pushed to GitHub, the workflow automatically checks the corresponding Sentry release and confirms whether required build artifacts (dSYM or ProGuard + mapping.txt) exist. If artifacts are complete, it updates the GitHub commit status to success, allowing the PR to be merged. If incomplete, the workflow fails silently (no commit status update), effectively blocking merges. ⚡ Quick Implementation Steps Configure GitHub Trigger for your repo. Add Sentry API credentials. Add GitHub API credentials. Update Sentry project URLs with your org_slug and proj_slug. Ensure your build pipeline uploads artifacts to Sentry before the workflow runs. Activate workflow. What It Does This workflow ensures your mobile crash-symbolication artifacts are fully present in Sentry for every release. When a new GitHub push occurs, the workflow: Reads the commit SHA and repo info from the GitHub Push event. Fetches the list of all releases from Sentry. Locates the correct release and fetches its uploaded artifact files. Runs custom validation logic: Success if: a .dSYM file exists *OR**\ both proguard.txt AND mapping.txt are present\ Failure if: neither dSYM nor both mapping artifacts exist. If validated successfully, the commit receives a success status on GitHub → PR can be merged. This provides a strong CI gate ensuring symbolication completeness and preventing un-debuggable releases. Who's It For Mobile development teams using Sentry for crash reporting. Engineering teams enforcing strict release-quality gates. DevOps teams wanting automated artifact validation. CI/CD pipeline engineers integrating Sentry symbolication checks. Teams who frequently upload dSYM or ProGuard mapping files. Requirements to Use This Workflow n8n instance (cloud or self-hosted) GitHub repository access (API credentials) Sentry project with: org_slug project_slug Auth Token with release access Build process that uploads artifacts to Sentry releases The release version must match the format expected by the workflow How It Works & How To Set Up Step 1: GitHub Push Trigger The GithubPushTrigger node listens for push events and extracts: Commit SHA Repository full name Branch Metadata No configuration required except selecting your GitHub credentials. Step 2: Configure Sentry Release Fetching Open Check Sentry Artifacts Releases and update: https://sentry.io/api/0/projects/<org_slug>/<proj_slug>/releases/ Make sure the Sentry credential is correctly selected. Step 3: Fetch Files for the Specific Release The next HTTP Request (Check Sentry Artifacts Files) uses a dynamic URL: https://sentry.io/api/0/projects/<org_slug>/<proj_slug>/releases/{{ $json.version }}/files/ Ensure your build pipeline sets version consistently with what Sentry receives. Step 4: Artifact Validation Logic The Verify Artifacts node runs JS logic to check: ✔ Condition 1 --- Valid dSYM Any file ending with .dSYM ✔ Condition 2 --- Valid Android Mapping proguard.txt\ mapping.txt ✖ Failure --- If neither set exists The Code node returns: { "status": "failure", "description": "Missing artifacts..." } This stops the workflow and prevents GitHub commit-status update. Step 5: Extract Commit Info & Prepare Update The Artifacts Validation and Get Repository Data node compiles: repo full name commit SHA validation status If validation failed → workflow ends here. Step 6: Update GitHub Commit Status The Update Status node hits: POST https://api.github.com/repos/<repoFullName>/statuses/<commitSHA> And sends: { "state": "success", "description": "Artifacts successfully verified." } This appears as a green check on your commit/PR. Step 7: Activate the Workflow Turn on the workflow to start enforcing symbolication completeness for all releases. How To Customize Nodes Change Sentry Project Edit URLs in both Sentry HTTP Request nodes: org_slug proj_slug Add Additional Artifact Rules Modify JS inside Verify Artifacts, e.g., require: native symbols extra asset files other platform artifacts Customize Commit Status Message Edit the request body in Update Status. Support Multiple Platforms / Multiple Releases Branch logic in: Code nodes Conditional checks Add-Ons (Optional Enhancements) Add Slack/Teams notifications when artifacts are missing. Auto-retry release checks after build completes. Merge-blocking PR checks for GitHub. Multi-platform artifact validation (iOS + Android + Unity). Upload artifacts directly from n8n. Store validation logs in Airtable or Google Sheets. Add GitHub Checks API rich reporting. Use Case Examples Block merges until symbolication artifacts are uploaded. Enforce strict Sentry release completeness for every build. Ensure Android mapping files always match the correct release version. Automatically verify multiple release types (debug, staging, production). Improve crash debugging by preventing un-symbolicated builds from shipping. Troubleshooting Guide | Issue | Possible Cause | Solution | |----------------------------|-----------------------------------------------|--------------------------------------------------------------------------| | Commit status never updates| Validation failed silently | Check logs from Verify Artifacts | | "version undefined" in URL | Sentry release list not matched | Ensure your build uploads a valid version | | 401 from Sentry API | Invalid/broken Sentry token | Regenerate token and update credentials | | Always failing validation | Artifact names differ (e.g., .dsym.zip) | Update RegEx patterns in Code node | | GitHub status API returns 404 | Missing repo permissions | Update GitHub credentials (repo status scope) | | Files array empty | Build system not uploading artifacts | Verify build → Sentry upload step | Need Help? If you need help customizing the artifact rules, integrating multiple platforms or automating Sentry/GitHub workflows, reach out to our n8n automation developers at WeblineIndia. We can assist with: Mobile CI/CD pipelines Sentry automation Multi-artifact validation GitHub PR quality-gates Advanced Code-node scripting And so much more. Happy automating! 🚀
by Dominic Spatz
🔄 Purpose of the Workflow: The Update-N8N workflow is designed to automatically trigger a (Portainer) webhook to update an N8N container, but only if a new version of N8N is available. ⚙️ Detailed Workflow Steps: 🕒 Scheduled Trigger The workflow runs every 16 hours at minute 8 using a schedule trigger node. 🌐 Fetch Latest N8N Version It sends an HTTP GET request to https://registry.npmjs.org/n8n/latest to retrieve the latest published N8N version from the npm registry. 📈 Get Currently Running Local Version Another HTTP GET request is sent to https://127.0.0.1/metrics (likely the Prometheus metrics endpoint of the local N8N instance) to extract the currently installed N8N version. 🧠 Version Comparison The workflow compares the local version (parsed from metrics) with the latest available version. 📬 Trigger Portainer Webhook If the versions do not match (i.e., an update is available), a POST request is sent to a webhook URL, which might be a Portainer webhook that redeploys or updates the N8N container/stack. ✅ Key Benefits: No manual checks or updates needed. Triggers only when a new version is available. Integrates seamlessly with Portainer via webhook. Secure configuration, e.g., disallowing unauthorized TLS certs for external requests.
by Yaron Been
This workflow provides automated access to the Digitalhera Heranathalie AI model through the Replicate API. It saves you time by eliminating the need to manually interact with AI models and provides a seamless integration for other generation tasks within your n8n automation workflows. Overview This workflow automatically handles the complete other generation process using the Digitalhera Heranathalie model. It manages API authentication, parameter configuration, request processing, and result retrieval with built-in error handling and retry logic for reliable automation. Model Description: Advanced AI model for automated processing and generation tasks. Key Capabilities Specialized AI model with unique capabilities** Advanced processing and generation features** Custom AI-powered automation tools** Tools Used n8n**: The automation platform that orchestrates the workflow Replicate API**: Access to the Digitalhera/heranathalie AI model Digitalhera Heranathalie**: The core AI model for other generation Built-in Error Handling**: Automatic retry logic and comprehensive error management How to Install Import the Workflow: Download the .json file and import it into your n8n instance Configure Replicate API: Add your Replicate API token to the 'Set API Token' node Customize Parameters: Adjust the model parameters in the 'Set Other Parameters' node Test the Workflow: Run the workflow with your desired inputs Integrate: Connect this workflow to your existing automation pipelines Use Cases Specialized Processing**: Handle specific AI tasks and workflows Custom Automation**: Implement unique business logic and processing Data Processing**: Transform and analyze various types of data AI Integration**: Add AI capabilities to existing systems and workflows Connect with Me Website**: https://www.nofluff.online YouTube**: https://www.youtube.com/@YaronBeen/videos LinkedIn**: https://www.linkedin.com/in/yaronbeen/ Get Replicate API**: https://replicate.com (Sign up to access powerful AI models) #n8n #automation #ai #replicate #aiautomation #workflow #nocode #aiprocessing #dataprocessing #machinelearning #artificialintelligence #aitools #automation #digitalart #contentcreation #productivity #innovation