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-formatted segment data directly to AB Tasty for real-time personalization and targeted experimentation based on their own data sources.

Typical use cases include:

• Uploading customer or visitor segments from external systems into AB Tasty to tailor experiments or campaigns.
• Integrating third-party audience data for enhanced targeting within AB Tasty.
• Automating segment updates as part of a broader marketing or data workflow.

For example, a marketer could export a list of high-value customers from their CRM as a CSV file and use this node to upload that segment to AB Tasty, enabling personalized A/B tests or feature rollouts for that group.

Properties

Note: The "Account ID" property is present but hidden when using the "Upload Segments" operation and thus not applicable here.

Output

The node outputs the response from the AB Tasty API after uploading the segments. The output JSON structure depends on the API's response but typically includes confirmation or status information about the upload.

If the API returns a string response, the node attempts to parse it as JSON; if parsing fails, it outputs the raw text. If no content is returned (HTTP 204), the node outputs an object indicating "204 No Content".

No binary output is produced by this operation.

Dependencies

• Requires an API key credential for AB Tasty with client ID and client secret to authenticate via OAuth2 and obtain an access token.
• The node makes HTTP requests to AB Tasty's OAuth token endpoint and the Universal Data Connector API endpoint.
• The CSV segment data must be provided as binary input in the specified input binary field.

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.
• Missing Required Parameters: For the upload operation, "Account Identifier" and "Partner Name" must be provided; otherwise, the node errors out.
• Invalid Binary Data: The input binary field must contain valid CSV data. If the binary data is missing or invalid, the upload will fail.
• API Errors: Any HTTP or API errors are caught and reported with the message "Error calling AB Tasty API" along with the original error message and stack trace.
• Parsing Response: If the API returns non-JSON text, the node outputs it as plain text. Unexpected response formats may require checking the API documentation or request payload.

Links and References

• AB Tasty Universal Data Connector API Documentation
• AB Tasty OAuth2 Authentication
• n8n Documentation on Binary Data Handling