Connect Chaport and ChargeOver

Both apps 41Chaport 20ChargeOver 21

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

  Triggers when a contact is updated in ChargeOver.

• Action
  Add item

  Create an item (product or discount).

• Action
  Add note

  Add a note to a customer, invoice, etc.

• Action
  Add Transaction

  records a payment, refund or credit against a customer (e.g. transaction_type=pay, gateway_method=check, amount) without charging a payment gateway. Creates a transaction record.

• Action
  Cancel a Subscription

  Cancel an existing subscription in ChargeOver.

• Action
  Create a Contact

  Create a new contact in ChargeOver.

• Action
  Create a Customer

  Create a new customer in ChargeOver.

• Action
  Create an Invoice

  Create a new Invoice in ChargeOver.

• Action
  Create a Subscription

  Create a new subscription in ChargeOver.

• Action
  Delete Item

  deletes an item (product/discount) by id.

• Action
  Find Contact

  Finds an existing contact by a specified field.

• Action
  Find Customer

  Finds an existing customer by a specified field.

• Action
  Find Item (Product, Discount)

  Finds an existing item (product, discount) by a specified field.

• Action
  Find Subscription

  Finds an existing subscription by a specified field.

• Action
  List Notes

  Lists the notes attached to a ChargeOver record (customer, invoice, subscription, contact), filtered by record type and record ID.

• Action
  Update a Customer

  Update a existing customer in ChargeOver.

• Action
  Update contact

  Update a user/contact.

• Action
  Update invoice

  Update an invoice.

• Action
  Update item

  Update an item.

• Action
  Update subscription

  Update a subscription (package).

• Action
  Void Transaction

  marks an existing transaction voided in ChargeOver (logs an externally-voided transaction; does not contact the gateway), changing its status.

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