Back to Catalog

Real-time currency conversion via webhook & Google search parsing

Oneclick AI SquadOneclick AI Squad
335 views
2/3/2026
Official Page

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

Real-time Currency Conversion via Webhook with Google Search Parsing

This n8n workflow provides a flexible way to perform real-time currency conversions by parsing Google search results. It listens for incoming webhook requests containing a specific query, executes a Google search for the currency conversion, extracts the conversion rate, and responds to the webhook with the result.

What it does

  1. Listens for Webhook Trigger: The workflow starts by waiting for an incoming HTTP POST request to a defined webhook URL.
  2. Performs Google Search: It takes the query from the incoming webhook and constructs a Google search URL to find the currency conversion rate (e.g., "1 USD to EUR").
  3. Fetches Search Results: An HTTP Request node is used to execute the Google search and retrieve the HTML content of the search results page.
  4. Parses Conversion Rate: A Code node then processes the HTML response to extract the actual currency conversion rate. It specifically looks for a pattern in the HTML that typically displays the conversion result.
  5. Responds to Webhook: Finally, the workflow sends the extracted conversion rate back to the caller of the webhook, allowing for real-time integration with other systems.

Prerequisites/Requirements

  • n8n Instance: A running n8n instance (cloud or self-hosted).
  • Google Search Access: The n8n instance needs to be able to make HTTP requests to Google search.
  • Basic JavaScript Knowledge (Optional): For understanding or modifying the "Code" node's parsing logic.

Setup/Usage

  1. Import the Workflow:
    • Copy the provided JSON code.
    • In your n8n instance, click "New" in the workflows list.
    • Click the "Import from JSON" button and paste the JSON code.
    • Click "Import".
  2. Activate the Workflow:
    • Ensure the workflow is activated by toggling the "Active" switch in the top right corner.
  3. Get Webhook URL:
    • The "Webhook" node (named "Webhook") will automatically generate a unique URL when the workflow is activated. Copy this URL.
  4. Send Requests:
    • Send an HTTP POST request to the copied Webhook URL. The request body should be JSON and contain a query field with the currency conversion you want to perform.
    • Example Request Body:
      {
        "query": "1 USD to EUR"
      }
      
    • The workflow will respond with the conversion rate.

Note: The parsing logic in the "Code" node relies on the structure of Google search results. If Google's search result page structure changes, the parsing logic might need to be updated.

Related Templates

Generate verified job offer letters with OpenAI, Gmail and Slack

📄 AI-Powered Verified Job Offer Letter Generator Description Creating job offer letters manually is time-consuming, error-prone, and difficult to scale. This AI-powered workflow automates the entire job offer letter process — from validating candidate emails to generating and delivering professional PDF offer letters. This intelligent workflow eliminates repetitive drafting, reduces human errors, and ensures offer letters are sent only to verified email addresses, helping HR teams move faster while maintaining professionalism and accuracy. --- What This Workflow Does Transforms manual offer letter creation into a seamless, automated HR process: 📝 Capture Candidate & Job Details – Receives candidate name, email, job role, salary, joining date, and company details via webhook or form. 📧 Email Verification – Validates the candidate’s email address before sending any communication to prevent delivery errors. 🧠 AI-Powered Offer Letter Generation – Uses AI to generate a clear, professional, and structured job offer letter. 📄 HTML Offer Letter Formatting – Converts the AI-generated content into a clean and readable HTML layout. 📑 PDF Generation – Automatically converts the offer letter into a professional PDF document. 📧 Offer Letter Delivery – Sends the PDF offer letter directly to the verified candidate email. 🗂️ Document Storage – Saves a copy of the offer letter for internal records and future reference. 🔁 Confirmation Response – Returns a success response confirming completion. --- Key Features 🤖 AI Offer Letter Writing – Generates professional, ready-to-send offer letters automatically. 📧 Email Verification Built-In – Ensures offer letters are only sent to valid email addresses. 📑 PDF Generation – Creates clean, official-looking offer letters. ⚙️ End-to-End Automation – No manual drafting, formatting, or sending required. 📂 Centralized Record Keeping – Keeps copies of all generated offer letters. 🔄 Flexible Triggering – Can be triggered from HR systems, forms, or internal tools. --- Perfect For 🏢 HR & Recruitment Teams – Automate offer letter creation and delivery. 🚀 Startups & Growing Companies – Send professional offer letters without extra admin work. 🏫 Staffing & Hiring Agencies – Generate offer letters quickly for multiple candidates. 💻 Remote & Distributed Teams – Ensure consistent communication across locations. 🧠 Operations Teams – Maintain accurate records and reduce manual errors. --- What You’ll Need Required Integrations 🌐 Webhook Trigger – Receives candidate and job details. 🤖 OpenAI – Generates offer letter content. 📧 VerifyEmail – Validates candidate email addresses. 📄 HTMLCSS to PDF – Converts HTML into PDF offer letters. 📧 Gmail – Sends the offer letter email. ☁️ Google Drive (optional) – Stores generated offer letters. --- Optional Enhancements 🎨 Brand Customization – Add company logo, colors, and formatting to offer letters. 🧾 HR System Integration – Connect with ATS or HR tools for automatic triggering. 🌍 Multilingual Offer Letters – Generate offer letters in different languages. 🔐 Approval Step – Add internal approval before sending offer letters. 📊 Audit Logging – Store offer letter data in Google Sheets or databases. 📎 Additional Attachments – Include policies or onboarding documents with the offer letter. --- Quick Start 1️⃣ Import the workflow template into your n8n workspace 2️⃣ Connect credentials for OpenAI, VerifyEmail, Gmail, and HTMLCSS to PDF 3️⃣ Send test candidate data to the webhook 4️⃣ Review the generated PDF offer letter 5️⃣ Activate the workflow and start sending offer letters automatically --- Customization Options 1️⃣ Offer Letter Tone – Adjust AI prompt for formal or friendly tone. 2️⃣ Company Branding – Customize HTML layout and styling. 3️⃣ Email Content – Modify subject line and email message. 4️⃣ PDF Layout – Adjust spacing, fonts, and structure. 5️⃣ Storage Location – Change where offer letters are saved. 6️⃣ Validation Rules – Extend email or input checks. --- Expected Results ⚡ Faster Hiring Process – Generate offer letters in minutes. 🤖 Consistent Quality – Every offer letter follows a professional format. 📧 Error-Free Delivery – Verified emails reduce failed communication. 🗂️ Organized Records – All offer letters stored automatically. 🏢 Professional Candidate Experience – Clean, official documents every time. --- Workflow Structure Visualization 📝 Candidate & Job Details ↓ 📧 Email Verification ↓ 🧠 AI Offer Letter Generation ↓ 📄 HTML Formatting ↓ 📑 PDF Conversion ↓ 📧 Email Delivery ↓ 🔁 Confirmation Response --- 🚀 Ready to Automate Job Offer Letters? Import this template today and let AI handle offer letter creation, verification, and delivery — so your team can focus on hiring the right talent faster. ✨ ---

