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 API, enabling users to programmatically manage and retrieve data related to experiments, campaigns, user access, and account configurations on the AB Tasty platform. Specifically, the "Change User Access" operation under the "Public API" resource allows modifying a user's access permissions within an AB Tasty account.
Common scenarios for this node include:
- Automating user permission updates in AB Tasty accounts.
- Integrating AB Tasty user management into broader workflows or admin dashboards.
- Managing access control dynamically based on external triggers or events.
For example, you could use this node to revoke or grant access to specific users automatically when their role changes in your organization, ensuring that only authorized personnel can modify or view AB Tasty experiments.
Properties
| Name | Meaning |
|---|---|
| Account ID | The numeric identifier of the AB Tasty account where the user access will be changed. |
| User ID | The numeric identifier of the user whose access is to be changed (required for this operation). |
| Request Body | A JSON object containing the details of the access change to apply to the user. |
Output
The node outputs the response from the AB Tasty API as JSON. This typically includes confirmation of the access change or details about the updated user access. 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 AB Tasty's REST API endpoints.
- For some operations (not specifically "Change User Access"), it may require reading CSV files from the filesystem, but this is not applicable here.
Troubleshooting
- Missing Credentials: If the client ID or client secret is missing, the node throws an error indicating these are required.
- Required Parameters Missing: Errors occur if mandatory parameters like Account ID or User ID are not provided.
- Failed Token Retrieval: If the OAuth token cannot be obtained, the node will fail with an authentication error.
- API Errors: Any errors returned by the AB Tasty API are wrapped and reported with the message "Error calling AB Tasty API" along with the original error message and stack trace.
- Invalid JSON in Request Body: Ensure the JSON provided in the Request Body property is valid; otherwise, parsing errors may occur.
Links and References
- AB Tasty API Documentation (general reference for API endpoints and usage)
- OAuth2 Client Credentials Flow (for understanding authentication mechanism)