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 capabilities, messages, subscriptions, and other account-related data. Specifically, the "Get Capabilities" operation retrieves a list of capabilities associated with a specified user.
This node is useful in scenarios where you want to programmatically manage or query user capabilities within the Aigency platform, such as fetching available features for a user, auditing permissions, or integrating capability data into workflows.
Example use cases:
- Fetching a paginated list of capabilities for a user to display in a dashboard.
- Automating checks on user capabilities before performing certain actions.
- Integrating capability data into reporting or monitoring systems.
Properties
| Name | Meaning |
|---|---|
| User ID | The numeric identifier of the user whose capabilities are being queried (required). |
| Limit | Maximum number of results to return in one call; controls pagination (required). |
| Offset | Number of items to skip before starting to collect the result set; used for pagination. |
Output
The node outputs an array of JSON objects under the json field. Each object represents a capability retrieved from the Aigency API for the specified user. The exact structure of each capability object depends on the API response but generally includes details about the capability's properties and status.
No binary data output is produced by this operation.
Dependencies
- Requires an API key credential and API URL endpoint for authenticating requests to the Aigency API.
- These credentials can be configured either via environment variables (
AIGENCY_API_KEYandAIGENCY_API_URL) or through the n8n credentials interface. - The node uses HTTP POST requests with JSON-RPC 2.0 format to communicate with the API.
Troubleshooting
- Missing Credentials: If neither environment variables nor configured credentials are found, the node will throw an error indicating missing credentials. Ensure that the API key and URL are properly set.
- API Errors: If the API returns an error (e.g., invalid user ID, rate limiting), the node will either throw an error or continue with partial results depending on the "Continue On Fail" setting.
- Pagination Issues: Incorrect use of
limitandoffsetmay lead to incomplete or repeated data. Adjust these parameters carefully to paginate through large datasets. - Network Issues: Connectivity problems or incorrect API URLs will cause request failures. Verify network access and endpoint correctness.
Links and References
- Aigency API Documentation (replace with actual URL if known)
- JSON-RPC 2.0 Specification
- n8n Documentation on Creating Custom Nodes