Clinicorp
Read and write data in Clinicorp, the dental and clinic management platform. Query estimates (orçamentos), patients, appointments (agenda), financial reports, payments, sales and conversion, procedures, professionals, clinics, CRM leads, analytics and goals; and create patients, appointments, CRM leads and purchase orders. Conventions: dates are sent as YYYY-MM-DD and times as 24-hour HH:mm; IDs (clinic, professional, status) must come from the matching list operation, never invented; the Subscriber ID is read automatically from the credential, so it is never an input. To book an appointment, first read availability (Clinic > Get Available Times, or Appointment > Get Available Times when using a booking Code Link), then call Appointment > Create with that exact slot. Usable as an AI Agent tool.
Actions47
- Analytics Actions
- Appointment Actions
- Clinic Actions
- CRM Actions
- Estimate Actions
- File Actions
- Financial Actions
- Group Actions
- Migration Actions
- Operational Actions
- Patient Actions
- Payment Actions
- Procedure Actions
- Product Actions
- Professional Actions
- Sales Actions
- User Actions
File → Upload
AI-generatedSummary
Uploads a file, image, or document to Clinicorp by sending a one-item request to its file upload endpoint. Provide a public URL or a local file reference; optionally associate the upload with a patient and set a callback URL for the result.
Inputs
- URL — Public URL of the file. The source includes it in the request only when non-empty.
- Additional Fields → Local File — Path or reference to a local file; included only when non-empty.
- Additional Fields → Patient ID — Patient ID to associate with the upload; included in the API request as
PatinetIdwhen non-empty. - Additional Fields → Patient Name — Patient name to associate with the upload; included only when non-empty.
- Additional Fields → Response Webhook URL — URL Clinicorp can call with the upload result; included only when non-empty.
Output shape
The Clinicorp API response, converted into n8n JSON output items.
The node sends one request body item containing the supplied non-empty fields. The operation does not require any of these fields in the UI; the response structure depends on the API.