Arivo CRM icon

Arivo CRM

Create and edit data in Arivo CRM

Overview

This node integrates with Arivo CRM to update an existing email record associated with a contact. It allows users to modify details of a specific email address, such as changing the email address itself or updating its type (e.g., work or home). This is useful in scenarios where contact information needs to be kept current, for example, when a client changes their email or when correcting data entry errors.

Practical examples include:

  • Updating a customer's primary email address after they notify support of a change.
  • Changing the classification of an email from "work" to "home" to better reflect contact preferences.

Properties

Name Meaning
Contact ID The unique identifier of the contact whose email is being updated.
Email ID The unique identifier of the email record to update.
Update Fields Collection of fields to update on the email record:
- Email Address: The new email address string.
- Email Type: The category of the email address; options are "Work" or "Home".

Output

The node outputs a JSON object representing the updated email record. This typically includes the updated email address, its type, and identifiers confirming the successful update. The output is paired with the input item index for traceability.

No binary data output is involved.

Dependencies

  • Requires an API key credential for authenticating with Arivo CRM.
  • The node depends on the Arivo CRM API being accessible and properly configured.
  • No additional environment variables are explicitly required beyond the API authentication setup.

Troubleshooting

  • Common Issues:

    • Invalid or missing Contact ID or Email ID will cause the update to fail.
    • Providing invalid email formats or unsupported email types may result in API errors.
    • Network connectivity issues can prevent communication with Arivo CRM.
  • Error Messages:

    • Errors related to authentication indicate problems with the provided API key credential; verify and reconfigure if necessary.
    • Validation errors from the API usually specify which field is incorrect; ensure all required fields are correctly formatted.
    • If the node throws an error about missing parameters, confirm that Contact ID and Email ID are supplied and non-empty.
  • Resolution Tips:

    • Double-check IDs and field values before execution.
    • Use the "Continue On Fail" option to handle partial failures gracefully.
    • Review API limits or permissions if updates are rejected unexpectedly.

Links and References

Discussion