Overview
The Translation agent reads text from a field in a record and uses your connected AI provider to translate it into a target language. The translated content is written back to an output field of your choice.
You can configure multiple translation entries per action, each pulling from a different source field and writing to a different output field in a different language. This lets a single action handle several translation tasks at once.
Note: This feature requires an AI Connection to be set up in Platform Settings before you can create an AI Agent action. See the AI Connection article for setup instructions.
Prerequisites
Before creating this action, make sure you have:
- At least one AI Connection configured under Platform Settings
- A form with a source field containing the text to translate, and a separate output field to receive the translated content
Creating the Action
Actions are created from the Actions section in your app.
- In the left-hand navigation, select Actions.
- Click + Create Action.
- In the New Action dialog, set Select Action Type to AI Agent. Additional fields will appear.
- Enter an Action Name (up to 128 characters).
- Optionally, add a Description.
- Under Select Form, choose the form this action will run against.
- Under AI Connection, select the AI connection to use. Connections are managed in Platform Settings.
- Under Agent Type, select Translation. The Translation Entries section will appear below.

Configure the translation entries and remaining options as described in the Configuration Reference section below.
- Click Create to save the action. The action configuration editor will open, where you can review and adjust settings.
Configuration Reference
The fields below appear in both the New Action dialog and the action configuration editor after creation.
Action Details
| Field | Description |
| Select Action Type * | Set to AI Agent. Cannot be changed after creation. |
| Action Name * | A short name to identify this action in the Actions list. Maximum 128 characters. |
| Description | Optional. A note describing what this action does. |
| Select Form * | The form whose records this action will process. |
| AI Connection * | The AI service connection to use. Connections are configured in Platform Settings. |
| Agent Type * | Set to Translation for this agent. |
Translation Entries
This section defines one or more translation entries. Each entry maps a source field to an output field and specifies the target language.
Use the + Add Translation Entry link to add additional entries. Use the – button to the left of an entry to remove it.
| Field | Description |
| Type * | Determines the source of the text to translate. Set to Field to read from a field in the record, or Custom to provide a static text value. |
| Source Field * | The field whose content will be sent to the AI for translation. Appears when Type is set to Field. |
| Output Language * | The language the text should be translated into. Select from the full list of supported languages. |
| Output Field * | The field where the translated text will be written. |
Note: You can configure multiple translation entries in a single action. Each entry can target a different source field, language, and output field.

Context Prompt
An optional free-text field that applies to the action as a whole. Use this to give the AI additional instructions — for example, to maintain a formal tone, preserve terminology, or handle domain-specific language.
You can reference field values in the prompt by typing @ to insert a field token. This allows the prompt to include dynamic content from the record being processed.
Change Record Stage After Execution
A toggle that, when enabled, reveals a Stage dropdown. When the AI agent finishes processing, the record will automatically move to the selected stage.
| Field | Description |
| Change Record Stage After Execution | Toggle off by default. Enable to automatically advance the record to a specific stage once the agent completes. |
| Stage | Appears when the toggle is enabled. Select the stage the record should move to after the agent runs. |
