Back to Integrations
integrationDeepL node
integrationHTTP Request node

DeepL and HTTP Request integration

Save yourself the work of writing custom integrations for DeepL and HTTP Request and use n8n instead. Build adaptable and scalable Utility, Development, and Core Nodes workflows that work with your technology stack. All within a building experience you will love.

How to connect DeepL and HTTP Request

  • Step 1: Create a new workflow
  • Step 2: Add and configure nodes
  • Step 3: Connect
  • Step 4: Customize and extend your integration
  • Step 5: Test and activate your workflow

Step 1: Create a new workflow and add the first step

In n8n, click the "Add workflow" button in the Workflows tab to create a new workflow. Add the starting point – a trigger on when your workflow should run: an app event, a schedule, a webhook call, another workflow, an AI chat, or a manual trigger. Sometimes, the HTTP Request node might already serve as your starting point.

DeepL and HTTP Request integration: Create a new workflow and add the first step

Step 2: Add and configure DeepL and HTTP Request nodes

You can find DeepL and HTTP Request in the nodes panel. Drag them onto your workflow canvas, selecting their actions. Click each node, choose a credential, and authenticate to grant n8n access. Configure DeepL and HTTP Request nodes one by one: input data on the left, parameters in the middle, and output data on the right.

DeepL and HTTP Request integration: Add and configure DeepL and HTTP Request nodes

Step 3: Connect DeepL and HTTP Request

A connection establishes a link between DeepL and HTTP Request (or vice versa) to route data through the workflow. Data flows from the output of one node to the input of another. You can have single or multiple connections for each node.

DeepL and HTTP Request integration: Connect DeepL and HTTP Request

Step 4: Customize and extend your DeepL and HTTP Request integration

Use n8n's core nodes such as If, Split Out, Merge, and others to transform and manipulate data. Write custom JavaScript or Python in the Code node and run it as a step in your workflow. Connect DeepL and HTTP Request with any of n8n’s 1000+ integrations, and incorporate advanced AI logic into your workflows.

DeepL and HTTP Request integration: Customize and extend your DeepL and HTTP Request integration

Step 5: Test and activate your DeepL and HTTP Request workflow

Save and run the workflow to see if everything works as expected. Based on your configuration, data should flow from DeepL to HTTP Request or vice versa. Easily debug your workflow: you can check past executions to isolate and fix the mistake. Once you've tested everything, make sure to save your workflow and activate it.

DeepL and HTTP Request integration: Test and activate your DeepL and HTTP Request workflow

Translate cocktail instructions using DeepL

This workflow allows you to translate cocktail instructions using DeepL.

HTTP Request node: This node will make a GET request to the API https://www.thecocktaildb.com/api/json/v1/1/random.php to fetch a random cocktail. This information gets passed on to the next node in the workflow. Based on your use case, replace the node with the node from where you might receive the data.

DeepL node: This node will translate the cocktail instructions that we got from the previous node to French. To translate the instructions in your language, select your language instead.

Nodes used in this workflow

Popular DeepL and HTTP Request workflows

+3

Collect Viral Instagram AI Art with GPT-4 Analysis and Telegram Delivery

