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 retrieve and manage data related to experiments, campaigns, and account configurations. Specifically, the "Get Third Party Tools Link" operation fetches a third-party tool link associated with a particular test in an AB Tasty account.
Use cases include:
- Automating retrieval of third-party tool links for tests to integrate with external analytics or marketing tools.
- Managing and auditing third-party integrations linked to specific A/B tests.
- Building dashboards or reports that consolidate test metadata including external tool references.
Example: You have an A/B test running in AB Tasty and want to automatically fetch the URL or configuration of a linked third-party tool (e.g., a heatmap or personalization service) for further processing or display.
Properties
| Name | Meaning |
|---|---|
| Account ID | Numeric identifier of the AB Tasty account where the test resides. |
| Test ID | Numeric identifier of the specific test from which to get the third-party tool link. |
| Third Party Tool Link ID | Numeric identifier of the third-party tool link to retrieve for the specified test. |
Output
The node outputs JSON data representing the details of the requested third-party tool link. This typically includes information such as the link's URL, configuration parameters, and metadata related to the integration with the AB Tasty test.
If the API returns no content, the output will indicate a "204 No Content" status.
No binary data output is produced by this operation.
Dependencies
- Requires an API key credential for AB Tasty with client ID and client secret to authenticate via OAuth2 client credentials flow.
- The node makes HTTP requests to the AB Tasty Public API endpoints.
- Proper configuration of the AB Tasty API credentials in n8n is necessary.
Troubleshooting
- Missing Required Parameters: Errors occur if Account ID, Test ID, or Third Party Tool Link ID are not provided. Ensure all required IDs are set.
- Authentication Failures: If the client ID or secret is missing or invalid, the node will fail to obtain an access token. Verify credentials.
- API Errors: Network issues or incorrect IDs may cause API errors. Check error messages for details.
- Empty Responses: A "204 No Content" response means no data was found; verify the IDs correspond to existing resources.
Links and References
- AB Tasty Public API Documentation (general reference for API endpoints)
- OAuth2 Client Credentials Flow (for understanding authentication)