Actions58
- Lead Management Actions
- User Agent Management Actions
- Campaign Management Actions
- Phone DID Management Actions
- List Management Actions
- Reporting Monitoring Actions
- System Info Actions
- Other Operations Actions
Overview
This node interacts with a Lead Management API to retrieve comprehensive information about a specific lead. It is designed to fetch all available data related to a lead, including optional custom fields and archived status, based on the provided lead ID and other parameters.
Common scenarios where this node is beneficial include:
- Enriching CRM records by pulling detailed lead data.
- Automating workflows that require up-to-date lead information for decision-making.
- Integrating lead data into marketing or sales automation pipelines.
For example, a user might use this node to get all details of a lead before sending a personalized email campaign or updating a sales dashboard.
Properties
| Name | Meaning |
|---|---|
| Function | API function name; fixed to "Lead All Info" for this operation. |
| User | API user credential used for authentication. |
| Pass | API password credential used for authentication. |
| Source | Description of what originated the API call (default: "n8n"). |
| Lead Id | The unique identifier of the lead to retrieve information for. |
| Phone Number | Optional phone number associated with the lead (6-16 digits). |
| Custom Fields | Whether to include custom fields in the output; options: "Y" (yes), "N" (no). |
| Force Entry List Id | Optional parameter to force a specific entry list ID. |
| Archived Lead | Whether to include archived leads; options: "Y" (yes), "N" (no). |
| Stage | Output format of the response; options: "csv", "tab", "pipe", "json". |
| Header | Whether to include a header row in the output; options: "YES", "NO". |
Output
The node outputs the retrieved lead information in the json field of the output data. The structure depends on the selected output format (Stage property):
- If
jsonis selected, the output will be structured JSON representing all lead details. - For
csv,tab, orpipeformats, the output will be a string formatted accordingly, optionally including a header row if enabled.
No binary data output is indicated.
Dependencies
- Requires an API key credential consisting of a username and password for authenticating with the Lead Management API.
- The node sends HTTP requests to the configured API endpoint using these credentials.
- No additional external dependencies are indicated.
Troubleshooting
- Authentication errors: Ensure that the correct API user and password are provided and valid.
- Invalid Lead Id: Providing a non-existent or malformed lead ID may result in empty or error responses.
- Output format issues: Selecting an unsupported output format or mismatched header option might cause parsing problems downstream.
- Network connectivity: Verify that the API endpoint is reachable from the n8n environment.
Common error messages likely relate to authentication failure, missing required parameters (like Lead Id), or invalid query parameters. Resolving these typically involves verifying credentials, input values, and network access.
Links and References
- Refer to the Lead Management API documentation for detailed descriptions of parameters and response formats.
- n8n documentation on HTTP Request nodes and credential management for setting up API authentication.