Actions13
- AI/ML Actions
- ChatGPT Actions
- Communication Actions
- Data Processing Actions
- E-Commerce Actions
- Printing Actions
- Utility Actions
Overview
The node provides an integration with the CustomJE API to save chat messages into a specified thread. It is designed for scenarios where you want to programmatically store conversation messages, such as logging user-assistant interactions or maintaining chat history in a centralized system.
A practical example use case is saving messages from a chatbot session: when a user sends a message or the assistant replies, this node can save each message with its role and content into a specific thread identified by a thread ID.
Properties
| Name | Meaning |
|---|---|
| API Key | Your CustomJE API key used for authenticating requests to the CustomJE service. |
| Thread ID | Identifier of the chat thread where the message will be saved. |
| Role | Role of the message sender; options are "User" or "Assistant". |
| Content | The actual text content of the message to be saved. |
Output
The node outputs a JSON object representing the response from the CustomJE API after attempting to save the message. This typically includes confirmation details or any data returned by the API about the saved message.
No binary data output is produced by this operation.
Dependencies
- Requires access to the CustomJE API endpoint
https://api.customje.com/save-messages.php. - Needs a valid API key credential for authentication.
- Network connectivity to the CustomJE service must be available.
Troubleshooting
Common issues:
- Invalid or missing API key will cause authentication failures.
- Incorrect or non-existent thread ID may result in errors or messages not being saved.
- Providing empty content or invalid role values might cause the API to reject the request.
Error messages:
- Errors returned from the API will be propagated by the node. Typical error messages could include authentication errors ("Invalid API key"), validation errors ("Thread ID not found"), or content errors ("Message content required").
Resolution tips:
- Verify that the API key is correct and has necessary permissions.
- Ensure the thread ID exists and is correctly formatted.
- Confirm that the role is either "user" or "assistant".
- Make sure the content field is not empty.
Links and References
- CustomJE API Documentation (general reference to the API base URL; specific docs not provided in source)