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 "Give User Access" operation allows you to grant access permissions to a user within an AB Tasty account. This is useful in scenarios where you want to automate user management tasks such as onboarding new team members or adjusting access rights without manually using the AB Tasty web interface.

Practical examples include:

• Automatically granting access to new users when they are added to your organization's system.
• Integrating AB Tasty user access control into broader workflows for managing marketing or product teams.
• Automating access provisioning based on external triggers or events.

Properties

The Request Body property expects a JSON structure that defines the specifics of the access being granted (e.g., user roles, permissions). The exact schema depends on AB Tasty's API requirements for this endpoint.

Output

The node outputs the response from the AB Tasty API call in the json field. This typically contains confirmation details about the user access granted or any relevant metadata returned by the API.

If the API returns no content (HTTP 204), the output will contain a status message indicating "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 OAuth token endpoint and then to the Public API endpoints.
• Proper configuration of the AB Tasty API credentials in n8n is necessary.
• Network access to https://api.abtasty.com and related subdomains must be allowed.

Troubleshooting

• Missing Client ID or Client Secret: The node throws an error if these credentials are not set or invalid. Ensure the API credentials are correctly configured in n8n.
• Failed to retrieve access token: Indicates authentication failure; verify that the client ID and secret are correct and have proper permissions.
• Required parameters missing: For example, if Account ID is not provided, the node will throw an error. Always provide all required inputs.
• API errors: If the AB Tasty API returns an error, it will be wrapped and shown with the message "Error calling AB Tasty API". Check the error details for causes like invalid request body or insufficient permissions.
• Invalid JSON in Request Body: Ensure the JSON input is well-formed and matches the expected schema for the user access grant.

Links and References

• AB Tasty Public API Documentation (general reference for API endpoints and payloads)
• OAuth 2.0 Client Credentials Flow
• n8n HTTP Request Node Documentation (for understanding how HTTP calls are made)

This summary focuses on the "Public API" resource and the "Give User Access" operation as requested.