Actions68
- Email Actions
- File Actions
- Note Actions
- Product Category Actions
- Task Actions
- Address Actions
- Company Actions
- Custom Record Actions
- Deal Actions
- Deal Item Actions
- Person Actions
- Phone Actions
- Product Actions
Overview
The node integrates with Arivo CRM to create or update a person record. It allows users to either add a new person or update an existing one by matching on a specified field such as name, email, CPF (Brazilian individual taxpayer registration), or phone number. This operation is useful in scenarios where you want to maintain up-to-date contact information in your CRM without creating duplicates. For example, when importing contacts from another system or updating customer details after a form submission.
Properties
| Name | Meaning |
|---|---|
| Person Name | The full name of the person to create or update (e.g., "Nathan Smith"). |
| Field to Match On | The field used to find an existing person for updating. Options: Name, Email, CPF, Phone. |
| Additional Fields | A collection of optional fields to provide more details about the person: |
| - CPF | Brazilian individual taxpayer registration number. |
| - Birth Date | Person's birth date in YYYY-MM-DD format. |
| - Position | Job position/title of the person (e.g., Software Engineer). |
| - Company ID | Identifier of the company where the person works. |
| One or multiple email addresses with type classification (Work, Personal, Other). | |
| - Phone | One or multiple phone numbers with type classification (Work, Mobile, Home, Other). |
| - Tags | Tags associated with the person for categorization or filtering. |
| - User Name or ID | The user assigned to this person within the CRM. Can be selected from a list or specified via expression. |
| - Team Name or ID | The team assigned to this person within the CRM. Can be selected from a list or specified via expression. |
| - Address | One or multiple addresses with detailed fields including street, city, state, district, country, zip code, and address type (Work, Home, Other). |
| - Custom Fields | Custom fields defined in the CRM for persons. Each custom field requires specifying the field name or ID and its value. |
Output
The node outputs JSON data representing the created or updated person record as returned by the Arivo CRM API. This typically includes all standard and custom fields of the person, such as their unique identifier, name, contact details, company association, tags, and any other metadata stored in the CRM.
No binary data output is indicated for this operation.
Dependencies
- Requires an active connection to Arivo CRM via an API key credential configured in n8n.
- The node depends on the Arivo CRM API to perform create or update operations on person records.
- Some properties load options dynamically (e.g., user and team selections, custom fields) which require proper API access and permissions.
Troubleshooting
- Matching Field Not Found: If the specified match field does not correspond to any existing person, the node will create a new record instead of updating. Ensure the match field is correctly chosen to avoid duplicates.
- Invalid Data Format: Fields like birth date must follow the YYYY-MM-DD format; otherwise, the API may reject the request.
- Permission Errors: Insufficient API permissions can cause failures when trying to create or update persons. Verify that the API key has appropriate rights.
- API Rate Limits: Frequent calls might hit rate limits imposed by Arivo CRM, resulting in errors. Implement retry logic or reduce call frequency if needed.
- Custom Fields Loading Issues: If custom fields do not load properly in the UI, check API connectivity and permissions related to custom field access.
Links and References
- Arivo CRM Official Documentation (generic placeholder, replace with actual URL if available)
- n8n Expressions Documentation – for using expressions in property values such as user or team IDs.