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, allowing users to programmatically manage and retrieve data related to experiments, campaigns, user access, scripts, tests, variations, modifications, and other account configurations. It supports multiple API resources including the Public API, Data Explorer API, and Universal Data Connector API.
The "Update AB Tasty Script" operation under the "Public API" resource specifically enables updating or rebuilding the AB Tasty script associated with an account. This is useful when you want to refresh or modify the script that runs on your website for A/B testing purposes.
Common scenarios:
- Automatically triggering a rebuild of the AB Tasty script after changes in experiments or configurations.
- Managing user access rights or retrieving test and variation details programmatically.
- Querying detailed visitor-level data for custom analytics.
- Uploading custom audience segments for targeted experimentation.
Practical example:
- After modifying an experiment setup externally, use this node to update the AB Tasty script so that the latest changes are reflected on the website without manual intervention.
Properties
| Name | Meaning |
|---|---|
| Resource | The API resource to interact with: Data Explorer API, Public API, or Universal Data Connector API. |
| Operation | The specific action to perform within the selected resource. For Public API includes operations like Update AB Tasty Script, List Tests, Get User, etc. |
| Account ID | Numeric identifier of the AB Tasty account (required for most Public API operations). |
| Account Identifier | String identifier used for some Universal Data Connector API operations. |
| Test ID | Numeric identifier of a test (required for operations involving specific tests). |
| Variation ID | Numeric identifier of a variation within a test (required for some operations). |
| Modification ID | Numeric identifier of a modification (used in modification-related operations). |
| Third Party Tool Link ID | Numeric identifier for third party tool links (used in related operations). |
| User ID | Numeric identifier of a user (used in user access and user retrieval operations). |
| Partner Name | String name of the partner (used in segment upload operations). |
| Input Binary Field | Name of the binary input field containing CSV data (used in segment upload). |
| Query Flagship | Boolean flag to add a special header for querying Flagship (used in Data Explorer API query). |
| Visitor ID | String visitor identifier (used in visitor segment listing). |
| Filters | Collection of filters to refine list or search operations (e.g., active status, folder, tags). |
| Request Body | JSON object representing the request payload for applicable operations (e.g., user access changes, test play/pause). |
Output
The node outputs an array of JSON objects corresponding to the API responses for each input item processed. The structure of the JSON depends on the specific operation performed but generally reflects the data returned by the AB Tasty API endpoints, such as:
- Details about tests, variations, modifications, users, or events.
- Confirmation messages or status codes for actions like script updates or user access changes.
- Lists of entities filtered according to provided parameters.
If the response is empty (HTTP 204 No Content), the output will contain a JSON object indicating "Status Code": "204 No Content".
For operations uploading binary CSV data (e.g., segment uploads), the node sends the binary content but does not output binary data itself.
Dependencies
- Requires an API key credential with client ID and client secret for authenticating with the AB Tasty OAuth2 token endpoint.
- Needs internet access to call AB Tasty's REST API endpoints.
- The node uses standard HTTP methods (GET, POST, PATCH, DELETE) to interact with the API.
- No additional external libraries beyond n8n core helpers are required.
Troubleshooting
- Missing Credentials: If the client ID or client secret is missing, the node throws an error "Missing Client ID or Client Secret." Ensure these credentials are configured correctly.
- Required Parameters Missing: Many operations require mandatory parameters like Account ID, Test ID, Variation ID, or User ID. Omitting these results in errors specifying which parameter is missing.
- Failed Token Retrieval: If the OAuth token cannot be obtained, the node throws "Failed to retrieve access token." Check API credentials and network connectivity.
- API Errors: Any API call failure returns an error with the message prefixed by "Error calling AB Tasty API:" along with the original error message and stack trace.
- Invalid JSON in Request Body: For operations requiring a JSON request body, ensure the input is valid JSON to avoid parsing errors.
- Binary Data Handling: When uploading CSV data, ensure the binary input field exists and contains valid CSV content; otherwise, the upload will fail.