Integration
Connect Demio to Simpleen Translation
When something happens in Demio, 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.
Build it
What do you want Demio 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 CodeEverything your agent can do with Demio and Simpleen Translation
Triggers and actions 3 triggers ยท 17 actions
Trigger
Does Not Attend WebinarTriggers when a webinar ends and we detect a registrant did not attended.
Trigger
New Webinar RegistrationTriggers when there is a new registration for a webinar.
Trigger
Webinar UpdateTriggers after a webinar has ended. If using a series webinar, we provide the date of the next schedule series.
Action
Get eventReturns information about a specific Event, including a full list of its Event Sessions ordered by scheduled date/time. GET /events/{event_id}
Action
Get event sessionReturns information about a specific Event Session. GET /events/{event_id}/sessions/{date_id}
Action
List event participantsReturns the Event Date participants list, optionally filtered by status query param (attended, did not attend, completed, left early, banned). GET /report/{event_id}/{date_id}/participants
Action
List eventsReturns active (not canceled) Events grouped by Event ID, ordered by next upcoming session date/time. Supports type=upcoming query param to filter to upcoming events only. GET /events
Action
Add glossaryCreate a new glossary of word entries/ignored terms for translation. POST /glossaries.
Action
Add segmentCreate a new translation segment (source entry + translated entry) tied to a file. POST /segments.
Action
Create TranslationTranslates content to selected target language
Action
Get fileGet a specific localization file by id, including its segments and languages. GET /files/{id}.
Action
Get glossaryGet a specific glossary by id, including its entries and ignored words. GET /glossaries/{id}.
Action
Get segmentGet a specific translation segment by id. GET /segments/{id}.
Action
List filesList the localization files known to the account. GET /files.
Action
List glossariesList the user's glossaries (word lists of ignored terms + custom translations). GET /glossaries.
Action
List languagesList all supported languages (DeepL/Google Translate backed) with source/target flags. GET /languages.
Action
List segmentsList translatable segments (source/translated entry pairs) across the user's files. GET /segments.
Action
Run translatorTranslate text using a saved, preconfigured Translator (reusable source/target language + format + glossary setup). POST /translators/{id}/translate.
Action
Update glossaryUpdate an existing glossary's name, entries, or ignored words. PUT /glossaries/{id}.
Action
Update segmentPost-edit an existing translation segment's entry to fix/correct future translation usage. PUT /segments/{id}.
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.
Each app on its own
Reviews