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, specifically allowing programmatic management of user access within an AB Tasty account under the "Public API" resource. The "Change User Access" operation enables modifying a user's access rights in an account.
Typical use cases include:
- Automating user permission updates in AB Tasty based on external workflows.
- Integrating AB Tasty user management into broader identity or access management systems.
- Dynamically adjusting user roles or access levels as part of deployment or audit processes.
For example, you might use this node to update a user's access level after they change teams or leave a project, ensuring their permissions in AB Tasty are kept up-to-date automatically.
Properties
| Name | Meaning |
|---|---|
| Account ID | Numeric identifier of the AB Tasty account where the user access will be changed. |
| User ID | Numeric identifier of the user whose access is being modified. Required for this operation. |
| Request Body | JSON object containing the details of the access changes to apply to the user. |
Output
The node outputs the JSON response returned by the AB Tasty API after attempting to change the user's access. This typically includes confirmation of the updated user access details or error information if the request failed.
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 AB Tasty's public API endpoints.
- Proper configuration of the AB Tasty API credentials in n8n is necessary before using this node.
Troubleshooting
- Missing Credentials: If the client ID or client secret is not set, the node throws an error indicating missing credentials.
- Required Parameters Missing: The node validates that
Account IDandUser IDare provided; otherwise, it throws errors specifying which parameter is missing. - API Authentication Failure: If the OAuth token cannot be retrieved, an error is thrown indicating failure to get the access token.
- API Errors: Any errors returned from the AB Tasty API are wrapped and presented with the message prefix "Error calling AB Tasty API".
- Invalid JSON in Request Body: The
Request Bodymust be valid JSON; invalid JSON will cause parsing errors.
To resolve these issues:
- Ensure all required input properties are filled.
- Verify AB Tasty API credentials are correctly configured.
- Confirm the JSON in the
Request Bodyis well-formed. - Check network connectivity and API endpoint availability.
Links and References
- AB Tasty Public API Documentation
- OAuth 2.0 Client Credentials Flow
- n8n HTTP Request Node Documentation (for understanding underlying HTTP calls)