Actions23
- Data Explorer API Actions
- Public API Actions
- Change User Access
- Clear AB Tasty Script
- Get Framework Checksum
- Get Modification
- Get Test
- Get Third Party Tools Link
- Get User
- Get Variation
- Give User Access
- List Events
- List Modifications
- List Tests
- List Tests Statistics
- List Third Party Tool Links
- List Users
- List Variations
- Pause Test
- Play Test
- Revoke User Access
- Update AB Tasty Script
- Universal Data Connector API Actions
Overview
This node integrates with the AB Tasty platform's Universal Data Connector API to list visitor segments associated with a specific visitor ID within an account. It is useful for retrieving real-time audience segment data that can be used for personalization, targeted marketing, or experimentation based on custom audience definitions.
Typical use cases include:
- Fetching all segments a particular visitor belongs to in order to tailor content dynamically.
- Integrating visitor segmentation data into workflows for analytics or customer journey orchestration.
- Enabling real-time decision-making by accessing up-to-date segment membership information.
For example, you might input an Account ID and Visitor ID to retrieve all segments assigned to that visitor, then use this data to trigger personalized campaigns or experiments.
Properties
| Name | Meaning |
|---|---|
| Account ID | The numeric identifier of your AB Tasty account where the visitor segments are stored. |
| Visitor ID | The unique string identifier of the visitor whose segments you want to list. |
Output
The node outputs a JSON array where each item corresponds to the response from the AB Tasty Universal Data Connector API listing visitor segments for the specified visitor. The structure depends on the API response but generally includes details about each segment the visitor belongs to.
If the API returns no content, the output will indicate a "204 No Content" status.
No binary data output is produced by this operation.
Dependencies
- Requires an API authentication token obtained via OAuth2 client credentials flow using a Client ID and Client Secret.
- Needs valid credentials configured in n8n for the AB Tasty API.
- Makes HTTP requests to
https://api-data-connector.abtasty.comendpoints. - No additional environment variables beyond the API credentials are required.
Troubleshooting
- Missing Credentials: If the Client ID or Client Secret is not provided, the node throws an error indicating missing credentials.
- Missing Required Parameters: The node requires both Account ID and Visitor ID for this operation; omitting either results in an error.
- Failed Token Retrieval: If the OAuth token cannot be retrieved, the node will throw an error indicating failure to get the access token.
- API Errors: Any errors returned by the AB Tasty API are wrapped and reported as node API errors with relevant messages and stack traces.
- Invalid Visitor ID or Account ID: Providing incorrect IDs may result in empty responses or API errors; verify these values before running the node.