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 Public API to programmatically access and manage user data within an AB Tasty account. Specifically, the "Get User" operation retrieves detailed information about a specific user associated with a given account. This is useful for scenarios where you need to automate user management tasks, audit user permissions, or synchronize user data between AB Tasty and other systems.
Practical examples include:
- Fetching user details to verify access rights before performing further operations.
- Automating reporting on users in an AB Tasty account.
- Integrating AB Tasty user data into CRM or identity management platforms.
Properties
| Name | Meaning |
|---|---|
| Account ID | The numeric identifier of the AB Tasty account from which to retrieve the user. |
| User ID | The numeric identifier of the user within the specified account whose details are fetched. |
Output
The node outputs a JSON object representing the user data retrieved from the AB Tasty Public API. The structure typically includes user attributes such as user ID, name, email, roles, and access permissions related to the specified account.
If the API response is empty (HTTP 204 No Content), the output will indicate this status accordingly.
No binary data output is involved in this operation.
Dependencies
- Requires an API key credential with client ID and client secret for AB Tasty API authentication.
- The node performs OAuth2 client credentials flow to obtain an access token before making API requests.
- Network access to
https://api.abtasty.comis required.
Troubleshooting
- Missing Client ID or Client Secret: The node throws an error if these credentials are not provided. Ensure that valid API credentials are configured.
- Missing Required Parameters: Errors occur if either Account ID or User ID is not supplied. Verify that these inputs are correctly set.
- Failed to Retrieve Access Token: If the OAuth token request fails, check network connectivity and validity of client credentials.
- API Request Errors: Any HTTP errors returned by the AB Tasty API will be surfaced with descriptive messages. Review the error message and stack trace for debugging.
- Invalid JSON Response: If the API returns malformed JSON, the node attempts to handle it gracefully but may output raw text instead.