Smartcat
Document ProcessingAutomate localization through Smartcat's Integration API. Agents create and cancel translation projects, track document status across workflow stages, and pull word-count statistics to estimate translation volume and cost.
What This Integration Enables
Localization is a supply chain: content flows in, passes through Translation, Editing, and Proofreading stages, and ships back out in every target language, with real money attached to every word. Smartcat manages that chain, and FlowRunner agents run its logistics. They open projects when content publishes, pull word-count statistics broken down by exact matches, repetitions, and new words for honest cost estimation, track documents through each workflow stage, and correlate everything back to your own systems through external tags. - Open translation projects automatically when [WordPress](/integrations/wordpress) or [Contentful](/integrations/contentful) publishes new content - Estimate volume and cost per language from match-category word counts before committing - Poll document status across workflow stages and post progress to [Slack](/integrations/slack) - Store delivered translations in the right [Google Drive](/integrations/google-drive) folder on completion - Log translation volume and estimated cost per language into [Google Sheets](/integrations/google-sheets) - Tie every Smartcat project to a CMS record or ticket via external tags, so nothing floats free The statistics are the underrated piece. Exact matches and repetitions are typically discounted in translation pricing, so an agent that reads Get Project Statistics before work begins gives the team a cost picture grounded in how the industry actually bills, not a flat rate times a guess.
Without FlowRunner
With FlowRunner
Use Case Scenarios
Publish once, localize everywhere
A product page goes live in [Contentful](/integrations/contentful). The agent verifies the language pairs with Get Account, creates a project with Create Project targeting German, French, and Japanese with the standard three-stage workflow, and tags it with the entry ID. Documents upload, Get Project Statistics reports the counts, and the localization manager approves the spend. From publish to approved localization project: one flow, same morning.
The status board that answers before anyone asks
Twice daily, List Projects sweeps active work and List Documents pulls per-stage progress for each. The tracking sheet in [Google Sheets](/integrations/google-sheets) updates with each document's stage and percentage, and any document stalled in Editing for more than two days gets flagged to the localization channel in [Slack](/integrations/slack). When the German version reaches Proofreading, the release manager sees it without sending a single "any update?" email.
Delivery that files itself
Get Project shows a project complete. The flow retrieves the finished documents' details, stores the delivered files in the release folder in [Google Drive](/integrations/google-drive) organized by language, posts the completion summary with final word counts, and marks the originating CMS record as localized using the external tag correlation. The last mile of localization, the part where finished translations sit unnoticed in a vendor platform, disappears.
Human-in-Loop Highlight
Cancel Project halts an active workflow with no undo, and what it halts is not a background job but human work: Smartcat is a linguist marketplace, and an active project usually has translators and editors partway through documents, with hours invested that cancellation strands. An agent that cancels on a false signal, a CMS record unpublished for a five-minute fix, a duplicate-detection mistake, has thrown away paid professional work and told the linguists their effort did not matter, twice over if the project then gets recreated. So cancellation is never an agent's own call in FlowRunner flows. The agent presents the case: project name, per-stage progress from Get Project, how many documents sit mid-stage, and the trigger that suggested cancellation. The localization manager, who knows whether the German launch is actually dead or just delayed, gives the yes. Create Project carries a lighter check at the cost line instead, because opening a project is the moment translation spend becomes real.
Agent Capabilities
8 actionsProjects
5- List Projects Lists translation projects with optional filtering by name and external tag, paginated by offset and limit. Returns each project's languages, workflow status, deadline, and creation date. The sweep behind status boards and correlation lookups.
- Get Project Retrieves one project in full: languages, workflow stages with progress, deadline, status, and its document IDs. The evidence read before completion routing or any cancellation decision.
- Create Project Creates a translation project with a source language, one or more targets, and an ordered workflow, submitted so documents can upload separately. The write that starts the localization supply chain, reviewed at the cost line.
- Cancel Project Cancels an active project by ID, halting its workflow permanently. Cannot be undone, and strands in-progress linguist work, which is why this call belongs to a person.
- Get Project Statistics Retrieves statistics by target language and workflow stage, with word counts split into exact matches, repetitions, and new words. The honest basis for volume and cost estimation before work proceeds.
Documents
2- List Documents Lists a project's documents with ID, name, status, languages, and per-stage progress. The polling read behind progress tracking and stall detection.
- Get Document Retrieves one document's status and metadata by its projectInternalId_documentPart ID, including word count and workflow-stage progress. The drill-down for a single deliverable's state.
Account
1- Get Account Retrieves the authenticated account's ID, name, and available source and target language pairs. The validation step before any project is created, so flows fail at setup rather than mid-launch.
Frequently Asked Questions
What can FlowRunner do with Smartcat?
FlowRunner agents can run List Projects, Get Project, and Create Project in Smartcat, plus 5 more actions.
Does connecting Smartcat to FlowRunner require OAuth?
No. Smartcat connects to FlowRunner with basic authentication (a username and password), no OAuth flow required.
Can Smartcat trigger a FlowRunner workflow automatically?
Smartcat doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Start building with Smartcat
$100 in credits. No card required. Connect in minutes.