Aigency icon

Aigency

Interact with Aigency API
Join our community

Actions35

Overview

The node interacts with the Aigency API, providing various operations to manage user capabilities, messages, subscriptions, and other related data. Specifically, the "Remove Capability" operation allows users to remove a capability associated with a given user ID and capability ID.

This node is beneficial in scenarios where automated management of user capabilities is required, such as revoking access rights or disabling features for specific users programmatically. For example, an application could use this node to dynamically disable certain AI capabilities for users based on their subscription status or behavior.

Properties

Name Meaning
User ID The numeric identifier of the user whose capability is to be removed.
ID The string identifier of the capability to remove from the specified user.

Output

The output is a JSON object containing the result of the API call. Typically, it includes a result field with details about the success or failure of the removal operation. If an error occurs, the output will contain an error field describing the issue.

No binary data output is produced by this operation.

Example output JSON structure:

{
  "result": {
    // Details about the removed capability or confirmation message
  }
}

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 API.

Troubleshooting

  • Missing Credentials: If the API key or URL is not set, the node throws an error instructing to configure these credentials either in the environment variables or n8n credentials.
  • API Errors: If the API returns an error (e.g., invalid user ID or capability ID), the node outputs the error message. Users should verify that the provided IDs are correct and that the API key has sufficient permissions.
  • Network Issues: Connection failures or unreachable API endpoints will cause errors. Ensure network connectivity and correct API URL configuration.
  • Continue On Fail: If enabled, the node will continue processing subsequent items even if one fails, returning error details in the output JSON.

Links and References

Discussion