Connect Salesforce to Simpleen Translation

Both apps 24Salesforce 11Simpleen Translation 13

• Trigger
  New object record

  Polling trigger: fires for each new record created in the specified SObject type. Polls SOQL ordered by CreatedDate descending.

• Trigger
  New or updated object record

  Polling trigger: fires for each record created or modified in the specified SObject type. Polls SOQL ordered by SystemModstamp descending.

• Action
  Create object record

  Creates a new record of the specified SObject type (standard or custom, e.g. Account, Contact, Lead, Opportunity, Case, or MyObject__c) with the supplied field values.

• Action
  Delete object record

  Deletes an existing SObject record by object type and record ID.

• Action
  Describe object

  Returns the full field and metadata description (describe) for an SObject type — useful for discovering available fields and their API names.

• Action
  Find most recent created or updated record

  Returns the single most recently created or last-modified record for the specified SObject type (ordered by SystemModstamp DESC, LIMIT 1).

• Action
  Find object records

  Finds matching records for an SObject type by a field/value equality match via SOQL. Returns Id and the requested fields for all matches.

• Action
  Get object record

  Retrieves a single SObject record by object type and record ID. Optionally restrict returned fields with a comma-separated 'fields' list.

• Action
  List objects

  Lists all available SObject types (standard and custom) on the org.

• Action
  SOQL query

  Executes a SOQL query against the org and returns matching records. Example: SELECT Id, Name FROM Account WHERE CreatedDate = TODAY.

• Action
  Update object record

  Updates an existing SObject record by object type and record ID with the supplied field values. Salesforce returns no body on success (HTTP 204).

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