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 manage and control A/B tests programmatically. Specifically, the "Play Test" operation allows users to start or resume a paused test by sending a play command to the AB Tasty API for a given test ID within an account.
Common scenarios where this node is beneficial include:
- Automating the lifecycle of A/B tests as part of a CI/CD pipeline.
- Resuming paused experiments based on external triggers or conditions.
- Integrating AB Tasty test management into broader marketing or analytics workflows.
For example, after updating test configurations or variations, you can use this node to automatically play the test without manual intervention in the AB Tasty dashboard.
Properties
| Name | Meaning |
|---|---|
| Account ID | Numeric identifier of the AB Tasty account under which the test exists. |
| Test ID | Numeric identifier of the specific test to be played (resumed). |
| Request Body | JSON object for additional request data; used in some operations but not required here. |
Output
The node outputs the JSON response returned by the AB Tasty API after attempting to play the specified test. The structure depends on the API response but typically includes status information about the test state.
If the API returns no content (HTTP 204), the output will indicate "Status Code": "204 No Content".
No binary data output is produced by this operation.
Dependencies
- Requires an API key credential with client ID and client secret for AB Tasty authentication.
- The node obtains an OAuth2 access token from AB Tasty before making API calls.
- Network access to
https://api.abtasty.comis necessary. - Proper configuration of the AB Tasty API credentials in n8n is mandatory.
Troubleshooting
- Missing Client ID or Client Secret: The node throws an error if these credentials are not set or invalid. Ensure your AB Tasty API credentials are correctly configured.
- Missing Account ID or Test ID: Both are required parameters. Errors will occur if either is missing.
- Failed to retrieve access token: Indicates issues with authentication; verify credentials and network connectivity.
- API call errors: Any HTTP or API errors are wrapped and reported with messages like "Error calling AB Tasty API". Check the error message and stack trace for details.
- Invalid JSON in Request Body: If provided, ensure the JSON is well-formed.