Who is this for? This template is perfect for: AI art enthusiasts** who want to stay updated on trending AI-generated artwork Content curators** looking to automate art discovery Japanese-speaking users** who want translated captions Social media managers** tracking AI art trends across platforms What this workflow does This workflow automatically collects viral AI art posts from Instagram and delivers them to your Telegram with Japanese translations. It runs daily and filters only high-engagement posts to ensure quality content. Key Features: 📸 Collects from 4 AI art hashtags (#AIart, #midjourney, #stablediffusion, #aiartwork) 🔥 Filters viral posts only (100+ likes threshold) 🇯🇵 Auto-translates captions to Japanese via DeepL ⚠️ Sends error alerts to Telegram if something goes wrong ⏱️ Built-in rate limiting to avoid API blocks How it works Schedule Trigger - Runs daily at 18:00 Instagram Scraping - Apify collects posts from multiple AI art hashtags Viral Filter - Only posts with 100+ likes and valid captions pass through Translation - DeepL translates captions from English to Japanese Image Download - Fetches the post image Telegram Delivery - Sends photo with translated caption, likes count, and source link Rate Limiting - 3-second delay between posts to avoid API limits Setup Requirements Apify account** - Sign up at apify.com for Instagram scraping DeepL API key** - Get free API access at deepl.com/pro-api Telegram Bot** - Create via @BotFather and get your Chat ID How to set up Import this workflow into n8n Set up credentials: Connect your Apify account Add your DeepL API key Configure Telegram Bot token Replace YOUR_TELEGRAM_CHAT_ID with your actual Chat ID in both Telegram nodes (Optional) Adjust the viral threshold in the Filter node (Optional) Modify hashtags in the Apify node Activate the workflow How to customize Change hashtags:** Edit the directUrls array in the Apify node Adjust viral threshold:** Change the 100 value in the Filter node Change schedule:** Modify the trigger time in the Schedule Trigger node Change language:** Update the translateTo parameter in the DeepL node Modify caption format:** Edit the caption template in the Telegram node
+2

Daily News Digest & Weekly Trends with AI Filtering, Slack & Google Sheets

Who is this for This template is perfect for: Market Researchers** tracking industry trends. Tech Teams** wanting to stay updated on specific technologies (e.g., "AI", "Cybersecurity"). Content Creators** looking for curated news topics. Busy Professionals** who need a high-signal, low-noise news digest. What it does Fetches News: Pulls daily articles via NewsAPI based on your chosen keyword (default: "technology"). AI Filtering: Uses an AI Agent (via OpenRouter) to filter out low-quality or irrelevant clickbait. Daily Digest (Slack): Summarizes the top 3 articles in English. Translates the summaries to Japanese using DeepL (optional). Posts both versions to a Slack channel. Data Archiving (Sheets): Extracts structured data (Title, Author, Summary, URL) and saves it to Google Sheets. Weekly Trend Report: Every Monday, it reads the past week's data from Google Sheets and uses AI to generate a high-level trend report and strategic insights. How to set up Configure Credentials: You will need API keys/auth for NewsAPI, OpenRouter (or OpenAI), DeepL, Google Sheets, and Slack. Setup Google Sheet: Create a sheet with the following headers in the first row: title, author, summary, url. Map the Sheet: In the "Append row in sheet" and "Read sheet (weekly)" nodes, select your file and map the columns. Define Keyword: Open the "Set Keyword" node and change chatInput to the topic you want to track (e.g., "Crypto", "SaaS", "Climate Change"). Slack Setup: Select your desired channel in the Slack nodes. Requirements n8n** (Self-hosted or Cloud) NewsAPI** Key (Free tier available) OpenRouter** (or any LangChain compatible Chat Model like OpenAI) DeepL** API Key (for translation) Google Sheets** account Slack** Workspace How to customize Change the Language:** Remove the DeepL node if you only want English, or change the target language code. Adjust the Prompt:** Modify the "AI Agent (Filter)" system message to change how strict the news filtering is. Change Schedule:** Adjust the Cron nodes to run at your preferred time (currently set to Daily 8 AM and Weekly Monday 9 AM).

Japanese Document Translation Quality Checker with DeepL & Google Drive to Slack

Title Japanese Document Translation Quality Checker with DeepL & Google Drive to Slack Who’s it for Localization teams, QA reviewers, and operations leads who need a fast, objective signal on Japanese document translation quality without manual checks. What it does / How it works This workflow watches a Google Drive folder for new Japanese documents, exports the text, translates JA→EN with DeepL, then back-translates EN→JA. It compares the original and back-translation to estimate a quality score and summarizes differences. A Google Docs report is generated, and a Slack message posts the score, difference count, and report link—so teams can triage quickly. How to set up Connect credentials for Google Drive, DeepL, and Slack. Point the Google Drive Trigger to your “incoming JP docs” folder. In the Workflow Configuration (Set) node, fill targetFolder (report destination) and slackChannel. Run once, then activate and drop a test doc. Requirements n8n (Cloud or self-hosted), Google Drive, DeepL, and Slack credentials; two Drive folders (incoming, reports). How to customize the workflow Tune the diff logic (character → token/line level, normalization rules), adjust score thresholds and Slack formatting, or add reviewer routing/Jira creation for low-score cases. Always avoid hardcoded secrets; keep user-editable variables in the Set node.
+2

Generate Weather-Based Date Itineraries with Google Places, OpenRouter AI, and Slack

🧩 What this template does This workflow builds a 120-minute local date course around your starting point by querying Google Places for nearby spots, selecting the top candidates, fetching real-time weather data, letting an AI generate a matching emoji, and drafting a friendly itinerary summary with an LLM in both English and Japanese. It then posts the full bilingual plan with a walking route link and weather emoji to Slack. 👥 Who it’s for Makers and teams who want a plug-and-play bilingual local itinerary generator with weather awareness — no custom code required. ⚙️ How it works Trigger – Manual (or schedule/webhook). Discovery – Google Places nearby search within a configurable radius. Selection – Rank by rating and pick the top 3. Weather – Fetch current weather (via OpenWeatherMap). Emoji – Use an AI model to match the weather with an emoji 🌤️. Planning – An LLM writes the itinerary in Markdown (JP + EN). Route – Compose a Google Maps walking route URL. Share – Post the bilingual itinerary, route link, and weather emoji to Slack. 🧰 Requirements n8n (Cloud or self-hosted) Google Maps Platform (Places API) OpenWeatherMap API key Slack Bot (chat:write) LLM provider (e.g., OpenRouter or DeepL for translation) 🚀 Setup (quick) Open Set → Fields: Config and fill in coords/radius/time limit. Connect Credentials for Google, OpenWeatherMap, Slack, and your LLM. Test the workflow and confirm the bilingual plan + weather emoji appear in Slack. 🛠 Customize Adjust ranking filters (type, min rating). Modify translation settings (target language or tone). Change output layout (side-by-side vs separated). Tune emoji logic or travel mode. Add error handling, retries, or logging for production use.

Translate cocktail instructions using DeepL

This workflow allows you to translate cocktail instructions using DeepL. HTTP Request node: This node will make a GET request to the API https://www.thecocktaildb.com/api/json/v1/1/random.php to fetch a random cocktail. This information gets passed on to the next node in the workflow. Based on your use case, replace the node with the node from where you might receive the data. DeepL node: This node will translate the cocktail instructions that we got from the previous node to French. To translate the instructions in your language, select your language instead.

Build your own DeepL and HTTP Request integration

Create custom DeepL and HTTP Request workflows by choosing triggers and actions. Nodes come with global operations and settings, as well as app-specific parameters that can be configured. You can also use the HTTP Request node to query data from any app or service with a REST API.

DeepL supported actions

Translate
Translate data

FAQs

  • Can DeepL connect with HTTP Request?

  • Can I use DeepL’s API with n8n?

  • Can I use HTTP Request’s API with n8n?

  • Is n8n secure for integrating DeepL and HTTP Request?

  • How to get started with DeepL and HTTP Request integration in n8n.io?

Need help setting up your DeepL and HTTP Request integration?

Discover our latest community's recommendations and join the discussions about DeepL and HTTP Request integration.
Moiz Contractor
theo
Jon
Dan Burykin
Tony

Looking to integrate DeepL and HTTP Request in your company?

Over 3000 companies switch to n8n every single week

Why use n8n to integrate DeepL with HTTP Request

Build complex workflows, really fast

Build complex workflows, really fast

Handle branching, merging and iteration easily.
Pause your workflow to wait for external events.

Code when you need it, UI when you don't

Simple debugging

Your data is displayed alongside your settings, making edge cases easy to track down.

Use templates to get started fast

Use 1000+ workflow templates available from our core team and our community.

Reuse your work

Copy and paste, easily import and export workflows.

Implement complex processes faster with n8n

red iconyellow iconred iconyellow icon