Connect Casebook and Chaport

Both apps 37Casebook 17Chaport 20

• Trigger
  New Case

  Triggers when a new case is created in Casebook.

• Trigger
  New Intake Report

  Triggers when a new intake report is created in Casebook.

• Trigger
  New Person

  Triggers when a new person is created in Casebook.

• Action
  Add a Person to a Case

  Adds a person to a Casebook case.

• Action
  Create a Case

  Creates a new case in Casebook with a name, description and case type.

• Action
  Create an Intake Report

  Creates a new intake report in Casebook with a name, narrative and report type.

• Action
  Create a Note

  Creates a note in Casebook, optionally attached to a person, case or other record.

• Action
  Create a Person

  Creates a new person in Casebook with their name and basic demographics.

• Action
  Create a Provider

  Creates a new provider in Casebook with a name and contact details.

• Action
  Delete a Person

  Deletes a person in Casebook. The record is hidden from view, not permanently purged.

• Action
  Find People

  Finds Casebook people by first name, last name or date of birth and returns the first match.

• Action
  Get a Case

  Returns one Casebook case by ID, including its name and description.

• Action
  Get an Intake Report

  Returns one Casebook intake report by ID, including its name, narrative and when it was reported.

• Action
  Get a Person

  Returns one Casebook person by ID, including name, date of birth and other demographics.

• Action
  Get a Provider

  Returns one Casebook provider by ID, including its name, email and phone number.

• Action
  Update a Case

  Updates a Casebook case's name, description or goals. Only the fields you fill in are changed.

• Action
  Update a Person

  Updates a Casebook person's name or demographics. Only the fields you fill in are changed.

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

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