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 retrieve and manage data related to experiments, campaigns, and account configurations. Specifically, the "Get Modification" operation fetches detailed information about a single modification within a variation of an A/B test.
Use cases include:
- Retrieving precise details about a specific modification applied in an experiment variation.
- Automating reporting or auditing workflows that require modification-level data.
- Integrating AB Tasty experiment modifications into broader marketing or analytics pipelines.
For example, you might use this node to get the configuration of a particular modification to verify its settings or to feed modification data into a dashboard.
Properties
| Name | Meaning |
|---|---|
| Account ID | The unique identifier of the AB Tasty account under which the test and modification exist. |
| Test ID | The identifier of the specific A/B test containing the modification. |
| Variation ID | The identifier of the variation within the test where the modification is applied. |
| Modification ID | The unique identifier of the modification to retrieve. |
Output
The node outputs a JSON object representing the requested modification's details as returned by the AB Tasty Public API. This typically includes all relevant properties of the modification such as its type, target elements, changes applied, and metadata.
If the API response is empty (HTTP 204), the output will indicate "204 No Content".
No binary data output is produced by this operation.
Dependencies
- Requires an API authentication token obtained via OAuth2 client credentials flow using a Client ID and Client Secret.
- Needs proper n8n credential setup for the AB Tasty API with these credentials.
- Makes HTTPS requests to AB Tasty's Public API endpoints.
- No additional external dependencies beyond standard Node.js modules and n8n helpers.
Troubleshooting
- Missing Required Parameters: The node throws errors if any of the required IDs (Account ID, Test ID, Variation ID, Modification ID) are not provided. Ensure all are set correctly.
- Authentication Failures: Errors occur if the Client ID or Client Secret are missing or invalid, or if the access token cannot be retrieved. Verify credentials and permissions.
- API Request Errors: Network issues or incorrect parameter values can cause API call failures. Check error messages for HTTP status codes and messages.
- Parsing Errors: If the API returns unexpected data formats, JSON parsing may fail. Review API responses and ensure compatibility.