AigencyInstall

Overview

This node integrates with the Aigency API, allowing users to perform a variety of operations related to user capabilities, messages, subscriptions, and other account-related actions. The "Enable Capability" operation specifically enables a particular capability for a given user by their User ID and the capability's ID.

Common scenarios where this node is beneficial include:

• Managing user permissions or features dynamically by enabling or disabling capabilities.
• Automating subscription management and message handling within the Aigency platform.
• Retrieving user data such as balances, warnings, or usage history.
• Interacting programmatically with the Aigency API to streamline workflows involving user accounts and capabilities.

Practical example:

• Automatically enable a new feature (capability) for a user after they complete a certain action in your system, by calling the "Enable Capability" operation with the user's ID and the capability ID.

Properties

Output

The node outputs JSON data under the json field containing the result of the API call. For the "Enable Capability" operation, the output typically includes the response from the Aigency API indicating success or failure of enabling the capability.

If an error occurs during the API call, the output will contain an error field describing the issue.

No binary data output is produced by this node.

Example output structure:

{
  "result": {
    // API-specific response details about the enabled capability
  }
}

or in case of error:

{
  "error": "Error message describing what went wrong"
}

Dependencies

• Requires an API key credential and API URL for authenticating requests to the Aigency API.
• These credentials can be configured either in the n8n credentials interface or via environment variables named AIGENCY_API_KEY and AIGENCY_API_URL.
• 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 are not set either in credentials or environment variables, the node will throw an error stating that credentials are empty. Ensure these are properly configured.
• Invalid Credentials or Unreachable API: The connection test may fail if the API key is invalid or the API URL is unreachable. Verify network connectivity and correctness of credentials.
• API Errors: If the API returns an error (e.g., invalid user ID or capability ID), the node will either throw an error or continue on fail depending on the node settings. Check the error message for details.
• Parameter Issues: Make sure required parameters like User ID and ID are provided and correctly typed (User ID as number, ID as string).

Links and References

• Aigency API Documentation (Assumed link; replace with actual if available)
• n8n Documentation - Creating Nodes
• JSON-RPC 2.0 Specification