Connect Casebook and Wachete

Both apps 26Casebook 17Wachete 9

• 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
  Any new notification

  Fires when there is a new change notification from any monitor in your Wachete account.

• Trigger
  New notification for monitor

  Fires when there is a new change notification from the specified Wachete monitor (taskId).

• Action
  Create monitor

  Create a new Wachete monitor (wachet) that watches a web page or part of a page for changes.

• Action
  Delete monitor

  Delete a Wachete monitor by its ID.

• Action
  Get monitor

  Get information about a specific Wachete monitor by its ID.

• Action
  Get monitor data

  Get the captured data/history for a Wachete monitor, optionally as a diff and within a date range.

• Action
  List folders

  List folder contents, optionally under a parent folder.

• Action
  List notifications

  List change notifications, optionally filtered by monitor (taskId) and date range.

• Action
  Update monitor

  Change the settings of an existing Wachete monitor — name, URL, watched/excluded XPath, regex, note, job type, check frequency and location, crawl options, folder, alerts, notification endpoints, headers and proxies. A partial update: the op first reads the monitor's current record, overlays only the fields you filled in, then writes the merged record back, so anything you leave blank keeps its current value — including settings this op does not expose. Identify the monitor by its id. Check frequency is in seconds (86400 = daily) and is ignored if not positive; the true/false options take the words true or false; alerts, notification endpoints, headers and proxies take JSON. Returns the monitor id, name and URL after the update plus the full monitor record.

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