AI Document Translator workflow blueprint

Inputs for the Document Translator workflow

Provide the following information when starting this workflow. Required inputs are validated before the first workflow stage runs.

• Document

  Required

  Document text to translate

  Type: String

• Target Language

  Required

  Target language (e.g. Spanish, French)

  Type: String

Input template

This request shape is generated from the blueprint's input schema. Angle-bracket values are placeholders; defaults and examples appear only when the source blueprint defines them.

{
  "document": "<required string>",
  "target_language": "<required string>"
}

How the Document Translator AI workflow works

This content & writing blueprint uses a dag workflow with 2 agents, 0 functions, and 0 MCP servers. This catalog blueprint is available by request; contact GraphN to discuss access and customization for your use case.

1. 1

   Translator

   Agent using Translator

2. 2

   Back Translator

   Agent using Back Translator

Blueprint resources and prerequisites

These are the actual agents, functions, and MCP servers declared by the blueprint. If an MCP server connects to an external system, configure the required connection and credentials in your GraphN workspace before running the workflow.

Workflow output contract

The completed workflow makes the following output available to downstream steps, applications, or API clients: