This article provides a complete, practical walkthrough of the Code Manual Process Webhook n8n agent. It connects HTTP Request, Webhook across approximately 1 node(s). Expect a Intermediate setup in 15-45 minutes. One‑time purchase: €29.

What This Agent Does

This agent orchestrates a reliable automation between HTTP Request, Webhook, handling triggers, data enrichment, and delivery with guardrails for errors and rate limits.

It streamlines multi‑step processes that would otherwise require manual exports, spreadsheet cleanup, and repeated API requests. By centralizing logic in n8n, it reduces context switching, lowers error rates, and ensures consistent results across teams.

Typical outcomes include faster lead handoffs, automated notifications, accurate data synchronization, and better visibility via execution logs and optional Slack/Email alerts.

How It Works

The workflow uses standard n8n building blocks like Webhook or Schedule triggers, HTTP Request for API calls, and control nodes (IF, Merge, Set) to validate inputs, branch on conditions, and format outputs. Retries and timeouts improve resilience, while credentials keep secrets safe.

Third‑Party Integrations

• HTTP Request
• Webhook

Import and Use in n8n

1. Open n8n and create a new workflow or collection.
2. Choose Import from File or Paste JSON.
3. Paste the JSON below, then click Import.
4. Show n8n JSON

   Title:
   Automate Image Conversion from JPG/PNG to WEBP with n8n and APYHub
   
   Meta Description:
   Learn how to automate image conversion from JPG or PNG to WEBP using n8n, Google Sheets, Google Drive, and the APYHub API. Ideal for optimizing images for web use and streamlining digital workflows.
   
   Keywords:
   n8n workflow, image conversion, JPG to WEBP, PNG to WEBP, APYHub API, Google Sheets automation, Google Drive, webp optimization, file format conversion, no-code automation
   
   Third-party APIs used:
   
   1. APYHub API - For converting JPG/PNG images to WEBP format
   2. Google Sheets API - For reading and updating image data
   3. Google Drive API - For uploading the converted WEBP images
   
   Article:
   
   Streamline Your Image Conversion Workflow with n8n and APYHub
   
   As the digital world increasingly emphasizes performance and user experience, the need for optimized media assets is greater than ever. One of the most effective ways to improve website load speed is to convert images into more efficient formats like WEBP, which offers superior compression without compromising quality.
   
   While manually converting images may seem manageable for occasional use, it quickly becomes tedious when dealing with hundreds or thousands of assets. Enter n8n — an extendable workflow automation tool that, when combined with services like APYHub, Google Sheets, and Google Drive, allows you to fully automate the image conversion process.
   
   In this article, we’ll showcase a powerful n8n workflow that automates converting JPG and PNG images to the WEBP format. It pulls image URLs from a Google Sheet, performs the conversion using the APYHub API, and uploads the output to Google Drive — without requiring a single line of manual labor once it’s set up.
   
   Overview of the Workflow
   
   Here’s a quick breakdown of what this n8n workflow accomplishes:
   
   1. Retrieves image URLs listed in a Google Sheet.
   2. Detects the file format (JPG, JPEG, or PNG).
   3. Uses the APYHub API to convert these to WEBP.
   4. Updates the Google Sheet with the converted image URL.
   5. Downloads the converted image.
   6. Uploads the resulting WEBP file to a designated Google Drive folder.
   
   Initial Setup
   
   Before using this workflow, you need to complete two preliminary steps:
   
   1. Get your free API key from APYHub (https://apyhub.com/).
   2. Clone this Google Sheet template and populate the “FROM” column with the image URLs (in jpg, jpeg, or png format): [Google Sheet Template](https://docs.google.com/spreadsheets/d/1upj3EDLwU1N7NHWWV3DhwMuE6ty39tIK5z5lCVDWWuM/edit?usp=sharing)
   
   Key Workflow Components
   
   Manual Trigger
   
   The workflow starts with a Manual Trigger node, allowing you to test and execute the workflow on demand during development or debugging stages.
   
   Set API Key
   
   A 'Set' node is used to insert your APYHub API key into the flow. This allows all HTTP requests to APYHub to be authenticated.
   
   Fetch Image URLs from Google Sheets
   
   Using the Google Sheets API node, the workflow reads image URLs from a pre-defined spreadsheet where only rows without a “DONE” flag are selected. This ensures previously processed images are skipped.
   
   Extract Filename and Extension
   
   A custom Code node analyzes each image URL to extract:
   - The file name (without extension)
   - The file extension (e.g., jpg, png)
   
   Determine File Format
   
   A Switch node evaluates the extension and routes each request appropriately:
   - If the image is in JPG or JPEG format, it is sent to the JPG-to-WEBP conversion path.
   - If it is PNG, it is directed to the PNG-to-WEBP route.
   
   Convert Image Using APYHub
   
   Separate HTTP Request nodes handle JPG and PNG conversions to WEBP using the APYHub API:
   - JPG: https://api.apyhub.com/convert/image/jpeg/webp/url
   - PNG: https://api.apyhub.com/convert/image/png/webp/url
   
   Each conversion request sends the original image URL in the request body and includes the API key in the header for authorization.
   
   Update Google Sheet with New URL
   
   Once converted, the new WEBP URL is written back into the original Google Sheet. This not only marks the image as processed (via a “DONE” flag) but also stores the final file’s location for backup or sharing purposes.
   
   Download and Upload to Google Drive
   
   The workflow then retrieves the converted image using another HTTP Request node and uploads it to a chosen Google Drive folder using the Google Drive API node. The image is renamed to match its original name but with a .webp extension.
   
   Benefits of This Workflow
   
   - Fully Automated: Requires minimal manual intervention once deployed.
   - Format Consistency: Standardizes image formats across your collection.
   - Web Optimization: WEBP images are ideal for faster web performance.
   - Scalable: Can handle hundreds of image URLs in one run.
   - Centralized Management: Uses Google Sheets and Drive for seamless integration.
   
   Use Cases
   
   - Website image optimization
   - Converting user-uploaded files for CMS platforms
   - Building a media processing backend
   - Automatically compressing large image libraries for mobile apps
   
   Conclusion
   
   With this n8n workflow, you can stop wasting time on manual conversions and ensure your media library is always web-optimized. By integrating APYHub with Google tools, you benefit from a robust, low-code automation solution that scales effortlessly.
   
   Whether you're a web developer, content manager, or digital marketer, this workflow empowers you to automate a fundamental part of your media management strategy — image optimization.
   
   Start by signing up at APYHub and cloning the Google Sheet template, and you’ll be on your way to a fully automated image conversion pipeline in just a few minutes.
   
   Happy automating!

5. Set credentials for each API node (keys, OAuth) in Credentials.
6. Run a test via Execute Workflow. Inspect Run Data, then adjust parameters.
7. Enable the workflow to run on schedule, webhook, or triggers as configured.

Tips: keep secrets in credentials, add retries and timeouts on HTTP nodes, implement error notifications, and paginate large API fetches.

Validation: use IF/Code nodes to sanitize inputs and guard against empty payloads.

Why Automate This with AI Agents

AI‑assisted automations offload repetitive, error‑prone tasks to a predictable workflow. Instead of manual copy‑paste and ad‑hoc scripts, your team gets a governed pipeline with versioned state, auditability, and observable runs.

n8n’s node graph makes data flow transparent while AI‑powered enrichment (classification, extraction, summarization) boosts throughput and consistency. Teams reclaim time, reduce operational costs, and standardize best practices without sacrificing flexibility.

Compared to one‑off integrations, an AI agent is easier to extend: swap APIs, add filters, or bolt on notifications without rewriting everything. You get reliability, control, and a faster path from idea to production.

Best Practices

• Credentials: restrict scopes and rotate tokens regularly.
• Resilience: configure retries, timeouts, and backoff for API nodes.
• Data Quality: validate inputs; normalize fields early to reduce downstream branching.
• Performance: batch records and paginate for large datasets.
• Observability: add failure alerts (Email/Slack) and persistent logs for auditing.
• Security: avoid sensitive data in logs; use environment variables and n8n credentials.

FAQs

Can I swap integrations later? Yes. Replace or add nodes and re‑map fields without rebuilding the whole flow.

How do I monitor failures? Use Execution logs and add notifications on the Error Trigger path.

Does it scale? Use queues, batching, and sub‑workflows to split responsibilities and control load.

Is my data safe? Keep secrets in Credentials, restrict token scopes, and review access logs.