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 programmatically access and manage data related to experiments, campaigns, and account configurations. Specifically, the "List Modifications" operation retrieves all modifications associated with a particular variation of an A/B test.
Use cases include:
- Fetching detailed modification data for a specific variation in an experiment to analyze changes applied.
- Automating reporting or synchronization of experiment modifications with other systems.
- Monitoring and auditing modifications applied within variations for quality control.
Example: You have an A/B test running with multiple variations, and you want to list all modifications made in one variation to understand what changes are being tested.
Properties
| Name | Meaning |
|---|---|
| Account ID | The unique identifier of the AB Tasty account where the test and variation exist. |
| Test ID | The unique identifier of the test (experiment) containing the variation. |
| Variation ID | The unique identifier of the variation within the test whose modifications will be listed. |
Output
The output is a JSON array where each item represents a modification object retrieved from the AB Tasty API for the specified variation. Each modification typically includes details such as modification type, target elements, values changed, and other metadata describing the change.
No binary data is output by this operation.
Dependencies
- Requires an API authentication token obtained via OAuth2 client credentials flow using a Client ID and Client Secret.
- Needs valid AB Tasty API credentials configured in n8n.
- Makes HTTP requests to the AB Tasty Public API endpoints.
Troubleshooting
- Missing Required Parameters: Errors occur if Account ID, Test ID, or Variation ID are not provided. Ensure these are set correctly.
- Authentication Failures: If the node cannot retrieve an access token, verify that the Client ID and Client Secret credentials are correct and have necessary permissions.
- API Errors: Network issues or invalid parameters may cause API errors. Check error messages for details.
- Empty Responses: If no modifications exist for the given variation, the output may be empty or indicate "204 No Content".