Connect Quilia to Stedi

Both apps 30Quilia 21Stedi 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.

• Action
  Add event destination

  Create a new event destination for receiving Stedi webhook events.

• Action
  Check eligibility

  Runs a real-time eligibility and benefits check (X12 270/271) against a payer for a patient and returns the payer's coverage and benefits response.

• Action
  Delete event destination

  Permanently deletes a Stedi event destination so it stops receiving events. This cannot be undone; to pause delivery instead, update the destination's status to DISABLED.

• Action
  Find payers by criteria

  Searches the Stedi Payer Network for payers matching a name, payer ID or alias, optionally filtered by supported transaction types, coverage types, operating states and insurance programs. Returns matching payers ranked by relevance.

• Action
  Get event destination

  Retrieve an event destination by id.

• Action
  Get payer

  Retrieve a single payer record by id.

• Action
  List event destinations

  Lists the event destinations configured in your Stedi account, optionally filtered by status or event type.

• Action
  List payers

  Lists every payer Stedi supports, with payer IDs, aliases, supported transactions and enrollment requirements.

• Action
  Update event destination

  Updates an existing Stedi event destination's name, URL, subscribed event types, description, status or concurrency limit. Fields left blank are not changed.

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