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 data and subscriptions. Specifically, the "Get Subscriptions" operation retrieves a list of subscriptions associated with a specified user. This is useful for scenarios where you want to monitor or manage user subscriptions programmatically, such as integrating subscription data into workflows, generating reports, or triggering actions based on subscription status.
For example, you could use this node to fetch all active subscriptions for a user and then send notifications or update CRM records accordingly.
Properties
| Name | Meaning |
|---|---|
| User ID | The numeric identifier of the user whose subscriptions you want to retrieve. |
| Limit | Maximum number of subscription results to return (minimum 1). |
| Offset | Number of subscription records to skip before starting to collect the result set. |
Output
The node outputs an array of JSON objects under the json field. Each object represents a subscription record returned by the Aigency API for the specified user. The exact structure of each subscription object depends on the API response but typically includes details about the subscription such as its ID, status, source, and other metadata.
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 configured in the n8n credentials manager 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 API.
Troubleshooting
- Missing Credentials: If neither credentials nor environment variables are set, the node will throw an error indicating that credentials are empty. Ensure you have configured the API key and URL properly.
- API Errors: If the API returns an error (e.g., invalid user ID, rate limiting), the node will either throw an error or continue on fail depending on your workflow settings. Check the error message for details.
- Invalid Input: Providing non-numeric or missing User ID will cause the operation to fail since it is required and must be a number.
- Network Issues: Connectivity problems to the API URL will result in request failures. Verify network access and API endpoint availability.
Links and References
- Aigency API Documentation (Replace with actual URL if available)
- n8n Documentation - Creating Custom Nodes