AB Tasty icon

AB Tasty

Use the AB Tasty API

Overview

This node integrates with the AB Tasty platform, allowing users to programmatically manage and retrieve data related to experiments, campaigns, and account configurations. Specifically, the "Pause Test" operation under the "Public API" resource enables users to pause an active test within their AB Tasty account. This is useful in scenarios where a test needs to be temporarily halted without deleting it, such as when analyzing preliminary results or addressing issues before resuming.

Practical example: A marketing team running multiple A/B tests might want to pause a specific test if they detect unexpected behavior or external factors affecting the test's validity. Using this node, they can automate pausing the test directly from their workflow without manual intervention in the AB Tasty dashboard.

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 paused.

Output

The node outputs the JSON response returned by the AB Tasty API after attempting to pause the test. This typically includes confirmation details about the paused test or relevant status information. 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 for AB Tasty with client ID and client secret.
  • The node performs OAuth2 client credentials flow to obtain an access token from https://api.abtasty.com/oauth/v2/token.
  • The pause test request is sent as a PATCH HTTP request to the endpoint:
    https://api.abtasty.com/api/interface/accounts/{accountId}/tests/{testId}/pause
    
  • Proper configuration of the AB Tasty API credentials in n8n is necessary.

Troubleshooting

  • Missing Account ID or Test ID: The node throws errors if either the Account ID or Test ID is not provided. Ensure these are set correctly.
  • Authentication Errors: Failure to retrieve an access token indicates invalid or missing client credentials. Verify that the API key credential is properly configured.
  • API Request Failures: Network issues or incorrect permissions may cause the API call to fail. Check the error message for details and ensure the API user has rights to pause tests.
  • Unexpected Response Format: If the API returns a string that cannot be parsed as JSON, the node outputs the raw text. This might indicate an API issue or unexpected response.

Links and References

Discussion