Jitesh DugarBy Jitesh Dugar
5

Generate PDF documents from HTML with PDF Generator API, Gmail and Supabase

Who’s this for 💼 This template is designed for teams and developers who need to generate PDF documents automatically from HTML templates. It’s suitable for use cases such as invoices, confirmations, reports, certificates, or any custom document that needs to be created dynamically based on incoming data. What this workflow does ⚙️ This workflow automates the full lifecycle of document generation, from request validation to delivery and storage. It is triggered by a POST webhook that receives structured JSON data describing the requested document and client information. Before generating the document, the workflow validates the client’s email address using Hunter Email Verification to prevent invalid or mistyped emails. If the email is valid, the workflow loads the appropriate HTML template from a Postgres database, fills it with the incoming data, and converts it into a PDF using PDF Generator API. Once the PDF is generated, it is sent to the client via Gmail, uploaded to Supabase Storage, and the transaction is recorded in the database for tracking and auditing purposes. How it works 🛠️ Receives a document generation request via a POST webhook. Validates the client’s email address using Hunter. Generates a PDF document from an HTML template using PDF Generator API. Sends the PDF via Gmail and uploads it to Supabase Storage. Stores a document generation record in the database. How to set up 🖇️ Before activating the workflow, make sure all required services and connections are prepared and available in your n8n environment. Create a POST webhook endpoint that accepts structured JSON input. Add Hunter API credentials for email verification. Add PDF Generator API credentials for HTML to PDF conversion. Prepare a Postgres database with tables for HTML templates and document generation records. Set up Gmail or SMTP credentials for email delivery. Configure Supabase Storage for storing generated PDF files. Requirements ✅ PDF Generator API account Hunter account Postgres database Gmail or SMTP-compatible email provider Supabase project with Storage enabled How to customize the workflow 🤖 This workflow can be adapted to different document generation scenarios by extending or modifying its existing steps: Add extra validation steps before document generation if required. Extend delivery options by sending the generated PDF to additional services or webhooks. Enhance security by adding document encryption or access control. Add support for additional document types by storing more HTML templates in the database. Modify the database schema or queries to store additional metadata related to generated documents. Adjust the data mapping logic in the Code node to match your input structure.

Marián DanašBy Marián Današ
113

Sync Zendesk tickets with subsequent comments to Asana tasks

This workflow creates an Asana task when a new ticket is created in Zendesk. Subsequent comments on the ticket in Zendesk are added as comments to the task in Asana. Prerequisites Zendesk account and Zendesk credentials. Asana account and Asana credentials. Asana workspace to create tasks in. How it works The workflow listens for new tickets in Zendesk. When a new ticket is created, the workflow creates a new task in Asana. The Asana GID is then saved in one of the ticket's fields (in setup we call this "Asana GID"). The next time a comment is added to the ticket, the workflow retrieves the Asana GID from the ticket's field and adds the comment to the task in Asana. Setup This workflow requires that you set up a webhook in Zendesk. To do so, follow the steps below: In the workflow, open the On new Zendesk ticket node and copy the webhook URL. In Zendesk, navigate to Admin Center > Apps and integrations > Webhooks > Actions > Create Webhook. Add all the required details which can be retrieved from the On new Zendesk ticket node. The webhook URL gets added to the “Endpoint URL” field, and the “Request method” should match what is shown in n8n. Save the webhook. In Zendesk, navigate to Admin Center > Objects and rules > Business rules > Triggers > Add trigger. Give trigger a name such as “New tickets”. Under “Conditions” in “Meet ALL of the following conditions”, add “Status is New”. Under “Actions”, select “Notify active webhook” and select the webhook you created previously. In the JSON body, add the following: { "id": "{{ticket.id}}", "comment": "{{ticket.latestcommenthtml}}" } Save the Zendesk trigger. You will also need to set up a field in Zendesk to store the Asana GID. To do so, follow the steps below: In Zendesk, navigate to Admin Center > Objects and rules > Tickets > Fields > Add field. Use the number field option and give the field a name such as “Asana GID”. Save the field. In n8n, open the Update ticket node and select the field you created in Zendesk.

n8n TeamBy n8n Team
1060