Connect eSignatures to Simpleen Translation

Both apps 28eSignatures 15Simpleen Translation 13

• Trigger
  Contract Signed

  Triggers when a contract is signed by all signers.

• Trigger
  Contract Withdrawn

  Fires when a sent contract is withdrawn/cancelled before signing completes. Webhook event "Contract withdrawn".

• Trigger
  Signer Declined Signature

  Fires when a signer declines to sign the contract. Webhook event "Signer declined the signature".

• Trigger
  Signer Viewed Contract

  Fires when a signer opens/views the contract. Webhook event "Signer viewed the contract".

• Action
  Add Signer

  Add a new signer to an existing contract. POST /api/contracts/:id/signers (Contracts - Signers - Add).

• Action
  Add Template

  Create a new reusable contract template. POST /api/templates (Templates - New).

• Action
  Create Contract

  Creates a new contract.

• Action
  Delete Signer

  Remove a signer from a contract that has not yet signed. DELETE /api/contracts/:id/signers/:signer_id (Contracts - Signers - Delete).

• Action
  Delete Template

  Delete a contract template. DELETE /api/templates/:id (Templates - Delete).

• Action
  Get Contract

  Retrieve a contract's current status, signer states, and metadata. GET /api/contracts/:id (Contracts - Query).

• Action
  Get Template

  Retrieve a contract template's details. GET /api/templates/:id (Templates - Query).

• Action
  List Templates

  List all contract templates in the account. GET /api/templates (Templates - List).

• Action
  Send Contract Draft

  Send a previously created draft contract to its signers. POST /api/contracts/:id/send (Contracts - Send draft).

• Action
  Update Template

  Update an existing contract template's title or settings. PUT /api/templates/:id (Templates - Update).

• Action
  Withdraw Contract

  Withdraw (cancel) a contract that has been sent but not fully signed. POST /api/contracts/:id/withdraw (Contracts - Withdraw).

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