Actions10
Overview
This node integrates with the Corbee CRM API to manage customer and attendance (service interaction) data. Specifically, the "Adicionar Cliente E Atendimento" operation allows users to create a new customer record and simultaneously register an associated attendance (service interaction or appointment) in the CRM system.
This operation is useful in scenarios where you want to onboard a new client and immediately log their first service interaction, such as when registering a new lead and scheduling their initial consultation or support session.
Practical examples:
- A sales team capturing a new prospect's details and logging their first meeting.
- Customer support creating a new client profile while recording the first support ticket or call.
- Marketing campaigns registering new customers and associating them with specific campaign stages or benefits.
Properties
| Name | Meaning |
|---|---|
| Nome | Full name of the customer. |
| CPF | Customer's CPF number (Brazilian individual taxpayer registry), only digits are sent. |
| Data De Nascimento | Customer's birth date in DD/MM/YYYY format. |
| Customer's email address. | |
| Telefone | Customer's phone number. |
| ID Da Etapa | Funnel stage ID for the attendance (service interaction). |
| Nome Da Campanha | Name of the marketing campaign associated with this attendance. |
| Benefício | Code of the benefit associated with the customer or attendance. |
| ID Do Órgão | Numeric ID of the organization related to the attendance. |
| ID Da Origem | Numeric ID representing the origin/source of the attendance. |
Output
The node outputs JSON data representing the response from the Corbee CRM API after creating the customer and attendance. This typically includes the newly created customer and attendance records with their respective IDs and details as returned by the API.
No binary data output is produced by this operation.
Dependencies
- Requires an API key credential for authenticating with the Corbee CRM API.
- The node uses the CorbeeHelpers class internally to handle API requests and data normalization.
- Proper configuration of the API credentials in n8n is necessary for successful operation.
Troubleshooting
Common issues:
- Invalid or missing API credentials will cause authentication failures.
- Incorrect formatting of CPF (should be numeric only) may result in validation errors.
- Missing required fields like "Nome" (customer name) can cause the API to reject the request.
- Providing invalid funnel stage IDs or organization IDs may cause the API to return errors.
Error messages:
"Opera\xE7\xE3o n\xE3o suportada"(Operation not supported): Indicates an unsupported operation was requested; ensure the correct operation name is selected.- Validation errors related to CPF or other fields usually indicate incorrect input formats; verify inputs conform to expected formats.
- Network or API errors suggest connectivity or server-side issues; check API availability and network settings.