Autocust - Contact Operation icon

Autocust - Contact Operation

Handle Autocust operations on contacts

Actions5

Overview

The "Get Many Contacts" operation in this node allows users to retrieve multiple contact records from the Autocust system. It supports filtering contacts either by their membership in specific lists or by segments, enabling targeted data retrieval. This operation is useful for scenarios such as exporting contacts belonging to certain marketing lists, analyzing segmented customer groups, or syncing subsets of contacts with other systems.

Practical examples include:

  • Fetching all contacts subscribed to a particular newsletter list.
  • Retrieving contacts filtered by demographic or behavioral segments.
  • Paginating through contacts when processing large datasets.

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 available lists or specify IDs via expressions.
Segment Name (Shown if filtering by Segment) Select a segment to filter contacts by. You can choose from available segments or specify an ID via expressions. 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 (Shown if not getting all contacts) Maximum number of contacts to return, between 1 and 50.
Skip (Shown if not getting all contacts) Number of contacts to skip, used for pagination.
Filters (Shown if filtering by List) One or more filters to apply on contact attributes. Each filter includes:
- Attribute Name or ID: The contact attribute to filter on.
- Operator: Comparison operator (e.g., equals, contains).
- Value: The value to compare against.

Output

The output consists of JSON objects representing the retrieved contacts. Each object contains the contact's attributes and metadata as returned by the Autocust API. The structure typically includes identifiers, contact details, list/segment memberships, and any custom attributes.

This operation does not output binary data.

Dependencies

  • Requires an API key credential for authenticating with the Autocust service.
  • Uses Autocust API endpoints to fetch lists, segments, and contacts.
  • The node relies on dynamic loading methods to populate options for lists, segments, and filterable attributes.

Troubleshooting

  • Common Issues:

    • Providing invalid list or segment IDs may result in empty results or errors.
    • Exceeding the maximum limit (50) will be rejected; ensure limits are within allowed range.
    • Pagination parameters (limit and skip) must be non-negative integers; invalid values may cause errors.
    • If no contacts match the filters, the output will be empty.

  • Error Messages:

    • "The operation 'getManyContacts' is not known!": Indicates the operation parameter was set incorrectly.
    • API authentication errors suggest missing or invalid API credentials.
    • Errors related to loading options (lists, segments, attributes) may indicate connectivity issues or permission problems.

Links and References

Discussion