Integration

Connect Process Street to Simpleen Translation

When something happens in Process Street, your agent does the next thing in Simpleen Translation. Describe it in plain language and the automation is built, tested on every branch and kept running.

Process Street4 triggersProcess Street8 actionsSimpleen Translation13 actions

Browse all apps

Build it

What do you want Process Street and Simpleen Translation to do together?

Describe it and your agent reads both APIs, builds the automation, tests every branch and ships it. The list below is what exists today, not the limit.

Ask the assistant

You'll sign in before anything runs. What you typed comes with you.

Or work from Claude Code

Install the APIANT plugin for Claude Code and build, edit, test and read run history from your terminal. Every plan gets this, including free, and it spends no assistant credits.

Connect Claude Code

Everything your agent can do with Process Street and Simpleen Translation

Triggers and actions 4 triggers · 21 actions

Trigger
New Comment Attachment
Triggers when someone attaches a file to a comment in a workflow run.
Trigger
New Task Checked
Triggers when a task is checked off in a workflow.
Trigger
New Workflow Run
Triggers when a workflow is run.
Trigger
Task Ready
Triggers when a task is ready to be worked on.
Action
Create Data Set Record
Adds a new record to a data set.
Action
Delete Data Set Record
Deletes an existing record in a data set.
Action
Find Data Set Records
Search for data set records by form fields.
Action
Find Workflow Run
Search for a workflow run by ID, name, form fields, and other attributes.
Action
Run Workflow
Runs a workflow.
Action
Update Data Set Record
Updates an existing record in a data set.
Action
Update Task
Update a task in a workflow run.
Action
Update Workflow Run
Update an existing workflow run.
Action
Add glossary
Create a new glossary of word entries/ignored terms for translation. POST /glossaries.
Action
Add segment
Create a new translation segment (source entry + translated entry) tied to a file. POST /segments.
Action
Create Translation
Translates content to selected target language
Action
Get file
Get a specific localization file by id, including its segments and languages. GET /files/{id}.
Action
Get glossary
Get a specific glossary by id, including its entries and ignored words. GET /glossaries/{id}.
Action
Get segment
Get a specific translation segment by id. GET /segments/{id}.
Action
List files
List the localization files known to the account. GET /files.
Action
List glossaries
List the user's glossaries (word lists of ignored terms + custom translations). GET /glossaries.
Action
List languages
List all supported languages (DeepL/Google Translate backed) with source/target flags. GET /languages.
Action
List segments
List translatable segments (source/translated entry pairs) across the user's files. GET /segments.
Action
Run translator
Translate text using a saved, preconfigured Translator (reusable source/target language + format + glossary setup). POST /translators/{id}/translate.
Action
Update glossary
Update an existing glossary's name, entries, or ignored words. PUT /glossaries/{id}.
Action
Update segment
Post-edit an existing translation segment's entry to fix/correct future translation usage. PUT /segments/{id}.

Each app on its own

The other way round: Simpleen Translation to Process Street