Notificações Inteligentes icon

Notificações Inteligentes

NI Integration
Join our community

Actions48

Overview

This node handles the creation or updating of leads in a marketing or CRM system. It allows users to add new leads or update existing ones with detailed contact information, notes, custom variables, tags, and tracking data. This is useful for automating lead management workflows, syncing lead data from various sources, or enriching lead profiles with additional metadata.

Practical examples:

  • Automatically creating a new lead when a form is submitted on a website.
  • Updating an existing lead’s phone number or notes after a customer interaction.
  • Adding marketing tags and tracking parameters to leads for better segmentation and campaign analysis.

Properties

Name Meaning
Lead Name The full name of the lead. Required for both creating and updating leads.
Phone The lead’s phone number including country code with a plus sign prefix (e.g., +55, +1). Required for create and update operations.
WARNING! You must include the plus sign (+) prefix with the number; Ex: | +55 | +1 A notice reminding users to include the plus sign prefix in the phone number.
Email The lead’s email address. Required when creating a lead but not mandatory for updates.
Notes Additional remarks or notes about the lead. Optional.
Custom Variables A collection of custom key-value pairs (slug and value) to add or update custom variables associated with the lead. Multiple variables can be added at once.
Tags Free text field to add, update, or remove tags related to the lead.
Selectable Tags A multi-select list of pre-existing tags available in the account that can be assigned to the lead.
Tracking Data A collection of optional tracking parameters such as user agent, IP address, advertising click identifiers (Google Ads, Facebook Ads, TikTok, LinkedIn, etc.), UTM campaign details, and other marketing attribution data.

Output

The node outputs JSON data representing the created or updated lead object returned by the API. This typically includes the lead’s unique identifier, contact details, tags, custom variables, notes, and any tracking data stored.

If the node supports binary data output (not indicated here), it would represent files or attachments related to the lead, but this node primarily deals with JSON lead data.

Dependencies

  • Requires an API key credential for authenticating requests to the external lead management service.
  • Uses HTTP requests to communicate with the service’s REST API endpoint.
  • The node dynamically loads selectable tags via an authenticated API call to /tags endpoint.
  • Network connectivity and proper API permissions are necessary.

Troubleshooting

  • Missing required fields: Errors may occur if required fields like Lead Name, Phone (with plus prefix), or Email (for creation) are missing. Ensure these are provided.
  • Invalid phone format: The phone number must include the country code with a plus sign prefix. Omitting the plus sign will likely cause validation errors.
  • API authentication failures: If the API key or token is invalid or expired, the node will fail to authenticate. Verify credentials and permissions.
  • Tag loading issues: If the selectable tags fail to load, check network connectivity and API access rights.
  • Timeouts: The node uses a 5-second timeout for tag loading requests; slow networks might cause timeouts.
  • Custom variables formatting: Ensure custom variables are provided as slug-value pairs; incorrect structure may cause request failures.

Links and References

Note: The above summary is based solely on static analysis of the provided source code and property definitions.

Discussion