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 specific account. It allows you to programmatically retrieve user data, which can be useful for managing user access, auditing, or synchronizing user information with other systems.

Common scenarios where this node is beneficial include:

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

For example, you might use this node to get a list of active users in your AB Tasty account who belong to a particular folder or have specific tags, then export that data for compliance checks or integration with your CRM.

Properties

Name Meaning
Account ID The numeric identifier of the AB Tasty account from which to list users. This is required to specify the scope of the user list.
Filters A collection of optional filters to refine the user list results. Available filter options include:
- Active: Filter users by their active status (Pause = 0, Play = 1). Default is Play (1).
- Exclude Tag: Exclude users with a specific tag.
- Folder: Search users by folder ID (0 means no folder).
- Is Preprod: Boolean flag to return only pre-production tests/users. Default is true.
- Is Schedule: Filter by schedule status (Test Not Schedule = 0, Test Schedule = 1). Default is Test Schedule (1).
- Max Per Page: Limit the number of items returned per page. Default is 10.
- Modification Type: Filter by type of global modification (plugin or actionTracking).
- Name: Search by name of the test/user.
- Name or URL: Search by name and URL.
- Operation: Search by operation of the modification.
- Order by ID: Order results by ID ascending or descending. Default is Ascending.
- Order by Name: Order results by name ascending or descending. Default is Ascending.
- Page: Specify the page number of the collection to retrieve. Default is 10.
- Parent: Search by parent ID (0 means no parent).
- Search: General search by name, URL, or ID.
- Tag: Filter users with a specific tag.
- Test Type: Filter by test types such as ab, heatmap, mobileapp, mastersegment, multipage, multivariate, mvt, predictive, segmentation, subsegment, tunnel.

Output

The node outputs an array of JSON objects representing the users retrieved from the AB Tasty Public API. Each object corresponds to a user and contains fields as returned by the API, typically including user details such as user ID, name, email, status, tags, and other metadata.

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

The node does not output binary data for 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 Public API endpoints.
  • Proper configuration of the AB Tasty API credentials in n8n is necessary.
  • Network access to https://api.abtasty.com is required.

Troubleshooting

  • Missing Client ID or Client Secret: The node will throw an error if the API credentials are not set or incomplete. Ensure that both client ID and client secret are configured correctly in n8n credentials.
  • Account ID Required: For listing users, the Account ID must be provided. Omitting it will cause an error.
  • API Rate Limits or Access Denied: If the API returns errors related to rate limiting or permission issues, verify that the API key has sufficient permissions and that usage limits are not exceeded.
  • Invalid Filter Values: Providing incorrect filter values (e.g., non-numeric where numbers are expected) may cause the API to reject the request.
  • Empty Results: If no users match the filters, the node will return a "204 No Content" status. Adjust filters or check account data accordingly.

Links and References

Discussion