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 a variety of operations related to user messages, subscriptions, capabilities, and other account-related data. The "Get Dev Mode" operation specifically retrieves the development mode status for a given user.
Common scenarios where this node is beneficial include:
- Managing user interactions and messages programmatically.
- Automating subscription and capability management.
- Retrieving user-specific information such as balance, warnings, or dev mode status.
- Integrating Aigency's AI-driven services into workflows for enhanced automation.
For example, using the "Get Dev Mode" operation, a developer can check if a particular user has development mode enabled, which might influence how subsequent automated processes behave for that user.
Properties
| Name | Meaning |
|---|---|
| User ID | The numeric identifier of the user for whom the operation (e.g., "Get Dev Mode") applies. |
Output
The node outputs JSON data under the json field containing the result of the requested operation. For the "Get Dev Mode" operation, the output will typically include the development mode status information related to the specified user.
If an error occurs during the API call, the output JSON will contain an error field describing the issue.
No binary data output is produced by this node.
Dependencies
- Requires an API key credential and API URL for authenticating requests to the Aigency API.
- These credentials can be configured in the n8n Web interface or provided via environment variables named
AIGENCY_API_KEYandAIGENCY_API_URL. - The node uses HTTP POST requests with JSON-RPC 2.0 format to communicate with the Aigency 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 response, it will be included in the output JSON under the
errorfield. Common causes include invalid user IDs or unauthorized access. - Network Issues: Connectivity problems to the API endpoint may cause failures; verify network access and API availability.
- Invalid Input: Providing incorrect types or missing required properties like
User IDwill cause errors.
To resolve these issues:
- Verify that the API key and URL are correct and active.
- Confirm that the user ID exists and is valid.
- Check network connectivity to the API server.
- Use the "Continue on Fail" option to handle errors gracefully within workflows.
Links and References
- Aigency API Documentation (Assumed link, replace with actual if available)
- n8n Documentation - Creating Custom Nodes
- JSON-RPC 2.0 Specification: https://www.jsonrpc.org/specification