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 perform various management and data retrieval operations related to experiments, campaigns, user access, scripts, and account configurations. Specifically, the "Clear AB Tasty Script" operation allows users to programmatically delete the AB Tasty script associated with a given account.
Common scenarios for this node include:
- Automating the management of AB Tasty experiments and tests.
- Managing user access rights within an AB Tasty account.
- Clearing or updating the AB Tasty script on a website as part of deployment or maintenance workflows.
- Retrieving detailed information about tests, variations, modifications, and third-party tool links.
Practical example:
- A marketing team wants to clear the AB Tasty script from their website before deploying a new version. Using this node with the "Clear AB Tasty Script" operation and specifying the Account ID, they can automate this step in their CI/CD pipeline.
Properties
| Name | Meaning |
|---|---|
| Account ID | The numeric identifier of the AB Tasty account where the script will be cleared. |
Output
The node outputs JSON data representing the response from the AB Tasty API after performing the requested operation. For the "Clear AB Tasty Script" operation, the output typically confirms the success or failure of the script deletion request. If the API returns no content (HTTP 204), the node outputs a JSON object indicating "Status Code": "204 No Content".
No binary data is produced by this operation.
Dependencies
- Requires an API key credential with client ID and client secret for authenticating with the AB Tasty OAuth2 token endpoint.
- Makes HTTP requests to the AB Tasty API endpoints.
- For some operations (not specifically "Clear AB Tasty Script"), may require reading CSV files from the filesystem.
- Requires n8n credentials configured with valid AB Tasty API authentication details.
Troubleshooting
- Missing Client ID or Client Secret: The node throws an error if these credentials are not provided. Ensure that the API key credential is correctly set up.
- Missing Account ID: This property is mandatory for the "Clear AB Tasty Script" operation. The node will throw an error if it is not specified.
- Failed to retrieve access token: Indicates issues with authentication; verify that the client ID and secret are correct and have proper permissions.
- API errors: Any error returned by the AB Tasty API will be wrapped and reported by the node. Check the error message and stack trace for details.
- Network issues: Connectivity problems to the AB Tasty API endpoints can cause failures; ensure network access and proxy settings if applicable.