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 manage user access and other account-related data programmatically. Specifically, the "Revoke User Access" operation allows you to remove a user's access rights from an AB Tasty account. This is useful in scenarios such as offboarding employees, managing permissions dynamically, or automating user access control within your experimentation platform.
Practical example: If you want to automate the removal of a user's access when they leave a project or company, this node can revoke their access by specifying the Account ID and User ID, ensuring security and compliance without manual intervention.
Properties
| Name | Meaning |
|---|---|
| Account ID | The numeric identifier of the AB Tasty account where the user access will be revoked. |
| User ID | The numeric identifier of the user whose access you want to revoke. |
Output
The node outputs the JSON response returned by the AB Tasty API after attempting to revoke user access. The structure typically contains confirmation of the action or details about the user membership status. 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 to authenticate via OAuth2 client credentials flow.
- The node makes HTTP requests to the AB Tasty API endpoints.
- Proper configuration of the AB Tasty API credentials in n8n is necessary before using this node.
Troubleshooting
- Missing Client ID or Client Secret: The node throws an error if these credentials are not set. Ensure your AB Tasty API credentials are correctly configured.
- Missing Required Parameters: Errors occur if Account ID or User ID are not provided. Double-check that these inputs are supplied.
- Failed to Retrieve Access Token: Indicates issues with authentication; verify your credentials and network connectivity.
- API Errors: Any errors returned by the AB Tasty API (e.g., invalid user ID, insufficient permissions) will be wrapped and reported by the node. Review the error message and stack trace for details.
- Empty or Unexpected Response: If the API returns an empty string or unexpected format, the node attempts to parse it but may return raw text or a 204 status indication.
Links and References
- AB Tasty Public API Documentation (general reference for API endpoints)
- OAuth2 Client Credentials Flow (for understanding authentication mechanism)
This summary focuses on the "Public API" resource and the "Revoke User Access" operation as requested.