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 retrieve detailed information about modifications within experiments (tests) run on the AB Tasty platform. Specifically, the "Get Modification" operation fetches data about a single modification applied to a variation of a test.
Use cases include:
- Retrieving details of a specific modification for audit or reporting purposes.
- Automating workflows that require fetching modification metadata to trigger further actions.
- Integrating AB Tasty experiment data into external dashboards or analytics tools.
For example, you might use this node to get the configuration of a particular modification in an A/B test variation to verify its settings or to synchronize it with another system.
Properties
| Name | Meaning |
|---|---|
| Account ID | The numeric identifier of the AB Tasty account under which the test and modification exist. |
| Test ID | The numeric identifier of the test (experiment) containing the modification. |
| Variation ID | The numeric identifier of the variation within the test where the modification is applied. |
| Modification ID | The numeric identifier of the specific modification to retrieve. |
These properties are required to uniquely identify the modification resource in the AB Tasty system.
Output
The node outputs a JSON object representing the requested modification's details as returned by the AB Tasty Public API. This typically includes fields describing the modification's type, configuration, status, and any other metadata provided by AB Tasty.
If the API returns no content, the node outputs a JSON object indicating a "204 No Content" status.
The node does not output binary data for this operation.
Dependencies
- Requires an API key credential for AB Tasty with client ID and client secret to authenticate via OAuth2 client credentials flow.
- Makes HTTP requests to the AB Tasty Public API endpoints.
- Requires network access to
https://api.abtasty.com.
Troubleshooting
- Missing Required Parameters: The node throws errors if any of the required IDs (Account ID, Test ID, Variation ID, Modification ID) are missing. Ensure all these inputs are provided.
- Authentication Errors: If the client ID or client secret are missing or invalid, the node will fail to obtain an access token. Verify your API credentials.
- API Request Failures: Network issues or incorrect parameters can cause API call failures. Check the error message for details.
- Unexpected Response Format: If the API response is not valid JSON, the node attempts to return raw text; ensure the API is functioning correctly.