Connect Chaport to Caspio

Both apps 28Chaport 20Caspio 8

• 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
  Deleted Record

  Fires when a record is deleted from the selected Caspio table. Instant self-registering webhook (table.recordDelete) — picking this trigger and a Table auto-registers the Caspio webhook on activation, scoped to that table.

• Trigger
  New or Updated Record

  Fires when a record is inserted or updated in the selected Caspio table. Instant self-registering webhook registering both table.recordInsert and table.recordUpdate — picking this trigger and a Table auto-registers the Caspio webhook on activation, scoped to that table.

• Trigger
  New Record

  Fires when a new record is inserted into the selected Caspio table. Instant self-registering webhook (table.recordInsert) — picking this trigger and a Table auto-registers the Caspio webhook on activation, scoped to that table. Payload: trigger.body = {data:[record...], objectName, eventType, eventDate, eventId, ...}.

• Trigger
  Updated Record

  Fires when a record's field value changes in the selected Caspio table. Instant self-registering webhook (table.recordUpdate) — picking this trigger and a Table auto-registers the Caspio webhook on activation, scoped to that table.

• Action
  Download File from Field

  Download the file stored in an Attachment-type field of a specific record. Returns the raw file content.

• Action
  Find Records

  Query records from a selected Caspio table with an optional WHERE filter, ORDER BY, and limit. Returns the matching records.

• Action
  Find View Records

  Query records from a Caspio View (a saved joined/filtered/aggregated dataset spanning tables). Optional WHERE / ORDER BY / limit.

• Action
  Upload File to Field

  Upload a file (from a URL) into an Attachment-type field of a specific record. Table from a dropdown, the attachment field and record ID (the record's primary-key value) are supplied per call. Requires an Attachment-type column (not the legacy File type).

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