Connect Caspio to Simpleen Translation

Both apps 21Caspio 8Simpleen Translation 13

• Trigger
  Deleted Record

  Fires when a record is deleted from the selected Caspio table. Instant self-registering webhook (table.recordDelete) — picking this trigger and a Table auto-registers the Caspio webhook on activation, scoped to that table.

• Trigger
  New or Updated Record

  Fires when a record is inserted or updated in the selected Caspio table. Instant self-registering webhook registering both table.recordInsert and table.recordUpdate — picking this trigger and a Table auto-registers the Caspio webhook on activation, scoped to that table.

• Trigger
  New Record

  Fires when a new record is inserted into the selected Caspio table. Instant self-registering webhook (table.recordInsert) — picking this trigger and a Table auto-registers the Caspio webhook on activation, scoped to that table. Payload: trigger.body = {data:[record...], objectName, eventType, eventDate, eventId, ...}.

• Trigger
  Updated Record

  Fires when a record's field value changes in the selected Caspio table. Instant self-registering webhook (table.recordUpdate) — picking this trigger and a Table auto-registers the Caspio webhook on activation, scoped to that table.

• Action
  Download File from Field

  Download the file stored in an Attachment-type field of a specific record. Returns the raw file content.

• Action
  Find Records

  Query records from a selected Caspio table with an optional WHERE filter, ORDER BY, and limit. Returns the matching records.

• Action
  Find View Records

  Query records from a Caspio View (a saved joined/filtered/aggregated dataset spanning tables). Optional WHERE / ORDER BY / limit.

• Action
  Upload File to Field

  Upload a file (from a URL) into an Attachment-type field of a specific record. Table from a dropdown, the attachment field and record ID (the record's primary-key value) are supplied per call. Requires an Attachment-type column (not the legacy File type).

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