Overview
The node performs operations related to managing contacts in the Autocust system. Specifically, for the Get Many Contacts operation, it retrieves multiple contact records based on filtering criteria such as lists or segments. This is useful when you want to bulk fetch contacts for marketing campaigns, data analysis, or synchronization with other systems.
Typical use cases include:
- Fetching all contacts belonging to specific mailing lists.
- Retrieving contacts filtered by a particular segment.
- Applying additional attribute-based filters to narrow down the contact selection.
- Controlling the number of contacts returned or fetching all available contacts.
For example, you might use this node to get all contacts subscribed to a "Newsletter" list or all contacts in a "VIP Customers" segment, optionally filtering those contacts by attributes like location or subscription date.
Properties
| Name | Meaning |
|---|---|
| Filter By | Choose whether to filter contacts by List or by Segment. |
| Lists Names | (Shown if filtering by List) Select one or more lists to filter contacts by. You can choose from existing lists or specify IDs via expressions. |
| Segment Name | (Shown if filtering by Segment) Select a segment to filter contacts by. You can choose from existing segments or specify an ID via expression. This field is required when filtering by segment. |
| Get All Contacts | Boolean flag indicating whether to return all matching contacts without applying a limit. |
| Limit | Maximum number of contacts to return when not fetching all. Value must be between 1 and 100. |
| Filters | (Shown if filtering by List) Additional attribute-based filters to apply to contacts. Each filter consists of: - Attribute Name or ID (selectable or via expression) - Operator (e.g., equals, contains) - Value |
Output
The node outputs JSON data containing the retrieved contacts. Each item in the output corresponds to a contact record with its associated attributes and metadata as provided by the Autocust API.
If binary data were involved (not indicated here), it would typically represent attachments or files related to contacts, but this operation focuses on JSON contact data only.
Dependencies
- Requires an API key credential for authenticating with the Autocust service.
- The node depends on Autocust's API endpoints for contacts, lists, and segments.
- It uses internal methods to load options dynamically for lists, segments, and filterable attributes.
Troubleshooting
- No contacts returned: Verify that the selected list or segment actually contains contacts. Also, check that any applied filters are correct and match existing attribute values.
- Invalid filter attribute or operator: Ensure that the attribute names/IDs and operators used in filters are valid and supported by the Autocust API.
- Limit exceeded error: The limit property accepts values between 1 and 100. Setting a value outside this range may cause errors.
- Authentication errors: Confirm that the API key credential is correctly configured and has sufficient permissions.
- Empty segment or list selection: When filtering by segment, the segment name is required; leaving it empty will cause an error.
Links and References
- n8n Expressions Documentation
- Autocust API documentation (not publicly linked here; refer to your Autocust account resources)
- n8n documentation on creating custom nodes