AB Tasty icon

AB Tasty

Use the AB Tasty API

Overview

This node integrates with the AB Tasty platform's Public API to list users associated with a specified account. It allows retrieving detailed user information programmatically, which is useful for managing user access, auditing user lists, or synchronizing user data with other systems.

Common scenarios include:

  • Fetching all users of an AB Tasty account to audit permissions.
  • Filtering users based on specific criteria such as active status or tags.
  • Paginating through large user lists for batch processing or reporting.

For example, a marketing team might use this node to extract all active users tagged with a particular role to ensure proper access control or to generate reports on user activity.

Properties

Name Meaning
Account ID The numeric identifier of the AB Tasty account from which to list users.
Query Parameters A collection of optional filters and pagination controls to refine the user list. Options include:
- Filter Active: Pause (0) or Play (1) status.
- Filter Exclude Tag: Exclude users with specific tags.
- Filter Folder: Search by folder ID.
- Filter Is Preprod: Boolean to filter pre-production users.
- Filter Is Schedule: Test schedule status (0 or 1).
- Filter Name: Search by user name.
- Filter Name or URL: Search by name or URL.
- Filter Order ID/Name: Sort results ascending or descending.
- Filter Parent: Search by parent ID.
- Filter Search: General search by name/URL/ID.
- Filter Tag: Include only users with specific tags.
- Filter Type: Search by test type.
- Max Per Page: Limit number of items per page.
- Page: Page number to retrieve.

Output

The node outputs an array of JSON objects representing users retrieved from the AB Tasty Public API. Each object corresponds to a user record containing user details as provided by the API response.

If the API returns no content, the output will indicate a "204 No Content" status.

No binary data output is involved in 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 services or environment variables are required beyond the API credentials.

Troubleshooting

  • Missing Credentials: If the Client ID or Client Secret is not set, the node will throw an error indicating missing credentials. Ensure these are correctly configured.
  • Required Parameters Missing: The node requires the Account ID parameter; omitting it will cause an error. Make sure to provide all mandatory parameters.
  • API Access Errors: Errors returned from the AB Tasty API (e.g., invalid token, permission denied) will be surfaced with descriptive messages. Verify API credentials and account permissions.
  • Empty Responses: If the API returns no users, the node outputs a "204 No Content" status. Confirm that query parameters and account ID are correct.
  • Invalid Query Parameters: Using unsupported or malformed query parameters may result in API errors. Use only supported filters as defined in the properties.

Links and References

Discussion