Actions35
- Add Message
- Add Subscription
- Call Capability
- Delete All Memories
- Delete All Messages
- Delete All Warnings
- Delete Last Messages
- Delete Memory
- Delete Message
- Disable Capability
- Disable Dev Mode
- Disable Subscription
- Enable Capability
- Enable Dev Mode
- Enable Subscription
- Get Balance
- Get Capabilities
- Get Current User
- Get Dev Mode
- Get File URL
- Get Memories
- Get Messages
- Get Next Scan
- Get Reward Amount
- Get Subscriptions
- Get Usage History
- Get Warnings
- Login
- Logout
- Remove Capability
- Remove Subscription
- Scan Subscriptions
- Send Message
- Sync Capabilities
- Throw Error
Overview
The node provides integration with the Aigency API, allowing users to perform various operations related to user messages, memories, subscriptions, capabilities, and more. Specifically, the Delete Memory operation deletes a particular memory entry associated with a user.
This node is useful in scenarios where you want to programmatically manage user data stored in Aigency, such as cleaning up specific memories or messages, managing subscriptions, or interacting with capabilities. For example, you might use the Delete Memory operation to remove outdated or incorrect memory entries for a user in an automated workflow.
Properties
| Name | Meaning |
|---|---|
| User ID | The numeric identifier of the user whose memory you want to delete. |
| ID | The string identifier of the specific memory entry to delete. |
Output
The output JSON contains the result of the API call for each input item processed. On success, it returns the result field from the Aigency API response, which typically confirms the deletion or provides relevant details about the deleted memory.
If an error occurs during the operation, the output JSON will contain an error field describing the issue.
The node does not output binary data.
Dependencies
- Requires an API key credential and API URL for authenticating requests to the Aigency API.
- These credentials can be set either via environment variables (
AIGENCY_API_KEYandAIGENCY_API_URL) or configured directly in the n8n credentials interface. - The node uses HTTP POST requests with JSON-RPC 2.0 format to communicate with the Aigency API.
Troubleshooting
- Missing Credentials: If neither environment variables nor configured credentials are found, the node throws an error indicating that credentials are empty. Ensure you have set the required API key and URL.
- API Errors: If the API returns an error (e.g., invalid user ID or memory ID), the node will either throw an error or continue on fail depending on your workflow settings. Check the error message for details.
- Network Issues: Connection failures or unreachable API endpoints will cause errors. Verify network connectivity and API endpoint correctness.
- Invalid Parameters: Providing incorrect or missing parameters like
userIdoridwill result in API errors. Double-check that all required fields are correctly set.
Links and References
- Aigency API Documentation (Assumed link; replace with actual if available)
- n8n Documentation - Creating Nodes
- JSON-RPC 2.0 Specification