TAUS EPIC is an API for quality estimation and automated post-editing. It provides a continuous quality control loop for machine translation output (predicting translation quality and automatically improving segments where needed) helping organizations scale multilingual content workflows while maintaining control over quality, cost, and risk.
The integration uses two Phrase Orchestrator workflows to automate an EPIC-driven editing stage inside a Phrase TMS project. When content enters the process, it triggers edits within EPIC and reports back into the workflow, ensuring the updated content is available in the project.
EPIC edits are only available in the CAT web editor and not the desktop editor.
The workflows can only be published and executed with the next-gen Phrase Orchestrator Workflow Engine.
-
Workflow A: Trigger AI processing
-
Initiates on job event (i.e. when a job completes MT pre-translation), and sends content to EPIC for processing.
-
-
Workflow B: Retrieve AI results
-
Receives EPIC callback when edits are complete and continues downstream processing to ensure EPIC edits are displayed in the Phrase CAT web editor interface.
-
-
The Phrase TMS project has a workflow that includes a first workflow step to inject raw machine translation. This step is usually automatically completed after the pre-translation is finished.
-
There is a dedicated second workflow step for EPIC editing and locking.
-
A human editing step follows as the next step in the workflow.
-
A webhook must be registered in TAUS EPIC to enable callback communication. Webhook configuration is available in the TAUS EPIC interface when logged in.
Required variables
These values must be defined in Orchestrator workspace before implementing the workflows:
|
Variable |
Purpose |
|---|---|
|
|
API token used to authenticate calls into EPIC |
|
|
The webhook/trigger URL that EPIC will call when edits finish NoteThe Example trigger URL: https://eu.phrase.com/orchestrator/webhooks/12c8a2ec-3f6d-478a-b254-428cd5158543 |
Populate variables
Create these variables using sensible naming and match exactly:
-
epic_api_tokenFor security reasons, this variable should be marked as secret. To retrieve the token, visit the TAUS account.
Import Workflow B:
-
From the page, click Create and select Workflow via Templates.
The template selection page opens.
-
Click on the template and click Use template.
The workflow is displayed.
-
Click Publish and confirm the publication.
-
Open the workflow and copy the .
This URL is the webhook that EPIC will call after editing.
-
Set this URL for the
workflow_2_trigger_urlvariable. -
Register the webhook in TAUS EPIC by adding as a webhook endpoint.
Import Workflow A:
Note
Ensure all variables are already defined, otherwise the workflow will present a publishing error. Variables can be added after import if needed.
-
From the page, click Create and select Workflow via Templates.
The template selection page opens.
-
Click on the template and click Use template.
The workflow is displayed.
-
Copy the UID of the project from its URL.
The UID can be found at the end of the URL in a browser. Example: https://cloud.phrase.com/web/project2/show/
KY6gfZXv4Gqw7B0m1U8br6 -
Edit the condition of the workflow trigger by clicking the blue bar at the top of the trigger and replacing the placeholder with the copied UID.
-
Click Publish and confirm the publication.
When opening a job that has been processed by EPIC, the CAT web editor displays the notification toast.
EPIC post-editing can result in the following outputs:
-
Edited target
The segment text was modified by EPIC. This is indicated by the EPIC-specific edit icon and the tooltip in the origin column.
-
Estimated target
If quality estimation is applied, a score is displayed above the EPIC icon and in the tooltip.
Users can review changes between workflow steps (such as the pre-translation step, EPIC processing step, and post-EPIC human editing step) in the translation changes pane of the CAT web editor or by exporting workflow changes from the project page.