Aixyte API

Complete API for managing personalized web experiences - Excites, Domains, Files, and AI features (Rate limited: 200 requests/min)

Actions18

Overview

This node integrates with the Aixyte API to manage personalized web experiences, specifically focusing on Excites (personalized content units), Domains, Files, and AI-powered features. The "File: Delete" operation allows users to remove a specific file associated with an Excite by providing the Excite's ID and the File's ID. This is useful for maintaining or updating the media assets linked to personalized experiences, such as removing outdated images or videos.

Practical example: If you have an Excite representing a marketing campaign and want to delete a promotional video that is no longer relevant, you can use this operation to remove that video file from the Excite.

Properties

Name Meaning
Excite ID UUID of the excite that owns the files. Required to identify which Excite the file belongs to.
File ID UUID of the file to operate on. Required to specify which file to delete from the Excite.

Output

The output JSON contains the response from the Aixyte API after attempting to delete the specified file. Typically, it includes a confirmation message indicating successful deletion, e.g.:

{
  "message": "file deleted successfully"
}

No binary data is output by this operation.

Dependencies

  • Requires an API key credential for authenticating requests to the Aixyte API.
  • The node communicates with the Aixyte API endpoint hosted at https://azxjgkopxmhwzvkxouuy.supabase.co/functions/v1/api.
  • Proper configuration of the API key credential in n8n is necessary.

Troubleshooting

  • Rate Limiting: The API enforces a rate limit of 200 requests per minute. If exceeded, the node will throw an error stating:
    "Rate limit exceeded (200 requests/min). Please wait and try again later."
    To resolve, reduce request frequency or add delays between executions.
  • Invalid IDs: Providing incorrect or non-existent Excite ID or File ID may result in errors or failure to delete. Verify UUIDs are correct.
  • Authentication Errors: Missing or invalid API key credentials will cause authentication failures. Ensure the API key is correctly set up.
  • Network Issues: Connectivity problems can cause request failures. Check network access to the Aixyte API endpoint.

If the node is configured to continue on fail, errors will be returned in the output JSON under an error field instead of stopping execution.

Links and References

Discussion