Notificações Inteligentes icon

Notificações Inteligentes

NI Integration
Join our community

Actions48

Overview

This node operation updates an existing lead's information in a CRM or marketing system. It allows users to modify various details of a lead such as their name, phone number, email, notes, custom variables, and tracking data related to advertising and user behavior.

Common scenarios where this node is beneficial include:

  • Keeping lead information up-to-date after receiving new contact details.
  • Adding or modifying custom attributes for segmentation or personalization.
  • Updating tracking parameters to better attribute leads to marketing campaigns.
  • Enriching lead profiles with additional notes or remarks.

For example, a marketing automation workflow could use this node to update a lead’s phone number and add campaign tracking data after a form submission.

Properties

Name Meaning
Lead ID The unique identifier of the lead to update. This is required to specify which lead record will be modified.
Lead Name The full name of the lead. Used to update or set the lead’s name.
Phone The lead’s phone number including the country code prefix with a plus sign (e.g., +1, +55). Required when updating the phone.
Email Optional email address of the lead. Can be updated or added.
Notes Additional notes or remarks about the lead. Useful for adding context or comments.
Custom Variables A collection of custom key-value pairs to add or update on the lead. Each variable has a slug (identifier) and a value. Allows flexible extension of lead data with custom fields.
Tracking Data Various tracking parameters related to advertising and analytics platforms. Includes identifiers from Facebook Ads, Google Ads, LinkedIn, TikTok, Twitter, Taboola, and others, as well as campaign and source metadata.

Output

The node outputs JSON data representing the updated lead object returned by the API. This typically includes the lead’s current state after the update, reflecting all changed properties.

If the node supports binary data output, it would represent attachments or files related to the lead, but based on the provided code and properties, this node primarily deals with JSON data.

Dependencies

  • Requires an API key credential or similar authentication token configured in n8n to access the external lead management service.
  • Makes HTTP requests to the external API endpoint https://api.notificacoesinteligentes.com to perform operations.
  • The node uses built-in n8n helper methods for authenticated HTTP requests.

Troubleshooting

  • Missing Lead ID: The update operation requires a valid lead ID. Ensure the "Lead ID" property is provided and correct.
  • Invalid Phone Format: Phone numbers must include the plus sign (+) prefix followed by the country code. Omitting this may cause errors.
  • API Authentication Errors: If the API key or authentication token is invalid or missing, the request will fail. Verify credentials are correctly set up in n8n.
  • Network Timeouts: The HTTP request timeout is set to 5 seconds. Slow network or API issues might cause timeouts; consider increasing timeout if needed.
  • Invalid Custom Variable Slugs: Custom variables require valid slugs. Incorrect slugs may result in the API rejecting the update.
  • Tracking Data Misconfiguration: Ensure tracking parameters correspond to expected formats and values to avoid API validation errors.

Links and References

Discussion