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. Specifically, the Get Current User operation retrieves information about a user based on their User ID. This node is useful in scenarios where you need to fetch user details from the Aigency platform as part of an automation workflow.
Practical examples include:
- Retrieving user profile data for personalization or reporting.
- Validating user existence before performing further actions.
- Integrating user data into other systems or workflows.
Properties
| Name | Meaning |
|---|---|
| User ID | The numeric identifier of the user whose current information you want to retrieve. |
Note: Although the provided JSON shows the User ID property required for many operations, for the Get Current User operation it is mandatory and must be supplied.
Output
The node outputs a JSON object under the json field containing the result returned by the Aigency API for the requested operation. For Get Current User, this will typically be the user's detailed information as provided by the API.
If an error occurs during the API call, the output JSON will contain an error field describing the issue.
The node does not output binary data.
Dependencies
- Requires an API key credential and API URL for authenticating and connecting to the Aigency API.
- These credentials can be configured either in the n8n credentials interface or 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 that the API key and URL are properly configured.
- API Errors: If the API returns an error (e.g., invalid User ID), the node either throws an error or, if "Continue On Fail" is enabled, outputs the error message in the JSON.
- Network Issues: Connection failures or unreachable API endpoints will cause errors; verify network connectivity and API endpoint correctness.
- 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 link if available)
- n8n Documentation on Creating Nodes