I’m currently maintaining an in-house app using the Hubspot NodeJS SDK for my company’s clients. While sending data up to the Engagements API for a Call or a Meeting, my client is missing the newline breaks within the location where info goes in the `hs_meeting_body` for meetings or `hs_call_body` for calls.
After some investigation, I found other posts and noticed the `<br>` tag works and it did for some time but for this particular client it does not.
I’m not sure how/why this occurs and it could be one of their own integrations but don’t know this might be the case.
Any help or advice would be greatly appreciated if anyone has encountered this type of issue!
Hi, @t-nguyen
Welcome to our community!
I don’t have a solution to offer. And I’d like to ask a few questions to assist the community in helping you troubleshoot.
- Could you please provide some examples of the data that you’re trying to send via the Engagements API? Specifically, examples where newline breaks are missing would be helpful.
- You mentioned that this is happening to a particular client—are you facing this issue with other clients as well, or is it isolated to just this one?
- Have there been any recent changes to the client’s setup that could potentially affect this?
- As for the
<br> tag, it should ideally work. Are there any specific circumstances under which it fails?
- The more details you can provide, the better the community will be able to assist you
Thank you! — Jaycee
Hi @Jaycee_Lewis
Thanks for getting back to me and I’ll do my best to answer the questions you have given me.
Using the Hubspot Node SDK, I’m sending up a request to Hubspot with the following example:
const description = `some stringify description
<br>
<br>
line break tests`
const response = await hubspotClient({
method: “POST”,
path: “/crim/v3/objects/calls”,
body: {
properties: {
hs_call_title: “some title”,
hs_call_body: description,
},
},
})
For the meetings, I’m doing something similar but I’m accessing the `hs_internal_meeting_notes: description` and it works fine from my experience.
My colleague has told me that it’s only clients within this specific company that’s experiencing this issue.
For the issue when the <br> fails, I haven’t been able to reproduce this on my local environment when I’m contacting the SDK directly and through our in-house app.