Connect Chaport and SerwerSMS

Both apps 38Chaport 20SerwerSMS 18

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

  Triggers when a new contact is added to the SerwerSMS address book.

• Trigger
  New Message

  Triggers when a new incoming SMS or MMS (reply, ND or NDI message) arrives on the account.

• Action
  Add Blacklisted Phone Number

  Adds a phone number to the blacklist so it receives no messages.

• Action
  Add Contact

  Adds a contact to a group and returns the new contact's ID.

• Action
  Add Sender Name

  Submits a new alphanumeric sender name (up to 11 characters) for SerwerSMS approval.

• Action
  Check Blacklisted Phone Number

  Checks whether a phone number is on the blacklist.

• Action
  Create Group

  Creates a contact group and returns its ID.

• Action
  Delete Contact

  Deletes a contact.

• Action
  Delete Group

  Deletes a contact group, optionally deleting its contacts too.

• Action
  Get Account Limits

  Returns the account type and how many messages of each type (ECO, FULL, MMS, voice, lookup) are left.

• Action
  List Contacts

  Lists contacts, optionally only those in one group or matching a search phrase.

• Action
  List Delivery Reports

  Lists delivery reports of sent messages, filtered by phone number, message ID, status or date range.

• Action
  List Groups

  Lists contact groups with their IDs and contact counts, optionally filtered by name.

• Action
  List Sender Names

  Lists the account's sender names and whether each is approved, pending or rejected.

• Action
  Remove Blacklisted Phone Number

  Removes a phone number from the blacklist.

• Action
  Send SMS

  Sends an SMS with the same text to one phone number. Returns the queued count and the message ID.

• Action
  Update Contact

  Updates an existing contact's details and group.

• Action
  Update Group

  Renames an existing contact group.

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