Actions23
- Data Explorer API Actions
- Public API Actions
- Change User Access
- Clear AB Tasty Script
- Get Framework Checksum
- Get Modification
- Get Test
- Get Third Party Tools Link
- Get User
- Get Variation
- Give User Access
- List Events
- List Modifications
- List Tests
- List Tests Statistics
- List Third Party Tool Links
- List Users
- List Variations
- Pause Test
- Play Test
- Revoke User Access
- Update AB Tasty Script
- Universal Data Connector API Actions
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 retrieves all variations associated with a given test within an AB Tasty account.
Use cases include:
- Fetching all variations of a specific A/B test to analyze or report on them.
- Automating workflows that require synchronization or processing of test variations.
- Integrating AB Tasty experiment data into other systems for enhanced personalization or analytics.
For example, a marketing team could use this node to automatically pull variation details from their AB Tasty tests and feed them into a dashboard or CRM system.
Properties
| Name | Meaning |
|---|---|
| Account ID | The unique numeric identifier of the AB Tasty account where the test resides. |
| Test ID | The unique numeric identifier of the test whose variations you want to list. |
Output
The node outputs a JSON array where each item represents a variation of the specified test. Each variation object contains detailed information as returned by the AB Tasty Public API, such as variation ID, name, status, and other metadata relevant to the variation.
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 to authenticate requests to the AB Tasty API.
- Makes HTTP requests to the AB Tasty Public API endpoints.
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 Token Retrieval Failure: If the OAuth token cannot be retrieved, the node will fail with an appropriate error message.
- HTTP Errors: Any issues communicating with the AB Tasty API (e.g., network errors, invalid parameters) will result in an error containing the API response message.
To resolve these issues:
- Ensure that the API credentials are correctly set up in n8n.
- Verify that the Account ID and Test ID inputs are correctly provided.
- Check network connectivity and API endpoint availability.