Aigency icon

Aigency

Interact with Aigency API
Join our community

Actions35

Overview

The "Delete All Memories" operation in the Aigency node allows users to remove all stored memory data associated with a specific user ID from the Aigency API. This can be useful in scenarios where you want to clear a user's entire memory history, for example, to reset their profile or start fresh without any previous context.

Practical examples:

  • Resetting a chatbot's memory for a particular user to avoid outdated or irrelevant responses.
  • Clearing all stored memories before onboarding a new user session.
  • Managing user data privacy by deleting all memory records upon user request.

Properties

Name Meaning
User ID The unique numeric identifier of the user whose memories will be deleted.

Output

The output is a JSON object containing the result of the delete operation returned by the Aigency API. Typically, this will confirm whether the deletion was successful or provide an error message if it failed.

Example output structure:

{
  "result": {
    // API-specific response details confirming deletion
  }
}

If an error occurs, the output JSON will contain an error field describing the issue.

Dependencies

  • Requires an API key credential and API URL for authenticating requests to the Aigency API.
  • These credentials must be configured either in the n8n credentials manager or set as environment variables (AIGENCY_API_KEY and AIGENCY_API_URL).
  • The node uses HTTP POST requests with JSON-RPC 2.0 format to communicate with the Aigency API.

Troubleshooting

  • Missing Credentials: If the API key or URL is not provided, the node will throw an error instructing to configure credentials or environment variables.
  • API Errors: If the API returns an error (e.g., invalid user ID, network issues), the node will either throw an error or continue on fail depending on the workflow settings.
  • Invalid User ID: Ensure the User ID is a valid number corresponding to an existing user in the Aigency system.
  • Network Issues: Verify that the API URL is reachable and the API key is valid.

Links and References

Discussion