OpenRuna
Sign in
← Workflows

Translate

15 nodes · splitOut, googleTranslate, aggregate, convertToFile, form, extractFromFile

Engine
n8n
Nodes
15
Trigger
scheduled/triggered
Source file
1993_Splitout_Code_Automation_Triggered.json

Workflow flow

IntegrationsSplit OutGoogleTranslateAggregateConvertToFileFormExtractFromFileSetCode
100%
TRIGGER

Receive SRT File to Translate

Form

Expose Binary

Code

Extract text from Binary File

ExtractFromFile

Split SRT Lines

Code

Split Out

Split Out

Prep Parts for Translate

Code

Google Translate

GoogleTranslate

Clean Translations & Group Titles

Code

Aggregate

Aggregate

Join completed text with double new line

Code

Edit Fields

Set

Generate Binary

Code

Convert to File

ConvertToFile

Respond with file

Form

14 steps · flows top to bottom, branches left to right

Browse by integration

splitOutgoogleTranslateaggregateconvertToFileformextractFromFile
Browse all integrations →
Download n8n JSONDownload sanitized JSONDownload flow graph

Import into n8n

  1. Download the n8n JSON file (full or sanitized).
  2. In n8n: Workflows → Import from file.
  3. Open each node and reconnect credentials to your accounts.
  4. Test with manual execution before enabling triggers.

Sanitized JSON removes credential IDs — safer for sharing. Flow graph JSON is OpenRuna's lightweight format for diagrams and other tools, not n8n import.

View source corpus ↗

Overview

Free n8n workflow: Translate. 15 nodes across splitOut, googleTranslate, aggregate, convertToFile, form, extractFromFile, with a downloadable JSON and a visual flow diagram on OpenRuna.

What this workflow does

Built in n8n, "Translate" chains 15 nodes to move data between splitOut, googleTranslate, aggregate, convertToFile, form, extractFromFile. 15 nodes · splitOut, googleTranslate, aggregate, convertToFile, form, extractFromFile It starts from a scheduled/triggered trigger and routes data through every node in order. OpenRuna renders the node graph and offers the JSON export so you can import and adapt it in minutes. Use it to learn integration patterns, fork it for your own use case, or deploy it quickly after reconnecting credentials.

Use cases

  • Study how data moves from splitOut to googleTranslate before building your own variant.
  • Share it with your team as a documented reference for scheduled/triggered automations in the splitOut stack.
  • Import "Translate" into n8n, reconnect credentials for splitOut, googleTranslate, aggregate, convertToFile, form, extractFromFile, and run the same automation in your own workspace.
  • Use it as a starting template when wiring splitOut, googleTranslate, aggregate, convertToFile, form, extractFromFile — adjust node parameters to your accounts and record IDs.

Example output

Imported into n8n, "Translate" exposes 15 configured nodes. Trigger type: scheduled/triggered. Integrations: splitOut, googleTranslate, aggregate, convertToFile, form, extractFromFile. Open each node after import to map credentials to your own splitOut and googleTranslate accounts. Run it once in test mode to verify any branch logic (Switch/IF nodes) before enabling production triggers.

Tips by platform

Claude

Ask Claude to turn the "Translate" JSON into a plain-English runbook, node by node. It can flag where splitOut rate limits or missing retries might bite before you go live.

ChatGPT

Drop the workflow JSON or this OpenRuna page URL into ChatGPT and ask for a step-by-step runbook: triggers, branches, and which fields to customise for splitOut, googleTranslate, aggregate, convertToFile, form, extractFromFile. Handy for onboarding teammates new to n8n.

Cursor

In Cursor, ask Agent mode to parameterise "Translate" — extract splitOut IDs and secrets into environment variables without changing the 15-node structure.

Frequently asked questions

How do I import "Translate" into n8n?
Click Download n8n JSON on this page, then in n8n choose Workflows → Import from file and select the downloaded file. Reconnect credentials on each node — the export carries credential IDs from the original author's instance, not working secrets.
Which integrations does "Translate" use?
It uses: splitOut, googleTranslate, aggregate, convertToFile, form, extractFromFile. The flow diagram above shows how each service connects across the 15 nodes. Filter OpenRuna by integration to find related workflows and tools.
Can I import a sanitized export without credentials?
Yes. Use "Download sanitized JSON" to strip credential references before sharing internally. You will still add your own splitOut and googleTranslate credentials in n8n after import.
What trigger type does "Translate" use?
Trigger type: scheduled/triggered. After import, confirm the trigger node (webhook, schedule, or app event) matches your environment, then activate the workflow when you are ready to run it.
Is "Translate" free to use?
OpenRuna catalogs community n8n workflows under open licenses. Check the source corpus link for the original license; commercial use may require verifying the third-party API terms for splitOut, googleTranslate, aggregate, convertToFile, form, extractFromFile.

Related resources