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 Public API to list events configured within a specific test in an AB Tasty account. It is useful for retrieving detailed information about the events set up for experimentation or campaign tracking purposes.
Typical use cases include:
- Fetching all events associated with a particular A/B test to analyze user interactions.
- Automating reporting workflows by extracting event data programmatically.
- Integrating event data into other systems for further processing or visualization.
For example, a marketer might use this node to pull all events from a running test to monitor engagement metrics or trigger downstream automation based on event configurations.
Properties
| Name | Meaning |
|---|---|
| Account ID | The numeric identifier of the AB Tasty account where the test resides. This is required to specify the scope of the request. |
| Test ID | The numeric identifier of the specific test whose events you want to list. This is mandatory to target the correct test. |
| Filters | Optional collection of filters to refine the results when listing events or other entities. Includes options such as: - Active (Pause or Play) - Exclude Tag - Folder ID - Is Preprod (boolean) - Is Schedule (Test scheduled or not) - Max Per Page (limit items per page) - Modification Type - Name or URL search - Ordering by ID or Name - Pagination (Page number) - Parent ID - Search by name/URL/ID - Tag filtering - Test Type (e.g., ab, heatmap, mobileapp, etc.) |
Output
The node outputs a JSON array where each item corresponds to an event retrieved from the specified test. The structure of each event object depends on the AB Tasty API response but typically includes details such as event identifiers, names, types, and configuration metadata.
If the API returns no content, the node outputs a status message indicating "204 No Content".
No binary data output is produced by this operation.
Dependencies
- Requires an API key credential with client ID and client secret to authenticate against the AB Tasty OAuth2 token endpoint.
- The node performs OAuth2 client credentials flow to obtain an access token before making API requests.
- Network connectivity to
https://api.abtasty.comand related AB Tasty endpoints is necessary. - Proper permissions on the AB Tasty account to read test events are required.
Troubleshooting
- Missing Account ID or Test ID: The node will throw errors if these required parameters are not provided. Ensure both are set correctly.
- Authentication Failures: If the client ID or client secret are missing or invalid, the node will fail to retrieve an access token. Verify credentials are configured properly.
- API Rate Limits or Permissions: If the API returns errors related to rate limiting or insufficient permissions, check your AB Tasty account settings and API usage policies.
- Empty or Unexpected Responses: If the node returns "204 No Content" or unexpected data, verify that the test ID is correct and that events exist for that test.
- Filter Misconfiguration: Incorrect filter values may result in no data returned. Double-check filter options and their expected formats.