Connect SendGrid to Simpleen Translation

Both apps 27SendGrid 14Simpleen Translation 13

• Trigger
  New bounce

  Polls the v3 Suppression Bounces API for bounced email addresses. Emits one record per bounce.

• Trigger
  New global suppression

  Polls the v3 Suppressions API for globally-suppressed (unsubscribed) email addresses. Emits one record per suppressed email.

• Trigger
  New or updated recipient

  Triggered when a recipient is created or updated.

• Trigger
  New suppressed email

  Triggered when a new email is suppressed.

• Action
  Add to suppression group

  Add a recipient's email to a SendGrid suppression group (unsubscribe group). POST /v3/asm/groups/{group_id}/suppressions.

• Action
  Create custom field

  Creates a new custom field.

• Action
  Create list

  Creates a new marketing contact list via the v3 Marketing Lists API.

• Action
  Create or update contact

  Adds or updates a marketing contact (upsert by email) via the v3 Marketing Contacts API. Optionally assigns to lists.

• Action
  Create or update recipient

  Creates a new recipient if the email does not exist, otherwise updates the existing recipient.

• Action
  Delete contacts

  Deletes one or more marketing contacts by their contact IDs via the v3 Marketing Contacts API.

• Action
  Get contact by email

  Looks up a marketing contact by email address via the v3 Marketing Contacts search-by-emails endpoint.

• Action
  Remove from suppression group

  Remove a recipient's email from a SendGrid suppression group (unsubscribe group). DELETE /v3/asm/groups/{group_id}/suppressions/{email}. Returns 204 No Content on success.

• Action
  Send an email

  Sends an email via the v3 Mail Send API to a single recipient with subject and plain-text or HTML body.

• Action
  Send an email using template

  Sends an email via the v3 Mail Send API using a dynamic template ID. Dynamic template data is passed as a JSON object.

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