RitsaAI ToolInstall

Summary

Runs a selected Ritsa CRM action, such as searching customers, managing appointments, sending messages, handling sales and payments, or retrieving CRM summaries. Choose an action and provide its relevant fields; the node sends the request to the configured CRM branch and returns the API response as workflow data.

Inputs

• action (required) — Select the CRM action. The default is getCustomers; available actions cover customers, appointments, messages, opportunities, POS, callbacks, automations, dashboard data, services, staff, branches, stock, and pre-consultations.
• customerName — Customer name for actions that use or identify a customer. The node searches the branch’s customers and uses the first match. If no match is found for an action that needs a customer, it returns an instruction to create the customer first.
• phone — Customer phone for customer and pre-consultation creation or updates, and appointment status changes, rescheduling, or cancellation. For appointment changes, a phone mismatch with the appointment owner prevents the change.
• source — Lead source for creating a pre-consultation; defaults to manual if omitted.
• sector — Interested service or sector for creating a pre-consultation.
• countryCode — Country code for creating a pre-consultation; can be left blank.
• serviceName — Service name for appointment creation or availability checks. The node resolves it by matching a service name; if no match is found, it returns available services.
• staffName — Staff name for appointment creation, rescheduling, or availability checks. A supplied name must match a staff member or the action stops and returns available staff. For appointment creation only, leaving it blank selects the first staff member.
• date — Date in YYYY-MM-DD format for appointment listing, creation, rescheduling, and availability checks.
• time — Time in HH:MM format for appointment creation or rescheduling. Rescheduling requires date and time together if changing the appointment time.
• searchQuery — Search text for customers, products/stock, or pre-consultations.
• notes — Notes for appointments, callbacks, or pre-consultations; used as the cancellation reason for appointment cancellation.
• messageContent — Message text for sendMessage, which sends through the WhatsApp channel.
• newStatus — New status for appointment, opportunity, or pre-consultation updates.
• netAmount — Net amount in TL for sales or payments. If payment methods are omitted or empty, the node uses a cash method for this amount.
• discountAmount — Discount amount in TL for sales or payments.
• saleItemsJson — JSON array of sale items for makeSale, for example [ {"name":"Lazer","quantity":1,"unit_price":350} ].
• paymentMethodsJson — JSON array of payment methods for sales or payments, for example [ {"method":"cash","amount":350} ]. If empty, the node creates a cash payment using netAmount.
• referenceId — Record ID used by detail, update, reschedule, cancellation, collection, refund, callback, automation, and pre-consultation actions. For appointment changes, first obtain the appointment ID from getAppointments.
• branchId — Branch ID for the request. If omitted or zero, the node uses the branch ID from credentials, falling back to 1.
• extraJson — Optional JSON object for additional fields. Used by selected actions; for example, toggleSession reads sessionAction (defaults to open), and createCallback reads callAt. Invalid JSON falls back to an empty object.

Output shape

A list of n8n items, one per input item, each containing the action response in its json field.

Successful actions return the CRM API response. Some lookup or validation failures are returned as success: false data with guidance or available choices; request errors are thrown unless the node is configured to continue on fail, in which case an error object is returned.

Links

• n8n community nodes installation guide