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 interacts with the Aigency API, allowing users to perform various operations related to user messages, subscriptions, capabilities, and other account-related actions. Specifically, the "Call Capability" operation enables invoking a particular capability of a user by sending text input to it.
This node is beneficial in scenarios where automation workflows need to interact programmatically with the Aigency platform, such as sending commands, querying user data, managing subscriptions, or triggering specific capabilities dynamically.
Example use case:
You want to send a text command to a user's AI capability to generate a response or perform an action, integrating this into a larger workflow that processes or routes the output.
Properties
| Name | Meaning |
|---|---|
| User ID | The numeric identifier of the user for whom the operation is performed. |
| ID | The string identifier relevant to the operation, e.g., capability ID when calling it. |
| Text | The text content sent as input when calling a capability or sending a message. |
Output
The node outputs JSON data under the json field containing the result of the called operation. For the "Call Capability" operation, the output JSON includes the response from the Aigency API corresponding to the invoked capability.
If an error occurs during the API call, the output will contain an error field describing the issue, provided the node is configured to continue on failure.
The node does not output binary data.
Dependencies
- Requires access to the Aigency API endpoint.
- Needs an API key credential and the API URL, which can be set either via:
- n8n credentials configuration (recommended), or
- environment variables
AIGENCY_API_KEYandAIGENCY_API_URL.
- Uses HTTP POST requests with JSON-RPC 2.0 format to communicate with the API.
Troubleshooting
- Missing Credentials: If neither credentials nor environment variables are set, the node throws an error indicating missing credentials. Ensure API key and URL are properly configured.
- API Errors: If the API returns an error, it is either thrown as a node error or returned in the output JSON if "Continue On Fail" is enabled.
- Invalid Input: Required properties like User ID, ID, and Text must be provided; otherwise, the node may fail or return errors.
- Network Issues: Connectivity problems to the API URL will cause failures; verify network access and API availability.
Links and References
- Aigency API Documentation (Replace with actual URL if available)
- n8n Documentation on Creating Custom Nodes