Actions104
- Custom Field Actions
- Custom Field Block Actions
- Custom Field Type Actions
- Customer Actions
- Deal Actions
- Lead Actions
- Meeting Actions
- Meeting Room Actions
- Meeting Type Actions
- Organization Actions
- Pipeline Actions
- Prospect Actions
- Staff Actions
- Task Actions
- Ticket Actions
- Treatment Actions
- Treatment Type Actions
- Workspace Actions
Lead → Get
AI-generatedOverview
This node interacts with the Magnet Customer API to retrieve detailed information about a specific lead by its ID. It supports authentication via API Token or OAuth2. The node can optionally resolve custom fields to return their actual names and values instead of just IDs, enhancing the readability and usability of the lead data. This is useful in scenarios where users need to fetch and work with lead data in workflows, such as CRM integrations, lead management, or marketing automation.
Use Case Examples
- Retrieve a lead's full details by providing the lead ID to integrate with a CRM system.
- Fetch lead information and resolve custom fields to display user-friendly data in reports or dashboards.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method used to authenticate API requests, either API Token or OAuth2. |
| Contact ID | The unique identifier of the lead to retrieve. This is a required field for the get operation on leads. |
| Resolve Custom Fields | If enabled, custom fields and option fields in the lead data are resolved to their actual names and values instead of just IDs, making the data more readable and meaningful. |
Output
JSON
_id- Unique identifier of the lead.name- Name of the lead.email- Email address of the lead.phone- Phone number of the lead.customFields- Custom fields associated with the lead, resolved to actual names and values if the option is enabled.createdAt- Timestamp when the lead was created.updatedAt- Timestamp when the lead was last updated.
Dependencies
- Magnet Customer API
Troubleshooting
- Ensure the provided Contact ID (leadId) is valid and exists in the Magnet Customer system to avoid 'not found' errors.
- Check that the correct authentication method is selected and credentials are valid to prevent authentication failures.
- If custom fields are not resolving correctly, verify that the 'Resolve Custom Fields' option is enabled and that the API user has permissions to access custom field data.