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 Events" operation retrieves all events set up within a specified test in an AB Tasty account.
Common scenarios for this node include:
- Fetching event definitions associated with a particular A/B test to analyze or report on user interactions.
- Automating workflows that require synchronization of test event data with other systems.
- Monitoring and auditing events configured in tests for quality assurance.
For example, a marketing analyst might use this node to list all conversion or engagement events tied to a specific experiment to evaluate its performance.
Properties
| Name | Meaning |
|---|---|
| Account ID | The unique numeric identifier of the AB Tasty account from which to retrieve events. |
| Test ID | The unique numeric identifier of the test whose events are to be listed. |
Output
The node outputs a JSON array where each item represents an event configured in the specified test. The structure corresponds directly to the AB Tasty API response for global modifications (events) of a test, typically including details such as event IDs, names, types, and configuration parameters.
If the API returns no content, the output will indicate a "204 No Content" status.
No binary data is produced by this operation.
Dependencies
- Requires valid AB Tasty API credentials: a client ID and client secret to obtain an OAuth2 access token.
- The node makes HTTP requests to the AB Tasty Public API endpoints.
- No additional environment variables are needed beyond the API credentials configured in n8n.
Troubleshooting
- Missing Credentials: If the client ID or client secret is not provided, the node throws an error indicating missing credentials.
- Required Parameters Missing: The node requires both Account ID and Test ID for this operation. Omitting either results in an error specifying the missing parameter.
- Failed Token Retrieval: If the OAuth2 token request fails or returns no access token, the node reports failure to retrieve the access token.
- API Errors: Any errors returned by the AB Tasty API are caught and rethrown with descriptive messages. Check the API response and ensure the account and test IDs are correct and accessible.
- Empty Responses: A "204 No Content" status indicates no events found; verify that the test has events configured.
Links and References
- AB Tasty Public API Documentation (general reference for API endpoints)
- OAuth2 Authentication: The node uses client credentials grant to authenticate with AB Tasty API.
This summary focuses exclusively on the "Public API" resource and the "List Events" operation as requested.