Connect Quilia and Wachete

Both apps 30Quilia 21Wachete 9

• Trigger
  Appointment Created

  Triggers when a new appointment is created in Quilia.

• Trigger
  Appointment Updated

  Triggers when an appointment is updated in Quilia.

• Trigger
  New Client Activity

  Triggers when a client performs an activity in Quilia, such as uploading a document to their case.

• Action
  Add New Client

  Creates a new client in Quilia with their name, phone, email, address and date of birth.

• Action
  Create Contact

  Creates a contact (such as a witness, adjustor, employer or medical provider) attached to a case or a client.

• Action
  Delete a Contact

  Permanently deletes a company or people contact from your Quilia organization.

• Action
  Delete Case

  Permanently deletes a case, including its members, documents and chat history.

• Action
  Delete Client

  Permanently deletes a client from your firm, including their case memberships.

• Action
  Delete Documents

  Deletes one or more Quilia documents, removing both the records and their stored files.

• Action
  Find a Document

  Finds a document by its id and returns its type plus a secure download link that expires after 30 minutes.

• Action
  Find Client by Phone

  Finds a client in your firm by phone number and returns the client record with the cases they belong to.

• Action
  Invite Clients to Case

  Invites clients or staff to a Quilia case. Clients are texted an invite; staff are added as invited. Returns who was invited and who was skipped.

• Action
  List Clients

  Returns the firm's clients, optionally filtered by name, email or phone.

• Action
  List Webhook Events

  Returns the webhook events your Quilia firm can subscribe to, with their descriptions and payload schemas.

• Action
  Retrieve a Single Client

  Returns a single client by id, including the cases the client belongs to.

• Action
  Retrieve Individual Case

  Returns one case by its ID, including its status, type, dates, client, organization and case members.

• Action
  Simulate Webhook Event

  Sends a sample Quilia webhook event to an endpoint URL so you can test a webhook integration.

• Action
  Update a Contact

  Updates an existing Quilia contact (a company or a person). Only the fields you fill in are changed.

• Action
  Update Case

  Updates an existing case's status, type, opening date or custom CMS data. Only the fields you fill in are changed.

• Action
  Update Client Information

  Updates an existing client's contact details, address and demographic information. Only the fields you fill in are changed.

• Action
  Upload Documents

  Uploads a document file to a client's case in Quilia and returns the new document ids.

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