AB Tasty

Overview

This node integrates with the AB Tasty Public API to programmatically retrieve and manage data related to experiments, campaigns, and account configurations. Specifically, the "List Tests Statistics" operation fetches statistical data about tests within a specified account.

Use cases include:

• Monitoring performance metrics of A/B tests or experiments in AB Tasty.
• Automating reporting workflows by extracting test statistics regularly.
• Integrating AB Tasty test data into dashboards or other analytics tools.

For example, a marketing analyst could use this node to pull up-to-date statistics on all active tests in their account to evaluate experiment effectiveness without manually logging into the AB Tasty platform.

Properties

Output

The node outputs an array of JSON objects representing the statistics of tests associated with the specified account. The exact structure depends on the AB Tasty API response but typically includes aggregated metrics such as impressions, conversions, and other performance indicators for each test.

No binary data output is produced by this operation.

Dependencies

• Requires an API authentication token obtained via OAuth 2.0 client credentials flow using a Client ID and Client Secret.
• Needs valid credentials configured in n8n for accessing the AB Tasty API.
• Makes HTTP requests to the AB Tasty Public API endpoints.
• No additional external dependencies beyond standard Node.js modules and n8n helpers.

Troubleshooting

• Missing Credentials: If the Client ID or Client Secret is not provided or invalid, the node will throw an error indicating missing credentials.
• Access Token Retrieval Failure: Failure to obtain an access token from the OAuth endpoint will result in an error; verify that credentials are correct and the AB Tasty service is reachable.
• Required Parameters Missing: The node validates required parameters like Account ID and Test ID (if applicable). Omitting these will cause errors.
• API Errors: Any HTTP errors returned by the AB Tasty API will be wrapped and reported by the node. Check the error message and stack trace for details.
• Invalid JSON Response: If the API returns malformed JSON, the node attempts to handle it gracefully but may output raw text or an empty status.

To resolve issues:

• Ensure all required input properties are set correctly.
• Confirm that the API credentials are valid and have sufficient permissions.
• Check network connectivity to the AB Tasty API endpoints.
• Review error messages for specific guidance.

Links and References

• AB Tasty Public API Documentation
• OAuth 2.0 Client Credentials Flow
• n8n HTTP Request Helper Documentation