AB Tasty

Overview

This node integrates with the AB Tasty platform's Public API to programmatically access and manage data related to experiments, campaigns, and account configurations. Specifically, the "List Variations" operation under the "Public API" resource retrieves all variations associated with a given test in an AB Tasty account.

Use cases include:

• Automating retrieval of experiment variations for reporting or analysis.
• Integrating AB Tasty variation data into other marketing or analytics workflows.
• Monitoring and managing A/B test variations programmatically.

For example, you might use this node to fetch all variations of a specific A/B test to analyze their performance or to synchronize variation details with another system.

Properties

Output

The node outputs a JSON array where each item represents a variation of the specified test. The structure corresponds directly to the AB Tasty API response for listing variations, typically including fields such as variation IDs, names, status, and other metadata describing each variation.

No binary data output is produced by this operation.

Dependencies

• Requires an API key credential (Client ID and Client Secret) for authenticating with the AB Tasty API.
• The node performs OAuth2 client credentials flow to obtain an access token before making API requests.
• Network access to https://api.abtasty.com and related AB Tasty endpoints is necessary.

Troubleshooting

• Missing Credentials: If the Client ID or Client Secret is not provided, the node will throw an error indicating missing credentials.
• Required Parameters Missing: The node requires both Account ID and Test ID for this operation. Omitting either will cause an error.
• API Access Token Failure: If the OAuth token request fails, the node will report failure to retrieve the access token.
• HTTP Errors: Any HTTP errors from the AB Tasty API are wrapped and reported with the message "Error calling AB Tasty API" along with the original error message.
• Invalid JSON Response: If the API returns a non-JSON string, the node attempts to parse it; if parsing fails, it returns the raw text.

To resolve issues:

• Ensure valid and complete API credentials are configured.
• Provide all required input parameters.
• Verify network connectivity to AB Tasty API endpoints.
• Check that the AB Tasty account and test IDs are correct and accessible.

Links and References

• AB Tasty API Documentation
• OAuth 2.0 Client Credentials Flow