WTS Chat icon

WTS Chat

Get data from Wts API

Actions17

Overview

This node integrates with the Helena API to manage various resources such as contacts, messages, sessions, and panels. Specifically for the Panel resource and the Create Annotation File operation, it allows users to add annotation files (attachments) to a specific card within a panel by providing URLs of the files.

Common scenarios where this node is beneficial include:

  • Attaching supporting documents or images to project cards or tasks in a CRM-like panel system.
  • Automating the process of adding file annotations to cards based on external triggers or workflows.
  • Enhancing collaboration by programmatically linking relevant files to panel cards.

Example use case:

  • A workflow that receives file URLs from an external source and automatically attaches these files as annotations to a specified card in a panel for team review.

Properties

Name Meaning
Card ID The unique identifier of the card in the panel to which the annotation files will be added.
File Urls A collection of one or more URLs pointing to the files to attach as annotations to the card.

Output

The output is a JSON object representing the response from the Helena API after creating the annotation file(s). This typically includes details about the newly created annotation note linked to the card, such as IDs, timestamps, and metadata related to the uploaded files.

No binary data output is produced by this operation; it only returns JSON metadata about the annotation.

Dependencies

  • Requires an active API key credential for the Helena API service.
  • The node makes HTTP POST requests to the Helena API endpoint at https://api-test.helena.run/crm/v1/panel/card/{cardId}/note.
  • Proper network access to the Helena API endpoint is necessary.

Troubleshooting

  • Invalid Card ID: If the provided card ID does not exist or is incorrect, the API may return an error. Verify the card ID before running the node.
  • Invalid File URLs: Ensure that the URLs provided are accessible and valid. Malformed URLs or inaccessible files might cause the API request to fail.
  • Authentication Errors: Missing or invalid API key credentials will result in authorization errors. Confirm that the API key is correctly configured in n8n credentials.
  • API Rate Limits or Downtime: Temporary failures could occur due to rate limiting or API downtime. Retry after some time if such errors occur.

Links and References

Discussion