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 access and manage data related to experiments, campaigns, tests, variations, modifications, users, and third-party tool links. Specifically, the "List Third Party Tool Links" operation retrieves all third-party tool links associated with a particular test in an AB Tasty account.
Common scenarios for this node include:
- Automating retrieval of third-party integrations linked to specific A/B tests.
- Auditing or reporting on external tools connected to your experiments.
- Integrating AB Tasty test data with other marketing or analytics platforms by fetching relevant third-party tool URLs.
For example, a user might want to list all third-party tool links for a given test ID to verify which external tools are currently integrated with that test.
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 for which to list third-party tool links. |
Output
The node outputs a JSON array where each item represents a third-party tool link associated with the specified test. Each item contains details about a single third-party tool link as returned by the AB Tasty Public API.
If the API response is empty (no content), the node returns an object indicating "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 API authentication.
- The node performs OAuth 2.0 client credentials flow to obtain an access token before making API requests.
- Network access to
https://api.abtasty.comis required. - No additional environment variables or n8n configurations beyond the API credential setup are needed.
Troubleshooting
- Missing Client ID or Client Secret: The node will throw an error if these credentials are not provided. Ensure the API credential is correctly configured.
- Missing Required Parameters: If either Account ID or Test ID is missing, the node throws an error specifying which parameter is required.
- Failed to Retrieve Access Token: This indicates issues with the provided credentials or network connectivity. Verify credentials and internet access.
- API Errors: Any errors returned from the AB Tasty API are wrapped and reported with the message prefix "Error calling AB Tasty API". Check the error message and stack trace for details.
- Empty Response: If no third-party tool links exist for the test, the node returns a 204 No Content status indication.
Links and References
- AB Tasty Public API Documentation (general reference for API endpoints)
- OAuth 2.0 Client Credentials Flow: https://oauth.net/2/grant-types/client-credentials/