Actions7
Overview
This node integrates with the Monitchat platform to manage conversations and tickets. Specifically, the "Forward Conversation from User" operation allows forwarding an existing conversation to another user within the system, optionally adding a comment explaining the reason for forwarding.
This is useful in scenarios where a conversation needs to be escalated or redirected to a different team member or specialist for further handling. For example, customer support agents can forward complex queries to senior staff or specific departments by selecting the appropriate user.
Properties
| Name | Meaning |
|---|---|
| Conversation ID | The unique identifier of the conversation to forward. |
| Usuário | Select a user from your system to whom the conversation will be forwarded. |
| Comment | Optional comment or reason for forwarding the conversation. |
Output
The node outputs the JSON response returned by the Monitchat API after attempting to forward the conversation. This typically includes confirmation details about the forwarding action or error information if the request failed.
No binary data output is produced by this operation.
Dependencies
- Requires an API key credential for Monitchat to authenticate requests.
- Makes HTTP POST requests to Monitchat's API endpoint:
https://api-v4.monitchat.com/api/v1/token/forward-conversation/{conversation_id} - The node expects the Monitchat API to return JSON responses.
Troubleshooting
Common issues:
- Invalid or expired API key causing authentication failures.
- Incorrect conversation ID leading to "not found" errors.
- Selecting a user that does not exist or is not accessible with the provided credentials.
- Network connectivity problems preventing API calls.
Error messages:
- Errors returned from the API are passed through in the output JSON under an
errorfield if "Continue On Fail" is enabled. - Typical error messages might include authorization errors, invalid parameters, or server errors.
- Errors returned from the API are passed through in the output JSON under an
Resolutions:
- Verify the API key is correct and has necessary permissions.
- Confirm the conversation ID exists and is active.
- Ensure the selected user is valid and available in the system.
- Check network connectivity and retry if transient errors occur.
Links and References
- Monitchat API Documentation (assumed URL based on API endpoints)
- n8n documentation on HTTP Request Node for understanding how API calls are made
- General best practices for managing conversations and ticket forwarding in customer support systems