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 manage phone records associated with contacts. Specifically, the "Phone" resource with the "Create" operation allows users to add a new phone number to an existing contact in the CRM system.
This node is beneficial in scenarios where automated workflows need to enrich contact information by adding phone numbers dynamically, such as during lead capture, customer onboarding, or data synchronization processes.
Practical example:
When a new lead is captured via a web form, this node can be used to automatically add their phone number to their contact record in Arivo CRM, ensuring that sales and support teams have up-to-date contact details.
Properties
| Name | Meaning |
|---|---|
| Contact ID | The unique identifier of the contact to which the phone number will be added. |
| Phone Number | The actual phone number including area code to be added to the contact's record. |
| Phone Type | The category of the phone number. Options: Work, Cell, Home, Fax. |
Output
The node outputs JSON data representing the newly created phone record in Arivo CRM. This typically includes details such as the phone number, its type, and the associated contact ID, along with any metadata returned by the CRM API confirming successful creation.
No binary data output is involved in 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 being accessible and the provided credentials having permissions to create phone records for contacts.
Troubleshooting
Common issues:
- Invalid or missing Contact ID: The node requires a valid contact identifier; ensure the Contact ID exists in Arivo CRM.
- Incorrect phone number format: The phone number should include the area code and be formatted according to expected standards.
- Insufficient permissions: The API key must have rights to modify contact phone data.
- Network or API errors: Connectivity issues or API downtime may cause failures.
Error messages:
- Errors related to authentication usually indicate invalid or expired API credentials.
- Validation errors from the API may indicate missing required fields or incorrect data formats.
- If the node throws an error about the contact not found, verify the Contact ID correctness.
Resolving these typically involves verifying input data, checking API credentials, and ensuring network connectivity.
Links and References
- Arivo CRM Official Documentation (example placeholder link)
- n8n Documentation on Creating Custom Nodes
- General best practices for phone number formatting: E.164 Standard