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, including Excites (personalized content), Domains, Files, and AI-powered features. Specifically, the "Domain: Delete" operation allows users to permanently delete a domain configuration by specifying its unique identifier.

Common scenarios for this node include:

  • Automating the management of web personalization domains within workflows.
  • Removing obsolete or incorrect domain configurations programmatically.
  • Integrating domain lifecycle management into broader automation pipelines.

For example, a marketing team could use this node to automatically clean up domains that are no longer in use after a campaign ends.

Properties

Name Meaning
Domain ID UUID of the domain to operate on. This is required to identify which domain to delete.

Output

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

{
  "message": "domain deleted successfully"
}

No binary data is output by this operation.

Dependencies

  • Requires an API key credential for authenticating with the Aixyte API.
  • The node makes HTTP requests to the Aixyte API endpoint hosted at https://azxjgkopxmhwzvkxouuy.supabase.co/functions/v1/api.
  • Proper network access to the API endpoint is necessary.
  • Rate limiting applies: maximum 200 requests per minute.

Troubleshooting

  • Rate Limit Errors: If you receive a "Rate limit exceeded (200 requests/min)" error, reduce the frequency of requests or add delays between executions.
  • Invalid Domain ID: Providing an incorrect or non-existent domain UUID will likely result in an error from the API. Verify the domain ID before running the node.
  • Authentication Failures: Ensure the API key credential is valid and has appropriate permissions.
  • Network Issues: Connectivity problems to the API endpoint will cause request failures; check your network and firewall settings.

If the node is set to continue on failure, errors will be returned in the output JSON under an error field for easier handling in workflows.

Links and References

Discussion