Integrations/NicoApps (MiniApps) Nativos/Sistemas de Negócios Locais/Clinicorp

Clinicorp

Clinicorp is a management system for medical and dental clinics (calendar, patient records, estimates/treatments, lead CRM). The NicoChat Clinicorp NicoApp integrates the channel with Clinicorp.

2026-08-12
Note
Available in the NicoApps tab. Integration base: Clinicorp REST API (https://api.clinicorp.com/rest/v1/...).

How to get the credentials

Username: Enter the System access ID.

Password: Enter the API Token.

How to find this information:

  • Log in to the System.
  • Click Manage Subscription.
  • Click External Access and Integrations.
  • Under Integrations: API User (Username) | API Token (Password).

Limitations

Note
Request limits (rate limit) and specific plan requirements are not publicly disclosed by Clinicorp. Check with Clinicorp support before sizing high-volume flows (e.g., an AI agent responding in real time).

What the NicoApp does

Action
What it does
Main inputs
Endpoint
Return all users
Lists the users (members) registered in the account
None (uses the account credentials)
GET /security/list_users
List Clinics
Lists the account's clinics/branches
None (uses the account credentials)
GET /business/list
List available schedules
Lists the free slots in a professional's calendar within a period
Professional ID, Clinic ID, Start Date, End Date
GET /business/list_available_times
Search for a Patient
Searches for an existing patient by name, phone, e-mail or ID
Name, Phone, E-mail or Patient ID (at least one)
GET /patient/get
Create a Patient
Registers a new patient
Name (required); Date of Birth, Gender, E-mail, Mobile, CPF/Document, Notes
POST /patient/create
Create Appointment
Creates an appointment; if the patient is given by name and does not yet exist in Clinicorp, the flow itself searches for the patient before scheduling
Patient Name/ID, Mobile, E-mail, Date, Start Time, End Time, Clinic ID, Dentist ID
POST /appointment/create_appointment_by_api
Retrieve an Appointment
Retrieves the details of an appointment by ID
Appointment ID
GET /appointment/get_appointment
Return a patient's appointment data
Lists appointments filtered by period, clinic and/or patient
Start Date, End Date, Clinic ID, Patient ID
GET /appointment/list
Confirm Appointment
Marks an existing appointment as confirmed
Appointment ID
POST /appointment/confirm_appointment
Cancel Appointment
Cancels an existing appointment
Appointment ID
POST /appointment/cancel_appointment
Return all the clinic's estimates
Lists a clinic's estimates/treatments within a period
Start Date, End Date, Clinic ID
GET /estimates/list
Return a patient's estimates
Returns the estimate for a specific treatment
Treatment ID
GET /estimates/get
Add Lead to CRM
Creates a lead in a board/pipeline of Clinicorp's CRM
Name, E-mail, Phone, Board Name (BoardName), Notes
POST /crm/add_leads

Tips and notes

  • Standard error handling: all actions follow the same pattern — if Clinicorp returns an error, the action takes the block's failure path (action_failed), carrying the actual error message returned by the API. Use this path to handle exceptions in the flow (e.g., patient not found, non-existent appointment).
  • Create Appointment resolves the patient automatically: if the appointment is created with the patient's name only (without an ID), the NicoApp first tries to locate a patient with the same name before proceeding — avoiding duplicate records.
  • Multiple calendars/branches on the same credentials: the authentication fields (user, token and calendar) accept comma-separated values, allowing the same installation to serve more than one calendar/branch of the clinic.
Note
A legacy action named "Cria uma solicitação de agendamento ❌" was found in the NicoApp structure — the name (with the "broken" emoji) suggests it is inconsistent or discontinued. For that reason, it was not included in the actions table above. We recommend reviewing this action in the NicoApp builder and either removing or fixing it.