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
This node integrates with the Aigency API, allowing users to perform various operations related to user messages, subscriptions, capabilities, and account management. The "Login" operation specifically facilitates authenticating or initiating a session for a user by their User ID.
Common scenarios where this node is beneficial include:
- Automating interactions with the Aigency platform such as sending messages, managing subscriptions, or querying user data.
- Integrating Aigency's AI-driven capabilities into workflows for customer support, content generation, or user engagement.
- Managing user sessions and authentication programmatically within n8n workflows.
For example, using the "Login" operation, a workflow can authenticate a user by their User ID before performing further actions like sending messages or retrieving user-specific data.
Properties
| Name | Meaning |
|---|---|
| User ID | The numeric identifier of the user to log in. Required for the Login operation. |
Output
The node outputs JSON data under the json field containing the result of the API call. For the "Login" operation, the output will typically include details about the login status or session information returned by the Aigency API.
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 the Aigency service. These can be configured either via n8n credentials or environment variables (
AIGENCY_API_KEYandAIGENCY_API_URL). - The node makes HTTP POST requests to the Aigency API endpoint using JSON-RPC 2.0 protocol.
- No additional external dependencies are required beyond network access to the Aigency API.
Troubleshooting
- Missing Credentials: If neither credentials nor environment variables are set, the node throws an error indicating missing credentials. Ensure that the API key and URL are properly configured.
- API Errors: If the API returns an error response, it will be included in the output JSON under the
errorfield. Common causes include invalid User ID, incorrect API key, or network issues. - Continue on Fail: If enabled, the node will continue processing subsequent items even if one fails, returning error details in the output JSON instead of stopping execution.
- Invalid User ID: Since User ID is required and must be a number, providing an invalid or missing value will cause errors.
Links and References
- Aigency API Documentation (Replace with actual URL if available)
- n8n Documentation - Creating Custom Nodes
- JSON-RPC 2.0 Specification