AB Tasty

Overview

This node integrates with the AB Tasty platform's Public API to programmatically retrieve and manage data related to experiments, campaigns, and account configurations. Specifically, the "Get Variation" operation fetches detailed information about a particular variation within an AB Tasty test.

Use cases include:

• Automating retrieval of variation details for reporting or analysis.
• Integrating AB Tasty experiment variations into other marketing or analytics workflows.
• Monitoring specific variations programmatically to trigger downstream actions based on variation data.

For example, you might use this node to get the configuration and status of a variation in an A/B test to dynamically adjust your website content or to feed variation data into a dashboard.

Properties

Output

The output is a JSON object representing the detailed data of the requested variation. This typically includes all metadata and configuration details of the variation as returned by the AB Tasty Public API endpoint for variations.

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

The node does not output binary data for this operation.

Dependencies

• Requires an API key credential (client ID and client secret) for authenticating with the AB Tasty OAuth2 token endpoint.
• The node performs an OAuth2 client credentials flow to obtain an access token before making API requests.
• Network access to https://api.abtasty.com is required.
• Proper configuration of the AB Tasty API credentials in n8n is necessary.

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.
• Access Token Retrieval Failure: If the OAuth token cannot be obtained, the error "Failed to retrieve access token." will occur. Verify that the credentials are valid and the AB Tasty API is reachable.
• Required Parameters Missing: The node validates presence of Account ID, Test ID, and Variation ID for this operation. Omitting any will cause errors like "Account ID is required", "Test ID is required", or "Variation ID is required".
• API Errors: Any HTTP or API errors from AB Tasty will be wrapped and reported with the prefix "Error calling AB Tasty API". Check the error message and stack trace for details.
• Invalid JSON Response: If the API response is a string but not valid JSON, the node attempts to return it as plain text.

Links and References

• AB Tasty Public API Documentation
• OAuth 2.0 Client Credentials Flow
• n8n Documentation - Creating Custom Nodes