AB Tasty

Overview

This node integrates with the AB Tasty platform's Public API to programmatically access detailed information about tests, experiments, campaigns, and account configurations. It is useful for automating retrieval and management of A/B testing data within workflows, enabling users to fetch test details, list modifications, manage user access, and more.

A practical example is retrieving detailed information about a specific test by providing the Account ID and Test ID, which can then be used for reporting or triggering further automation based on test status or results.

Properties

Note: The "Test ID" property is required for operations related to specific tests such as "Get Test", "List Events", "Pause Test", etc.

Output

The node outputs JSON data representing the response from the AB Tasty Public API for the requested operation. For the "Get Test" operation, the output JSON contains detailed information about the specified test, including its configuration, status, variations, and other metadata.

If the API returns no content (HTTP 204), the node outputs an object indicating "Status Code": "204 No Content".

Binary data output is not supported by this node.

Dependencies

• Requires an API authentication token obtained via OAuth2 client credentials flow using a Client ID and Client Secret.
• Needs an API key credential configured in n8n to authenticate requests to the AB Tasty API.
• Makes HTTP requests to various AB Tasty API endpoints depending on the selected operation.
• For some operations (e.g., uploading segments), it reads CSV files from the local filesystem.

Troubleshooting

• Missing Credentials: If the Client ID or Client Secret is missing, the node will throw an error "Missing Client ID or Client Secret." Ensure these are correctly set in the node credentials.
• Required Parameters Missing: Operations require certain parameters like Account ID, Test ID, Variation ID, etc. If any required parameter is missing, the node throws an error specifying which parameter is missing.
• Failed to Retrieve Access Token: If the OAuth2 token request fails, the node throws "Failed to retrieve access token." Verify that the Client ID and Client Secret are valid and have proper permissions.
• API Errors: Any errors returned by the AB Tasty API are wrapped and thrown as NodeApiError with the message prefixed by "Error calling AB Tasty API:" followed by the original error message.
• File Read Errors: For operations requiring CSV upload, ensure the file path is correct and accessible; otherwise, file read errors may occur.

Links and References

• AB Tasty Public API Documentation
• OAuth 2.0 Client Credentials Flow
• AB Tasty API Authentication Guide