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 programmatically retrieve and manage data related to experiments, campaigns, and account configurations. Specifically, the "Get Framework Checksum" operation fetches a checksum value for the framework associated with a given account. This checksum can be used to verify the integrity or version of the framework deployed in an AB Tasty account.
Common scenarios where this node is beneficial include:
- Validating that the AB Tasty framework on a website matches the expected version.
- Automating monitoring or auditing workflows to detect changes in the framework.
- Integrating framework status checks into broader experimentation or deployment pipelines.
Example use case:
- A marketing team wants to ensure that the AB Tasty framework loaded on their site is up-to-date before launching new experiments. They use this node to fetch the current framework checksum and compare it against a known value.
Properties
| Name | Meaning |
|---|---|
| Account ID | The numeric identifier of the AB Tasty account for which the framework checksum is fetched. |
Output
The node outputs JSON data representing the response from the AB Tasty Public API endpoint for the framework checksum. The exact structure depends on the API but typically includes fields such as the checksum value and possibly metadata about the framework version or status.
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.
- Makes HTTP requests to the AB Tasty API endpoints.
- Requires network access to
https://api.abtasty.com.
Troubleshooting
- Missing Client ID or Client Secret: The node will throw an error if these credentials are not provided. Ensure the API key credential is configured correctly.
- Account ID Required: If the Account ID property is missing or invalid, the node will raise an error indicating it is required.
- Failed to Retrieve Access Token: Indicates issues with authentication; verify that the client ID and secret are valid and have proper permissions.
- API Request Errors: Any errors returned by the AB Tasty API (e.g., 4xx or 5xx HTTP responses) will be surfaced as node errors with messages prefixed by "Error calling AB Tasty API". Check the message and stack trace for details.
- Empty or Unexpected Response: If the API returns no content or unexpected data, verify the account ID and API availability.