microsoft / microsoft/PowerPlatformConnectors

[BUG] HubSpot Conversations V2 - Get message history for a thread

Open
#4,128 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
C#
Stars
1.3k
Forks
1.5k
Avg merge
5d 15h
Merged PRs (30d)
11

Description

Type of Connector

Independent Publisher Connector

Name of Connector

HubSpot Conversations V2 - Get message history for a thread

Describe the bug

When thread has a messasge/comment created via Integration APP (e.g. Power Automate), there is an error when trying to get message history for this thread:

Action 'Get_message_history_for_a_thread' failed: The API 'hubspotconversations' returned an invalid response for workflow operation 'Get_message_history_for_a_thread' of type 'OpenApiConnection'. Error details: 'The API operation 'GetMessageHistoryForAThread' requires the property 'body/results/0/client/integrationAppId' to be of type 'String' but is of type 'Integer'.

Is this a security bug?

No, this is not a security bug

What is the severity of this bug?

Severity 1 - Connector is broken or there's a very serious issue

To Reproduce
  1. Configure your connection with HubSpot
  2. Create a comment with "Send a message to a thread" action
  3. Try to retrieve message history for given thread "Get message history for a thread"
Expected behavior

Action should work without issues (returned type has to be changed from string to int)

Environment summary

webapp: https://make.powerautomate.com

Additional context

none

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Search the connector definition for the GetMessageHistoryForAThread operation and inspect the response schema for body/results/0/client/integrationAppId. Reproduce the documented sequence with a message created through the Send a message to a thread action, then verify that retrieving the thread history succeeds when integrationAppId is returned as an integer.

Written by the indexing model from the issue text.

Assessment

Tech stack
openapi
Domain
api
Issue type
Bug
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.