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 messaging and subscriptions. Specifically, the "Send Message" operation sends a text message on behalf of a specified user ID. This is useful in scenarios where automated or programmatic communication needs to be sent through the Aigency platform, such as chatbots, notification systems, or customer engagement tools.
For example, you can use this node to send a custom message to a user identified by their user ID, enabling integration of Aigency messaging capabilities into your workflows.
Properties
| Name | Meaning |
|---|---|
| User ID | The numeric identifier of the user to whom the message will be sent. |
| Text | The content of the message to send. |
Output
The output is a JSON object containing the result of the "sendMessage" operation from the Aigency API. Typically, this includes confirmation details or metadata about the sent message. If an error occurs, the output JSON will contain an error field describing the issue.
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 either in the n8n credentials interface 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 throws an error indicating missing credentials. Ensure that the API key and URL are properly configured.
- API Errors: If the API returns an error response, it will be included in the output JSON under the
errorfield. Common causes include invalid user IDs, malformed messages, or network issues. - Continue On Fail: If enabled, the node will continue processing subsequent items even if one fails, returning error details in the output JSON instead of stopping execution.
- Invalid User ID or Text: Make sure the User ID is a valid number and the Text is a non-empty string, as both are required fields.
Links and References
- Aigency API Documentation (hypothetical link, replace with actual if available)
- n8n Documentation - Creating Custom Nodes