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 API, enabling users to interact programmatically with various AB Tasty services. It supports querying visitor-level data, managing experiments and campaigns, and handling audience segments for personalization and experimentation.
Common scenarios include:
- Retrieving detailed visitor data for custom analysis.
- Managing A/B tests, variations, modifications, and user access within an AB Tasty account.
- Uploading or listing custom audience segments for real-time targeting.
- Controlling test states (play/pause) and managing third-party tool links.
Practical examples:
- Querying visitor data to analyze experiment performance beyond standard reports.
- Listing all active tests in an account to monitor ongoing experiments.
- Uploading a CSV file of customer segments to target specific audiences dynamically.
- Pausing or playing a test based on external triggers or schedules.
Properties
| Name | Meaning |
|---|---|
| Account ID | Numeric identifier of the AB Tasty account to operate on. |
| Resource | Selects the AB Tasty API resource to use: Data Explorer API, Public API, or Universal Data Connector API. |
| Operation | Specifies the action to perform within the selected resource. Available operations vary by resource. |
| Test ID | Identifier of a specific test (required for many test-related operations). |
| Variation ID | Identifier of a variation within a test (used in modification and variation operations). |
| Modification ID | Identifier of a specific modification (used in modification retrieval). |
| Third Party Tool Link ID | Identifier for third party tool links related to a test. |
| User ID | Identifier of a user for user access management operations. |
| Partner Name | Name of the partner when uploading segments via the Universal Data Connector API. |
| CSV File Path | File path to a CSV file containing segments to upload. |
| Query Flagship | Boolean flag to add a special header indicating a "flagship" query (specific to some API calls). |
| Visitor ID | Identifier of a visitor used when listing visitor segments. |
| Query Parameters | Collection of optional filters and pagination parameters for list operations (e.g., filtering tests by status, tags, folder, etc.). |
| Request Body | JSON object used as the request payload for POST, PATCH, or PUT operations. |
Output
The node outputs an array of JSON objects representing the response from the AB Tasty API for each input item processed. The structure depends on the specific API endpoint called but generally includes:
- Data about tests, variations, modifications, users, segments, or query results.
- For some operations, a simple status code message if no content is returned (e.g., "204 No Content").
- If the response is a string that can be parsed as JSON, it is converted accordingly; otherwise, raw text is returned.
Binary data output is not supported by this node.
Dependencies
- Requires an API authentication token obtained via OAuth2 client credentials flow using a Client ID and Client Secret.
- Needs valid credentials configured in n8n for accessing the AB Tasty API.
- For segment uploads, requires access to the local filesystem to read CSV files.
- Uses standard HTTP methods (GET, POST, PATCH, DELETE) to communicate with AB Tasty endpoints.
Troubleshooting
- Missing Credentials: Errors occur if Client ID or Client Secret are not provided or invalid. Ensure these are correctly set in the node credentials.
- Required Parameters Missing: Many operations require specific IDs (Account ID, Test ID, User ID, etc.). Omitting these will cause errors indicating which parameter is missing.
- Invalid File Path: For segment uploads, an incorrect CSV file path will cause file reading errors.
- API Access Issues: Failed token retrieval or unauthorized requests may indicate expired or incorrect credentials.
- Unexpected Response Format: If the API returns non-JSON responses, the node attempts to parse them; failure to parse will return raw text.
- Network Issues: Connectivity problems to AB Tasty endpoints will result in request failures.
To resolve errors:
- Verify all required parameters are provided.
- Check credential validity and permissions.
- Confirm file paths and formats for uploads.
- Review error messages for specific missing fields or authorization issues.