AB Tasty icon

AB Tasty

Use the AB Tasty API

Actions23

Overview

This node integrates with the AB Tasty platform's Public API to programmatically access and manage data related to experiments, campaigns, tests, variations, modifications, users, and third-party tool links within an AB Tasty account. It is useful for automating workflows that involve retrieving detailed information about specific tests or managing test states without manual intervention in the AB Tasty dashboard.

A practical example is using this node to fetch detailed information about a particular A/B test by its Test ID, enabling further analysis or reporting in an automated pipeline. Another use case includes listing all tests under an account with specific filters applied, such as only active tests or those belonging to a certain folder.

Properties

Name Meaning
Account ID Numeric identifier of the AB Tasty account. Required for most operations to specify which account's data to access.
Test ID Numeric identifier of a specific test within the account. Used to retrieve or manipulate data related to a particular test.
Filters Collection of optional filters to refine list queries. Includes options such as:
- Active (Pause or Play)
- Exclude Tag
- Folder ID
- Is Preprod (boolean)
- Is Schedule (Test scheduled or not)
- Max Per Page
- Modification Type
- Name
- Name or URL
- Operation
- Order by ID or Name (Ascending/Descending)
- Page number
- Parent ID
- Search by name/URL/ID
- Tag
- Test Type (e.g., ab, heatmap, mobileapp, etc.)

Output

The node outputs JSON data corresponding to the response from the AB Tasty Public API endpoints. The structure varies depending on the operation but generally includes detailed information about tests, variations, modifications, users, or other requested resources.

  • For the Get Test operation, the output JSON contains detailed properties of the specified test, such as its configuration, status, variations, and metadata.
  • If the API returns no content, the node outputs a JSON object indicating "Status Code": "204 No Content".
  • The node does not output binary data for this resource-operation combination.

Dependencies

  • Requires an API key credential consisting of a Client ID and Client Secret to authenticate with the AB Tasty OAuth2 token endpoint.
  • The node internally obtains an OAuth2 access token before making API requests.
  • Network access to https://api.abtasty.com and related AB Tasty API endpoints is required.
  • No additional external dependencies beyond standard HTTP request capabilities provided by n8n.

Troubleshooting

  • Missing Credentials: If the Client ID or Client Secret is not set or invalid, the node will throw an error stating "Missing Client ID or Client Secret." Ensure credentials are correctly configured.
  • Required Parameters Missing: Many operations require mandatory parameters like Account ID, Test ID, Variation ID, etc. The node throws explicit errors if these are missing, e.g., "Account ID is required" or "Test ID is required." Verify all required inputs are provided.
  • Access Token Retrieval Failure: If the OAuth2 token cannot be retrieved, the node throws "Failed to retrieve access token." Check network connectivity and validity of credentials.
  • API Errors: Any API call failure results in an error message prefixed with "Error calling AB Tasty API:" followed by the original error message. Review the error details and ensure the API endpoint and parameters are correct.
  • Filter Parameter Encoding: Filters are URL-encoded; incorrect filter names or values may cause unexpected API responses. Use the exact filter names and types as defined.

Links and References

Discussion