Skip to content

User Guide

monday.com | Translate Document

Step 1: Install the app

  • Open the monday.com Apps Marketplace.
  • Search for “Translate Document”.
  • Click Install and choose your workspace.

Step 2: Add the integration to a board

  • Open the target board.
  • Click Integrate → Apps → Translate Document.
  • Select the recipe:
  • “When button clicked translate document(s) in source column, from source language to target language and upload to file column”
  • Click Add to board.

Step 3: Configure the recipe and connect the button

  • Add a Button column (e.g., “Translate”).
  • In the recipe setup:
  • Source File Column: the column with original documents
  • Target File Column: where translated files will be uploaded
  • Source Language: choose a language or Auto‑detect
  • Target Language: choose the output language
  • Button: select your “Translate” button column
  • Click Done.

Step 4: Run a translation

  • Attach one or more files to the Source File column on an item.
  • Click the Translate button on that item.
  • The translated file(s) will appear in the Target File column.

Optional: Formality control

  • Use the “Translate with formality” recipe to prefer formal/informal tone where supported (e.g., DE, FR, IT, ES, NL, PL, PT, RU).
  • Output filenames are tagged automatically, for example: formal_DE or informal_DE.

Supported file formats and size limits (DeepL Pro)

We enforce these limits up‑front to avoid failed uploads. Files over the limit are skipped and you’ll receive a bell notification.

FormatMax file sizeCharacter cap
.docx, .doc30 MB1,000,000
.pptx30 MB1,000,000
.xlsx30 MB1,000,000
.pdf30 MB1,000,000
.txt1 MB1,000,000
.html5 MB1,000,000
.xlf, .xliff10 MB1,000,000
.srt150 KB1,000,000

Notes:

  • Unsupported in this app: rtf, htm, xml, sdlxliff, and any format not listed above.
  • DeepL minimum billing applies to some types (.docx/.doc/.xlsx/.pptx/.pdf): at least 50,000 characters per document are billed by DeepL even for short content.

Behavior and limits

  • One document at a time per account (prevents abuse and accidental spikes).
  • Global upload pacing: ~1 file per 0.5 seconds to monday.com.
  • Duplicate clicks: repeated clicks on the same item are de‑duplicated within ~10 seconds; clicks after that enqueue a new job.
  • Bulk actions: if a recipe triggers multiple items, they are queued safely and processed sequentially.
  • Character usage and plan limits: usage is tracked and enforced; if you hit your plan limit, remaining items are skipped and you’ll get a notification.

Notifications you may see

  • Unsupported file type (lists filenames and supported types)
  • File too large for its type (shows actual vs. max)
  • DeepL translation error (shows error message from API)
  • Usage threshold/reached (75%, 90%, and 100%)

Permissions and security

  • Scopes used: notifications:write, boards:read, boards:write, assets:read
  • Documents are processed in memory and uploaded back to monday.com; the app does not persist file contents.
  • OAuth tokens are stored via monday.com SecureStorage and reused across recipes until uninstall or scope changes.
  • We use queueing and rate limiting to ensure stability and protect your account from overuse.

Troubleshooting

  • Nothing happens on click: ensure the Button column is linked in the recipe and the item has at least one supported file (and within size limits).
  • Prompted to re‑authorize when adding a recipe: after first OAuth approval, we reuse your stored token and short‑circuit the auth step. If you still see prompts, uninstall/reinstall or check region settings.
  • File is too large/unsupported: convert to a supported type or reduce size according to the table above.
  • Network/timeouts to DeepL: we automatically retry uploads/status/downloads with exponential backoff. Try again if the error persists.
  • Text encoding in .txt: we upload UTF‑8 with BOM to avoid garbled characters in some viewers.

Support

  • Email: support@otomosolutions.com
  • For faster help, include (if possible): board link, item ID, source/target column IDs, recipe name, and sample filenames.