Translate
Configured with Aggregate, Convert To File, Extract From File, Form, and additional nodes. Review the connections and setup before adapting this template.
Node categories in this workflow
- Transform
- Integration
- Code
- Trigger
Icons describe general node roles, inferred from node types. Inspect the parameters for the configured action.
Drag to pan; use + and − to zoom. Reconstructed from the exported node positions; nothing runs here. Dashed lines represent non-main connections. Full node names and notes appear below.
How it works
The exported workflow contains the following configured nodes. Their connections are shown above; inspect the JSON for the complete logic, expressions, and external actions.
| Node | Category | Type | Operation |
|---|---|---|---|
| Split Out | Transform | Split Out | See node parameters |
| Google Translate | Integration | Google Translate | See node parameters |
| Aggregate | Transform | Aggregate | See node parameters |
| Edit Fields | Transform | Edit Fields | See node parameters |
| Convert to File | Transform | Convert To File | toBinary |
| Split SRT Lines | Code | Code | See node parameters |
| Generate Binary | Code | Code | See node parameters |
| Prep Parts for Translate | Code | Code | See node parameters |
| Clean Translations & Group Titles | Code | Code | See node parameters |
| Join completed text with double new line | Code | Code | See node parameters |
| Respond with file | Integration | Form | completion |
| Receive SRT File to Translate | Trigger | Form Trigger | See node parameters |
| Extract text from Binary File | Transform | Extract From File | text |
| Expose Binary | Code | Code | See node parameters |
Setup
- Download the JSON and import it into an isolated n8n instance. Leave the workflow inactive.
- Connect your own credentials through n8n’s credential store. Replace
REPLACE_WITH_*values with your resource identifiers. - Inspect API destinations, Code nodes, database queries, file paths, and outbound actions.
- Run with synthetic data and harmless destinations. Enable triggers only after checking the actual outputs.
Requirements
An n8n instance with the listed node types and compatible versions. Service-connected workflows may require accounts, credentials, or paid APIs.
Credential types declared in the source
googleTranslateOAuth2Api
Workflow notes
Required Credentials
Required Credentials
https://docs.n8n.io/integrations/builtin/credentials/google/
Selecting Language
You can update the form to include your preferred language code (that you are translating to), by updating the dropdown field with a new option. Or update the Google Translate node language option back to 'fixed' and select your desired language. This will ignore the form option, but is safe to do.
Translate
Translate
Purpose and structure
This folder contains the Translate workflow. Its executable nodes use aggregate, code, convertToFile, extractFromFile, form, formTrigger, googleTranslate, set, splitOut. The table and connection map below are derived from the JSON, not an inferred guarantee of behavior.
Setup
Import inactive. Configure your own credentials and replace REPLACE_WITH_* values. Review external destinations and Code nodes before running.
Entry points
Receive SRT File to Translate
Verification
Sanitized source candidate; not runtime-tested. This overview is generated from node metadata. Read the folder README for the connection map, credential types, and license.
Attribution
https://github.com/Zie619/n8n-workflows/blob/94007c1445d9258a7da116646b79473e7c7c3282/workflows/Splitout/1993_Splitout_Code_Automation_Triggered.json MIT; preserve source notices.