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 list all modifications of a specific variation within an A/B test. It is useful for users who want to retrieve detailed information about the changes applied in different variations of their experiments, such as UI tweaks or feature toggles.
Typical scenarios include:
- Auditing or reporting on all modifications associated with a particular variation.
- Automating workflows that depend on modification data, e.g., syncing with other tools or triggering downstream processes.
- Monitoring and managing experiment configurations at scale.
For example, a marketer or product manager could use this node to fetch all modifications for a given variation to verify what changes are live before launching a campaign.
Properties
| Name | Meaning |
|---|---|
| Account ID | The numeric identifier of the AB Tasty account. Required to specify which account's data to access. |
| Test ID | The numeric identifier of the test (experiment) from which to list modifications. |
| Variation ID | The numeric identifier of the variation within the test whose modifications you want to list. |
| Filters | A collection of optional filters to refine the query results when listing modifications. Includes options like Active status (Pause/Play), Exclude Tag, Folder ID, Preprod flag, Schedule status, Max items per page, Modification Type, Name, Search terms, Ordering, Pagination, Parent ID, Tag, and Test Type. |
Note: For the "List Modifications" operation specifically, only Account ID, Test ID, and Variation ID are strictly required. Filters are generally used in other operations but are part of the node's properties.
Output
The output is a JSON array where each item represents a modification object retrieved from the AB Tasty API. Each modification contains details about a single change applied in the specified variation, such as its type, name, operation, and other 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 for AB Tasty with client ID and client secret to authenticate via OAuth2 client credentials flow.
- The node makes HTTP requests to AB Tasty's Public API endpoints.
- Network connectivity to
https://api.abtasty.comis necessary. - Proper permissions on the AB Tasty account to access test and variation data.
Troubleshooting
- Missing Required Parameters: Errors will occur if
Account ID,Test ID, orVariation IDare not provided. Ensure these are set correctly. - Authentication Failures: If the client ID or client secret are missing or invalid, the node will fail to obtain an access token. Verify credentials.
- API Rate Limits or Permissions: The AB Tasty API may return errors if the account lacks permission or exceeds rate limits.
- Empty Results: If no modifications exist for the specified variation, the node returns a "204 No Content" status.
- Malformed Filters: Incorrect filter values may cause unexpected results or API errors. Use valid filter options as documented.
Links and References
- AB Tasty Public API Documentation
- OAuth 2.0 Client Credentials Flow
- AB Tasty Modifications API Endpoint
This summary focuses on the "Public API" resource and the "List Modifications" operation as requested.