Bug Report: HubSpot connector write operations return error 500

Q&A
, ,
1

Product: Amazon Quick (AI Assistant)
Region: us-east-1
Date: 2026-08-16

Problem

The HubSpot connector in Amazon Quick fails on all write operations (creating and updating deals) with HTTP error 500. Read operations work normally.

Expected behavior

Create and update records in HubSpot via the Quick assistant, just as read operations already work.

Actual behavior

Any write attempt returns:

errorMessage: "[object Object]"
errorCode: "500"

The “[object Object]” message indicates the original error is not being properly serialized in the response.

Steps to reproduce

  1. Ask Quick to create a deal in HubSpot with valid data (existing pipeline, stage, and associated company)
  2. Or ask Quick to update any field on an existing deal
  3. Both operations fail with error 500

Evidence

  • Reading companies, deals, properties, and pipelines: :white_check_mark: OK
  • Creating a Deal: :cross_mark: Error 500
  • Updating a Deal: :cross_mark: Error 500
  • The same create/update procedure works via other HubSpot integrations (e.g., Claude MCP), confirming the issue is not on HubSpot’s side

Request IDs

  • b8784c9d-e5d2-457c-8359-75216e0f550f — 2026-08-16 21:01 UTC
  • 001e34cb-5ac6-4323-965f-49dd8511e0dc — 2026-08-16 21:05 UTC
  • 3e7ab91d-e427-4831-884d-8f64d0e5714f — 2026-08-16 22:52 UTC

Environment

  • HubSpot Portal: 47324227
  • AWS Region: us-east-1
  • Issue persisted for at least 2 hours of testing
2

Hi @joaolima and welcome to the community!

The fact that reads work fine but all writes return a 500, combined with the [object Object] serialization in the error message, makes me believe this is a service-side issue rather than anything on your end or HubSpot’s side (especially since you’ve confirmed the same operations work via another integration). The community is a public facing forum and this seems like something to be resolved on the connector’s backend. I’d recommend opening an AWS support ticket (Case management - AWS Support) and including the request IDs and timestamps you already have.

Hope this gets resolved and feel free to keep us updated!

3

Hi @joaolima,

Just checking back in since we haven’t heard from you in a bit. I wanted to see if the guidance shared earlier helped resolve your question, or if you found a solution in the meantime. Moreover, if you submitted a support ticket and it uncovered any findings, please feel free to share them!

If you still have any additional questions related to your initial post, feel free to share them. Otherwise, any update you’re able to provide within the next 3 business days would be helpful for the community.

Thank you.