AB Tasty

Overview

This node integrates with the AB Tasty platform, specifically enabling interaction with its Universal Data Connector API to upload custom audience segments. The "Upload Segments" operation allows users to send CSV files containing segment data directly to AB Tasty for real-time personalization and targeted experimentation based on their own data sources.

Typical use cases include:

• Marketers or data analysts uploading customer segmentation data from external systems into AB Tasty to tailor experiments or campaigns.
• Automating the process of updating audience segments in AB Tasty by regularly uploading CSV files with new or updated segment information.
• Integrating third-party data tools with AB Tasty to enhance visitor targeting capabilities.

For example, a user might upload a CSV file listing email addresses or user IDs tagged with specific behavioral attributes, which AB Tasty then uses to personalize website content or run A/B tests on those segments.

Properties

Output

The node outputs an array of JSON objects representing the response from the AB Tasty API after attempting to upload the segments. The structure depends on the API response but typically includes confirmation details or error messages.

• If the response is JSON, it is parsed and returned as JSON objects.
• If the response is plain text, it is returned as a text field.
• If there is no content (HTTP 204), the output indicates "Status Code": "204 No Content".

No binary data output is produced by this operation.

Dependencies

• Requires an API key credential with client ID and client secret for AB Tasty authentication.
• Uses OAuth 2.0 client credentials flow to obtain an access token before making API requests.
• Reads the CSV file from the local filesystem using Node.js fs module; thus, the CSV file must be accessible to the n8n runtime environment.
• Makes HTTP POST requests to the AB Tasty Universal Data Connector API endpoint for segment uploads.

Troubleshooting

• Missing Credentials: The node throws an error if the client ID or client secret is missing. Ensure these are configured correctly in the node credentials.
• File Access Issues: If the CSV file path is incorrect or inaccessible, the node will fail reading the file. Verify the file path and permissions.
• API Errors: Errors returned by the AB Tasty API (e.g., invalid account ID, partner name, or malformed CSV) will be surfaced as node errors with descriptive messages.
• Invalid Parameters: The node requires Account ID and Partner Name to be provided; missing these will cause immediate errors.
• Token Retrieval Failure: If the OAuth token cannot be retrieved, the node will throw an error indicating failure to get the access token.

Links and References

• AB Tasty Universal Data Connector API Documentation
• AB Tasty OAuth 2.0 Authentication Guide
• n8n HTTP Request Helper Documentation