AB Tasty

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 and personalization workflows.

Practical examples include:

• Automatically revoking access for users who no longer require it after project completion.
• Integrating with HR systems to synchronize user permissions based on employment status.
• Managing user roles and access rights as part of a larger automation pipeline.

Properties

Output

The node outputs the response from the AB Tasty API call in JSON format. The structure depends on the API response but generally includes confirmation of the access revocation or relevant status information.

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 authentication token obtained via OAuth2 client credentials flow using a Client ID and Client Secret.
• Needs valid credentials configured in n8n for accessing the AB Tasty API.
• Makes HTTP requests to the AB Tasty Public API endpoints.
• No additional external dependencies beyond standard Node.js modules and n8n helpers.

Troubleshooting

• Missing Credentials: If the Client ID or Client Secret is not provided or invalid, the node will throw an error indicating missing credentials.
• Required Parameters Missing: Errors will occur if either Account ID or User ID is not specified when performing the revoke operation.
• API Token Retrieval Failure: If the OAuth token cannot be retrieved, the node will fail with an appropriate error message.
• API Call Failures: Network issues, invalid IDs, or permission problems may cause the API call to fail. The node surfaces these errors with detailed messages including stack traces.
• Invalid JSON in Request Body: Although not typical for this operation, malformed JSON in request body parameters can cause errors.

To resolve these issues:

• Ensure all required input properties are set correctly.
• Verify that the API credentials are valid and have sufficient permissions.
• Check network connectivity and endpoint availability.
• Review error messages for specific details and adjust inputs accordingly.

Links and References

• AB Tasty Public API Documentation
• OAuth 2.0 Client Credentials Flow
• n8n HTTP Request Node Documentation (for understanding underlying request mechanics)