Connect Abyssale to Simpleen Translation

Both apps 29Abyssale 16Simpleen Translation 13

• Trigger
  New Export

  Triggers when an export of one or multiple images has been completed

• Trigger
  New File

  Triggers when a single file generation is completed

• Trigger
  New File Batch

  Triggers when a batch generation of files is completed

• Trigger
  Template Status Updated

  Triggers when a template's status has been updated.

• Action
  Add Design from JSON

  Create a new design by importing a JSON payload describing its layers and layout. POST /designs/import/json.

• Action
  Add Project

  Create a new project to organize designs. POST /projects.

• Action
  Duplicate Workspace Template

  Duplicate a workspace template into a project as a new editable design. POST /workspace-templates/{companyTemplateId}/use.

• Action
  Export Visuals

  Export one or multiple previously generated visuals in .zip format

• Action
  Find Format

  Fetch details about a format added to a template you designed in Abyssale

• Action
  Find Template

  Fetch details about a template you designed in Abyssale

• Action
  Generate Dynamic Image URL

  Create a dynamic image URL that renders a design on the fly with custom data, without generating a static file. POST /designs/{designId}/dynamic-image-url.

• Action
  Generate HTML5 Banner Ads

  Generate HTML5 banner ads from an animated template designed in Abyssale

• Action
  Generate Multi-Format Videos

  Generate multiple videos at once from an animated template designed in Abyssale

• Action
  Generate Open Graph Link

  Embed your images as Open Graph into unique redirect shortlinks. Great for hyper-personalized Linkedin or Facebook messages

• Action
  List Projects

  List all projects in the account. GET /projects.

• Action
  List Workspace Templates

  List the workspace's shared template library. GET /workspace-templates.

• 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}.

No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.