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
The node integrates with the Magnet Customer API to perform operations related to various CRM resources, including Pipelines. Specifically, for the Pipeline resource and the Search operation, it allows users to search pipelines based on customizable filters and sorting options.
This node is beneficial in scenarios where you want to programmatically query pipeline data from Magnet Customer within an n8n workflow. For example, you might want to find all pipelines matching certain criteria (like having interactions or emails) or sort them by creation date to process or analyze them further.
Practical examples:
- Searching pipelines that have associated emails and interactions.
- Sorting pipelines by their creation date in descending order.
- Filtering pipelines using a specific search term.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authentication: "API Token" or "OAuth2". |
| Filters | Collection of filters to narrow down the search results: |
| - Search Term: A string to search for in pipelines. | |
| - Has Emails?: Filter pipelines based on presence of emails ("Any", "Yes (Not Empty)", "No"). | |
| - Has Phones?: Filter pipelines based on presence of phones ("Any", "Yes (Not Empty)", "No"). | |
| - Has Interactions?: Filter pipelines based on presence of interactions ("Any", "Yes", "No"). | |
| Sort | Collection defining sorting preferences: |
| - Sort By: Field to sort by (e.g., "title", "createdAt"). | |
| - Sort Direction: Direction of sorting ("Ascending" or "Descending"). |
Note: There are also hidden properties like "lifeCycle" and "source" preset internally, but these are not exposed for user configuration.
Output
The node outputs JSON data representing the search results from the Magnet Customer API for pipelines. Each item in the output array corresponds to a pipeline object matching the search criteria.
The structure of each JSON object depends on the API response but typically includes pipeline details such as ID, title, stages, creation date, and other metadata.
The node does not output binary data.
Dependencies
- Requires access to the Magnet Customer API.
- Requires either an API token or OAuth2 credentials configured in n8n for authentication.
- The node uses internal helper functions to make HTTP requests to the Magnet Customer API endpoints.
Troubleshooting
Common issues:
- Authentication failures due to invalid or expired API tokens or OAuth2 credentials.
- Incorrect filter values leading to empty search results.
- Network connectivity issues preventing API calls.
Error messages:
- Errors returned from the API will be caught and can appear in the output if "Continue On Fail" is enabled.
- Typical error messages include authentication errors ("Unauthorized"), invalid parameters, or rate limiting.
Resolutions:
- Verify and update API credentials.
- Double-check filter and sort parameter values.
- Ensure network connectivity and API availability.