Connect Chaport to SendGrid

Both apps 34Chaport 20SendGrid 14

• Trigger
  Chat Closed (instant)

  Fires when a chat is closed. Webhook event: chat.closed.

• Trigger
  Chat Finished

  Triggers when chat is finished.

• Trigger
  Chat Stage Updated (instant)

  Fires when a chat's stage changes. Webhook event: chat.stageUpdated.

• Trigger
  Message Read (instant)

  Fires when a message is read. Webhook event: message.read.

• Trigger
  New Chat Started

  Triggers when chat is started.

• Trigger
  New Message Sent (instant)

  Fires when a new message is sent in a chat. Webhook event: message.sent.

• Trigger
  New Visitor (instant)

  Fires when a new visitor is created. Webhook event: visitor.created.

• Trigger
  Visitor Updated

  Triggers when visitor data is updated.

• Action
  Create an Operator

  Adds a new operator to your Chaport account and returns the created operator.

• Action
  Delete a Message

  Deletes one message from a Chaport chat. Identify the visitor and the message you want removed.

• Action
  Delete an Operator

  Removes an operator from your Chaport account.

• Action
  List Operators

  Returns every operator in your Chaport account, with each operator's name, email, role and status.

• Action
  List Visitors

  Returns the visitors in your Chaport account, one page at a time.

• Action
  Retrieve an Operator

  Returns one Chaport operator with their name, email, role, job title and current status.

• Action
  Retrieve a Visitor

  Returns one Chaport visitor with their name, contact details, notes and any custom data held about them.

• Action
  Retrieve Last Visitor Chat

  Returns a visitor's most recent Chaport chat, including its stage, operators and — when asked for — the transcript.

• Action
  Send a Message

  Posts a message into a Chaport visitor's chat, starting a chat if there isn't one open.

• Action
  Update an Operator

  Updates a Chaport operator's details. Anything you leave blank keeps its current value.

• Action
  Update a Visitor

  Updates an existing Chaport visitor's contact details, notes and custom data. Only the fields you fill in are changed; blank fields are left untouched.

• Action
  Update Operator Status

  Sets a Chaport operator's availability status, such as online or offline, optionally for a limited time.

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

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