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. The "Sync Capabilities" operation specifically synchronizes the capabilities of a given user by their User ID.
This node is beneficial in scenarios where you need to programmatically manage or synchronize user capabilities within the Aigency platform, such as updating user permissions, syncing feature access, or integrating Aigency capabilities into automated workflows.
Example use case:
Automatically sync a user's capabilities after an external event (e.g., user role change in another system) to ensure the user's permissions are up-to-date in Aigency without manual intervention.
Properties
| Name | Meaning |
|---|---|
| User ID | The unique numeric identifier of the user whose capabilities will be synchronized. |
Output
The output is a JSON object containing the result of the synchronization operation. It typically includes details about the updated capabilities or status confirmation from the Aigency API.
If an error occurs during the operation, the output JSON will contain an error field describing the issue.
No binary data output is produced by this operation.
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 the API key or URL is not provided, the node will throw an error instructing to set environment variables or configure credentials.
- 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 or network issues. - Continue on Fail: If enabled, the node will continue processing subsequent items even if one fails, returning error details per item.
- Connection Issues: Ensure that the API URL is reachable and the API key is valid. Test connectivity using the node's connection test feature or manually via API tools.
Links and References
- Aigency API Documentation (Assumed link; replace with actual if available)
- JSON-RPC 2.0 Specification
- n8n Documentation: Creating Custom Nodes