Actions68
- Custom Field Actions
- Custom Field Block Actions
- Custom Field Type Actions
- Customer Actions
- Deal Actions
- Lead Actions
- Organization Actions
- Pipeline Actions
- Prospect Actions
- Staff Actions
- Task Actions
- Workspace Actions
Overview
This node integrates with the Magnet Customer API to retrieve detailed information about prospects. Specifically, the "Get" operation for the "Prospect" resource fetches a single prospect's data by its unique ID. This is useful in scenarios where you want to enrich your workflow with up-to-date prospect details, such as contact information, status, or custom fields.
Practical examples include:
- Fetching a prospect's profile before sending a personalized email campaign.
- Retrieving prospect data to update CRM records or trigger follow-up tasks.
- Accessing prospect custom fields to segment or qualify leads dynamically.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authentication to use: either API Token or OAuth2. |
| Contact ID | The unique identifier of the prospect to retrieve. |
| Resolve Custom Fields | When enabled, custom fields and option fields are returned with their actual names/values instead of IDs. |
Note: Several hidden properties related to "Life Cycle" and "Source" exist but are preset internally and not exposed for user input.
Output
The output JSON contains the full data object of the requested prospect as returned by the Magnet Customer API. This includes standard prospect fields (e.g., name, email, status) and any associated custom fields.
If the "Resolve Custom Fields" option is enabled, custom field IDs are automatically replaced with their corresponding names and values for easier consumption.
The node does not output binary data.
Dependencies
- Requires an active connection to the Magnet Customer API.
- Supports two authentication methods: API Token or OAuth2 credentials.
- No additional environment variables are needed beyond the configured credentials.
Troubleshooting
- Invalid Prospect ID: If the provided prospect ID does not exist or is malformed, the API will return an error. Verify the ID is correct.
- Authentication Errors: Ensure that the selected authentication method is properly configured with valid credentials.
- Custom Field Resolution Issues: Enabling "Resolve Custom Fields" requires additional API calls; if these fail, custom fields may not resolve correctly. Check API permissions and connectivity.
- Rate Limits: Excessive requests may be throttled by the API. Implement retry logic or reduce request frequency.
Links and References
- Magnet Customer API Documentation
- n8n Documentation on Creating Custom Nodes
- OAuth2 Authentication Guide in n8n: https://docs.n8n.io/credentials/oauth2/