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 named "Aigency" allows interaction with the Aigency API through various operations related to user data, messaging, subscriptions, capabilities, and more. It is designed to facilitate automation workflows that require managing or querying user-related information and actions on the Aigency platform.
For the Enable Dev Mode operation specifically, the node enables developer mode for a specified user by their User ID. This can be useful in scenarios where developers want to activate special debugging or development features for a user account programmatically within an n8n workflow.
Practical example:
- Automatically enable developer mode for a user after they complete a certain onboarding step.
- Use it as part of a larger automation to toggle dev mode on/off based on external triggers or conditions.
Properties
| Name | Meaning |
|---|---|
| User ID | The numeric identifier of the user for whom the developer mode will be enabled. Required. |
Output
The node outputs JSON data under the json field containing the result of the API call. For the Enable Dev Mode operation, this typically includes a success confirmation or relevant response from the Aigency API indicating whether the developer mode was successfully enabled for the user.
If an error occurs, the output JSON will contain an error field describing the issue.
Dependencies
- Requires an API key credential and API URL for authenticating requests to the Aigency API.
- These credentials can be configured in the n8n credentials interface or provided via environment variables:
AIGENCY_API_KEYAIGENCY_API_URL
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 (e.g., invalid user ID, permission issues), the node either throws an error or outputs the error message depending on the "Continue On Fail" setting.
- Network Issues: Connection failures to the API endpoint will cause errors; verify network connectivity and API availability.
- Invalid User ID: Providing a non-numeric or incorrect user ID may lead to API errors.
Links and References
- Aigency API Documentation (Assumed, replace with actual if available)
- n8n Documentation on Creating Custom Nodes