Helpwise

Retrieves complete details of a specific conversation by ID from Helpwise. Returns the conversation metadata including subject, status, participants, and timestamps. Use this action when you need to view or analyze a specific conversation's details. Example use cases: - Checking the status of a support ticket conversation - Viewing conversation participants and assignees - Retrieving conversation metadata for reporting

Tool to search contacts by term with pagination. Use when you need to find contacts by name, email, phone, or other contact attributes.

Retrieves a specific attachment by its unique identifier. Use this after obtaining an attachment ID from conversations, messages, or attachment listings to get detailed attachment metadata including download URL, file name, content type, and timestamps.

Retrieves attachments from messages in a specific conversation. Important: Helpwise does not provide a dedicated attachments endpoint. This action retrieves attachments by fetching messages from the conversation and extracting attachment information from them. A conversation_id is required to use this action. Use this when you need to: - Get all file attachments from a specific conversation - Access attachment metadata (filename, URL, size, content type) - Download files shared in customer support conversations Note: This action retrieves attachments through the messages endpoint, as Helpwise embeds attachment data within message objects rather than providing a standalone attachments resource.

Tool to retrieve details of a specific note. Use when you know the conversation and note IDs and need full note information.

Retrieves all notes associated with a specific conversation. Notes are internal comments or annotations that team members add to conversations for collaboration and context.

Tool to retrieve a list of conversations. Use when you need to list and paginate support conversations for display or analysis.

Retrieves detailed information for a specific contact by ID. Use this when you need to fetch complete contact details including name, email, phone, company, and timestamps for a known contact ID.

Retrieves details of a specific custom field by its ID. Use this when you need to fetch custom field properties such as name, description, value, associated inboxes, and creator information.

Tool to retrieve details of a specific mailbox by its ID. Use when you know the mailbox ID and need full mailbox information.

Tool to upload a new attachment. Use when you need to send a file to Helpwise and receive its attachment metadata.

Tool to add a note to a conversation. Use after obtaining the conversation_id to provide context.

Creates a new team in Helpwise to group users for collaboration and assignment purposes. Use this tool when you need to: - Create a new team with a unique name - Optionally add a description for the team - Optionally assign initial members by their user IDs IMPORTANT: Team creation via API is not available in the current Helpwise API. All tested endpoints (/api/v1/teams, /dev-apis/teams, /api/v1/team, /dev-apis/team) return 404. Team management appears to be limited to the Helpwise web interface. If you need to create teams, please: 1. Use the Helpwise web interface at https://app.helpwise.io 2. Contact Helpwise support at dev@helpwise.io to request API endpoint availability This action is implemented speculatively for future API support and follows standard patterns used in other Helpwise actions.

Creates a new webhook subscription in Helpwise to receive real-time event notifications. Use this action to programmatically subscribe to Helpwise events like conversation creation, message replies, conversation assignments, status changes, and tag applications. Webhooks deliver JSON payloads to your specified callback URL when subscribed events occur. IMPORTANT: Helpwise webhook management is primarily done through the UI at: Settings > Automation > Integrations > Webhooks (https://app.helpwise.io/settings/integrations) This action attempts to use programmatic API endpoints, but if they're unavailable in your Helpwise plan or environment, you'll need to create webhooks manually via the UI.

Tool to update an existing Helpwise contact. Use when you need to modify contact details or custom attributes.

Tool to update an existing message. Use when you need to modify message content by its ID.

Updates an existing tag's name and/or color in Helpwise. Use this action when you need to rename a tag or change its visual appearance. You must have the tag's ID before calling this action - obtain it using HELPWISE_GET_TAG or from the Helpwise UI.

Updates an existing Helpwise email template by modifying its name, subject, and/or HTML content. Use this action when you need to: - Change the display name of a template - Update the subject line (including placeholders) - Modify the HTML content/body of the template Prerequisites: - You must have the template_id (obtain via Get Templates action or Helpwise UI) - At least one field (name, subject, or html) must be provided for update Note: This action performs a partial update - only provided fields will be modified.

Updates an existing Helpwise mailbox. Use this action to modify mailbox settings such as display name, email address, team assignment, email signature, or default status. At least one field must be provided for update. Obtain the mailbox_id from the Get Mailboxes action.

Deletes a contact from Helpwise by its unique identifier (ID). Use this action when you need to permanently remove a contact from your Helpwise account. Returns an empty response (HTTP 204 No Content) on successful deletion. Note: This action is idempotent - deleting a non-existent contact will return an appropriate error.

Permanently deletes a tag from Helpwise. This action removes the tag from all conversations where it was applied and cannot be undone. Use this when you need to permanently remove a tag that is no longer needed. Note: Deleting a tag will automatically remove it from all existing conversations that use this tag.

Tool to delete a team. Use when you need to remove an existing team by its unique identifier after confirming the ID and dependencies.

Deletes an email signature from Helpwise. Email signatures are text/HTML templates that automatically append to outgoing emails from specific mailboxes or users. This action permanently removes the signature identified by the signature_id. Returns an empty response on successful deletion (204 No Content).

Attempts to delete a conversation by ID from Helpwise. Note: The Helpwise API may not support conversation deletion via the REST API. If deletion is not supported, this action will return an error indicating that the endpoint was not found or the method is not allowed. Use this action when you need to attempt to permanently remove a conversation by its ID.

Attempts to delete a message from Helpwise. Note: The Helpwise API may not support message deletion via the REST API. If deletion is not supported, this action will return an error indicating that the DELETE method is not allowed (HTTP 405). Use this action when you need to attempt to permanently remove a message by its ID.

Tool to delete a note from a conversation. Use when you need to permanently remove a note by its ID from a specific conversation after confirming the IDs.

Delete a Helpwise webhook by its ID. Use this tool when you need to permanently remove a webhook configuration. Returns an empty response on successful deletion (HTTP 204 No Content).

Tool to delete a mailbox by its unique identifier. NOTE: As of 2026, the Helpwise API may not support mailbox deletion via API. This action attempts deletion but will fail if the endpoint is not available (405 Method Not Allowed). Consider managing mailboxes through the Helpwise web interface if API deletion is unsupported.

Deletes a Helpwise email template (saved reply) by its ID. Returns empty response on success (HTTP 204). Use this tool when you need to permanently remove a template that is no longer needed. Ensure the template_id is valid before deletion - this operation cannot be undone. Common responses: - Success (204): Template deleted successfully - Not Found (404): Template ID does not exist or was already deleted - Forbidden (403): No permission to delete this template