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 control and manage A/B tests and related resources within an account. Specifically, the "Play Test" operation allows users to start or resume a paused test by sending a request to the AB Tasty API to change the test status to "play."
Common scenarios for this node include:
- Automating the activation of A/B tests as part of a deployment or release pipeline.
- Resuming paused experiments based on external triggers or schedules.
- Integrating AB Tasty test management into broader marketing or analytics workflows.
For example, a marketer could use this node to automatically start a specific test after updating its configuration elsewhere, ensuring seamless experiment lifecycle management without manual intervention.
Properties
| Name | Meaning |
|---|---|
| Account ID | The numeric identifier of the AB Tasty account where the test resides. |
| Test ID | The numeric identifier of the specific test to be played (started/resumed). |
| Request Body | JSON object for additional request data if needed (optional; typically empty for play). |
Output
The node outputs the JSON response returned by the AB Tasty API after attempting to play the specified test. This response typically contains details about the test's updated status or confirmation of the action.
If the API returns no content (HTTP 204), the output will indicate "Status Code": "204 No Content".
No binary data is produced by this operation.
Dependencies
- Requires valid AB Tasty API credentials: a client ID and client secret must be configured in n8n credentials.
- The node obtains an OAuth2 access token from AB Tasty before making API calls.
- Network access to
https://api.abtasty.comis required.
Troubleshooting
- Missing Credentials: If the client ID or client secret is not set, the node throws an error "Missing Client ID or Client Secret."
- Missing Required Parameters: The node validates that both Account ID and Test ID are provided; otherwise, it throws errors like "Account ID is required" or "Test ID is required."
- Failed Token Retrieval: If the OAuth token cannot be obtained, the node throws "Failed to retrieve access token."
- API Errors: Any HTTP or API errors during the request result in a detailed error message prefixed with "Error calling AB Tasty API," including the original error message and stack trace.
- Invalid JSON in Request Body: If the request body JSON is malformed, the node may fail parsing it before sending.
To resolve these issues:
- Ensure all required parameters are correctly set.
- Verify that the AB Tasty API credentials are valid and have necessary permissions.
- Check network connectivity to AB Tasty endpoints.
- Validate JSON syntax in the Request Body property if used.
Links and References
- AB Tasty API Documentation (general reference for API endpoints)
- OAuth2 Authentication: The node uses client credentials grant to obtain access tokens from AB Tasty.