FeaturedDocument Ops#AI#Translation#Document#Agent

PDF / DOCX Translation Agent

Translate the full text of any uploaded document using an AI agent.

Workflow at a glance

The full canvas, before you import it

Click any node to see its config.

#AI#Translation#Document#Agent

Click a node to select it — same as the Heym editor; the panel shows its settings.

3 nodes · Free & source-available

PDF / DOCX Translation Agent

Upload a PDF or DOCX and receive a full translation in your target language. The agent handles long documents through chunked processing and reassembles the result.

What this workflow does

  1. Input node receives the document text (paste extracted text or pipe from a file-reading node)
  2. Agent node translates the full content with context-aware chunking
  3. Output node returns the translated text ready to copy or save

Use cases

  • Legal and contract document translation
  • Research paper localisation
  • Technical manual adaptation

Customisation

Update the system instruction in the Agent node to set the target language and any domain-specific terminology guidelines.

How to import this template

  1. 1Click Import → Copy JSON on this page.
  2. 2Open your Heym and navigate to a workflow canvas.
  3. 3PressCmd+V/Ctrl+V— nodes appear instantly.
  4. 4Add your API keys in the node config panels and click Run.
More workflow templates
View all templates
Heym
incident analysis · production AI
Observed across 100s of AI rollouts

AI workflows don't fail because of prompts.
They fail because of orchestration.

symptom · glue code01
5 tools
Scripts, vector DB, approval bot, tracing, browser runner — none of them talk.
symptom · visibility02
~0%
Observable behavior across the stack. Debugging is guesswork.
with heym · one runtime
1 canvas
Agents, RAG, HITL, MCP, traces & evals. Self-hosted. Observable.
AI-Native RuntimeProduction-Grade
github.com/heymrun/heym