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 platform's Public API to perform various management and data retrieval operations related to experiments, campaigns, users, scripts, and tests within an AB Tasty account. Specifically, the "Clear AB Tasty Script" operation deletes the AB Tasty script associated with a given account, which can be useful for resetting or removing tracking scripts from your website.
Common scenarios where this node is beneficial include:
- Automating the management of AB Tasty experiments and user access.
- Programmatically clearing or updating AB Tasty scripts on websites.
- Retrieving detailed information about tests, variations, modifications, and third-party tool links.
- Managing user permissions within an AB Tasty account.
Practical example:
- You want to clear the AB Tasty tracking script from your website programmatically as part of a deployment pipeline or troubleshooting process. Using this node with the "Clear AB Tasty Script" operation allows you to do so by specifying the relevant Account ID.
Properties
| Name | Meaning |
|---|---|
| Account ID | The numeric identifier of the AB Tasty account where the script will be cleared. |
Output
The node outputs the JSON response returned by 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 status message indicating "204 No Content".
No binary data output is produced by this operation.
Dependencies
- Requires an API key credential with client ID and client secret to authenticate with the AB Tasty OAuth2 token endpoint.
- Makes HTTP requests to AB Tasty's REST API endpoints.
- Requires network access to
https://api.abtasty.comand related subdomains. - The node expects the user to provide a valid Account ID for the targeted AB Tasty account.
Troubleshooting
- Missing Client ID or Client Secret: The node throws an error if authentication credentials are not provided or incomplete. Ensure that the API key credential includes both client ID and client secret.
- Missing Account ID: The operation requires the Account ID property; omitting it results in an error.
- Failed to retrieve access token: Indicates issues with OAuth2 authentication, possibly due to invalid credentials or network problems.
- API errors: Any HTTP or API-level errors are wrapped and reported with messages prefixed by "Error calling AB Tasty API". Check the error details for specific causes such as invalid parameters or permission issues.
- Empty or unexpected responses: If the API returns empty strings or non-JSON responses, the node attempts to handle them gracefully but verify API availability and correctness of input parameters.