AB Tasty

Overview

This node integrates with the AB Tasty Public API to retrieve detailed information about variations within A/B tests. Specifically, the "Get Variation" operation fetches data for a single variation of a specified test in an AB Tasty account. This is useful for users who want to programmatically access variation details such as configuration, status, or performance metrics directly from AB Tasty without manual intervention.

Common scenarios include:

• Automating reporting workflows by fetching variation details for analysis.
• Integrating AB Tasty variation data into dashboards or other marketing tools.
• Validating or auditing test configurations programmatically.

Example: Retrieve the details of variation ID 10 for test ID 123 in account 4567 to check its setup or status.

Properties

Output

The output is a JSON object representing the detailed data of the requested variation. This typically includes all properties returned by the AB Tasty API for a variation, such as its name, status, modifications, traffic allocation, and other metadata relevant to that variation.

If the API returns no content, the node outputs a status code message indicating "204 No Content".

The node does not output binary data.

Dependencies

• Requires an API key credential (Client ID and Client Secret) for authenticating with the AB Tasty OAuth2 token endpoint.
• Makes HTTP requests to the AB Tasty Public API endpoints.
• Uses n8n's built-in HTTP request helper methods.
• No additional external dependencies beyond standard Node.js modules and n8n environment.

Troubleshooting

• Missing Credentials: If the Client ID or Client Secret are not provided, the node will throw an error "Missing Client ID or Client Secret." Ensure these credentials are configured correctly in n8n.
• Required Parameters Missing: The node validates required parameters like Account ID, Test ID, and Variation ID. Omitting any of these will cause errors specifying which parameter is missing.
• Failed Token Retrieval: If the OAuth token cannot be obtained, the node throws "Failed to retrieve access token." Check API credentials and network connectivity.
• API Errors: Any errors returned by the AB Tasty API will be wrapped and reported with the prefix "Error calling AB Tasty API:" followed by the original message. Review the error message and stack trace for debugging.
• Invalid JSON Response: If the API response is a string but not valid JSON, the node attempts to return it as plain text. Unexpected formats may require checking API changes or response content.

Links and References

• AB Tasty Public API Documentation
• OAuth 2.0 Authentication
• n8n HTTP Request Node Documentation