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 various operations on different resources. Specifically, for the Custom Field Type resource with the Search operation, it allows users to search for custom field types defined in their Magnet Customer account. This is useful when you want to dynamically retrieve and filter custom field types based on a search term or other criteria.
Common scenarios include:
- Dynamically populating dropdowns or UI elements with available custom field types.
- Searching for specific custom field types by name or other attributes to use in further automation steps.
- Filtering custom field types to manage or update them programmatically.
Example: You want to find all custom field types that match a certain keyword to update their configuration or link them to other data entities.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authentication to use: "API Token" or "OAuth2". |
| Page | The page number of results to return (pagination). |
| Limit | Maximum number of results to return per request (minimum 1). |
| Search Term | The text string to search for within custom field types. |
| Filters | Collection of boolean filters to refine the search results: |
| - Emails Empty: Filter where emails are empty. | |
| - Phones Empty: Filter where phones are empty. | |
| - Interactions Empty: Filter where interactions are empty. | |
| Sort | Collection defining sorting options: |
| - Sort By: Field to sort the results by (default "name"). | |
| - Sort Type: Direction of sorting, either "Ascending" or "Descending". |
Note: Some hidden properties related to "Life Cycle" and "Source" exist but are not relevant for this resource-operation combination.
Output
The output is a JSON array where each item represents a custom field type matching the search criteria. Each JSON object contains the details of a custom field type as returned by the Magnet Customer API, typically including fields like:
_id: Unique identifier of the custom field type.name: Name of the custom field type.fieldType: The type/category of the custom field.- Other metadata fields describing the custom field type.
No binary data output is involved in this operation.
Dependencies
- Requires an active connection to the Magnet Customer API.
- Supports two authentication methods: API Token or OAuth2.
- Requires proper credentials configured in n8n for authentication.
- Pagination and filtering depend on the API's support for these features.
Troubleshooting
- Empty Results: If no custom field types are returned, verify the search term and filters. Also, check if the API user has permission to access custom field types.
- Authentication Errors: Ensure the API token or OAuth2 credentials are valid and have sufficient permissions.
- Rate Limits: The Magnet Customer API may enforce rate limits; handle errors accordingly or reduce request frequency.
- Invalid Parameters: Passing invalid values for pagination or filters may cause errors; ensure numeric values for page and limit, and boolean for filters.
- Network Issues: Connectivity problems can cause request failures; verify network access to the Magnet Customer API endpoint.
Links and References
- Magnet Customer API Documentation (Assumed URL, replace with actual if known)
- n8n Documentation on Creating Custom Nodes
- OAuth2 and API Token Authentication best practices in n8n
This summary is based solely on static analysis of the provided source code and property definitions.