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, specifically enabling users to send custom queries to the Data Explorer API. It allows retrieval of detailed visitor-level data collected by AB Tasty for advanced analysis and reporting. This is particularly useful for marketers, analysts, or developers who want to perform custom data queries beyond standard reports.
A common scenario includes querying visitor behavior or experiment results programmatically to feed into external analytics tools or dashboards. For example, a user might send a query to extract conversion rates segmented by visitor attributes or test variations.
Properties
| Name | Meaning |
|---|---|
| Account ID | The numeric identifier of the AB Tasty account to query data from. |
| Query Flagship | Boolean flag indicating whether to add a special header (x-source: flagship) in the request. |
| Request Body | JSON object representing the query payload sent to the Data Explorer API endpoint. |
Output
The node outputs an array of JSON objects corresponding to the response from the AB Tasty Data Explorer API. Each item in the output array contains the parsed JSON result of the query. If the response is empty (HTTP 204), it returns an object with "Status Code": "204 No Content".
No binary data output is produced for this operation.
Dependencies
- Requires an API key credential with a Client ID and Client Secret for AB Tasty.
- Uses OAuth2 client credentials flow to obtain an access token before making API requests.
- Makes HTTP POST requests to
https://api-data-explorer.abtasty.com/v2/clients/{accountId}/query. - The node expects valid JSON in the "Request Body" property to form the query.
Troubleshooting
- Missing Credentials: If the Client ID or Client Secret is not provided, the node will throw an error "Missing Client ID or Client Secret."
- Access Token Failure: If the OAuth token cannot be retrieved, the error "Failed to retrieve access token." will occur.
- Required Parameters Missing: The node validates that the Account ID is provided; otherwise, it throws "Account ID is required."
- Invalid JSON in Request Body: The request body must be valid JSON; otherwise, the API call may fail.
- API Errors: Any errors returned by the AB Tasty API are wrapped and reported as "Error calling AB Tasty API" with details.
- Empty Response: A 204 No Content response is handled gracefully but indicates no data was returned.
Links and References
- AB Tasty Data Explorer API Documentation
- AB Tasty OAuth2 Authentication
- n8n HTTP Request Node Documentation (for understanding underlying request mechanics)