Workchat icon

Workchat

Consume Prinrcart API

Actions4

Overview

This node integrates with the Prinrcart API to interact with a messaging system called Workchat. Specifically, the "Send Message" resource with the "Get Detail Message" operation retrieves detailed information about a specific chat message for a given user ID.

Common scenarios include:

  • Fetching the full details of a conversation or message thread for a particular user.
  • Using the retrieved message details to display chat history or analyze communication content in workflows.
  • Automating customer support or internal communication tracking by pulling message details dynamically.

Example: A workflow that triggers when a new message is received and then fetches the detailed message content to process or log it.

Properties

Name Meaning
Authentication Method of authentication; currently supports "API Token" for accessing the API.
User ID The identifier of the user whose message details are to be retrieved.

Output

The output is a JSON array where each item corresponds to the response from the API call fetching message details for the specified user ID. The structure of each JSON object matches the API's response schema for message details, typically including message content, timestamps, sender/receiver info, and other metadata.

No binary data output is produced by this operation.

Dependencies

  • Requires an API token credential to authenticate requests against the Prinrcart Workchat API.
  • The node makes HTTP requests to endpoints under https://erp-amz.cloodo.com/v4/messages/.
  • n8n must be configured with the appropriate API token credential to authorize these calls.

Troubleshooting

  • Common issues:

    • Invalid or missing API token will cause authentication failures.
    • Incorrect or empty User ID may result in errors or empty responses.
    • Network connectivity problems can prevent successful API calls.

  • Error messages:

    • Authentication errors typically indicate invalid credentials; verify the API token.
    • 404 or "not found" errors suggest the User ID does not exist or no messages are available.
    • Timeout or connection errors require checking network access and endpoint availability.

To resolve errors, ensure the API token is valid and has necessary permissions, confirm the User ID is correct, and verify network connectivity to the API endpoint.

Links and References

Discussion