topic Re: Upserting custom object from Twilio Segment into HubSpot in APIs & Integrations

Upserting custom object from Twilio Segment into HubSpot

MBuhr — Tue, 09 Jan 2024 00:12:37 GMT

We have been trying to push data from Twilio Segment into HubSpot by upserting a custom object.

The custom object in HubSpot is called customer values and the field I am trying to push data into is called 'segment'. We are essentially building an audience within Twilio Segment and then pushing a value for this audience into the field 'segment' within the custom object.

We are getting error of 'search criteria not unique' when sending data to HubSpot from Twilio Segment.

I have set the custom object to be unique records only as I want one customer to only be in one segment at a time but that should surely not be causing any issues?

Has anyone come across the same issue or has done the mapping for Twilio Segment by upserting a custom object and can help?

Re: Upserting custom object from Twilio Segment into HubSpot

BérangèreL — Tue, 09 Jan 2024 09:56:48 GMT

Hi @MBuhr and all my Best Wishes for 2024!!!

I love to read your post, thank you for asking the Community!

I understand that you are using this "Segment" integration and this "CRM Search" API. If that's not the case, please let me know.

To be able to investigate further, could you please give us the following information (without sensitive/confidential information):

- What are you trying to achieve exactly, please?
- The method used (get/put...)
- The URL used
- The raw body of the request
- The response of the request

To start with, I found this related article that might be of interest: "Upsert custom object record".

I also would like to put you in touch with one of our Community Members who also uses this integration: Hi @MNabi did you ever get this type of error, please? Or do you know what could cause this behavior, please?

I also wanted to invite a couple of subject matter experts to this conversation: Hi @mangelet, @MBERARD, @Teun and @louischausse do you have customers who use Segment and get this error, please? Do you have suggestions to help @MBuhr, please?

If anybody else has anything to add and/or share, please feel free to join in the conversation 🙂

I can see that you currently have a ticket open with our technical support team. It looks like the team is currently investigating this for you. I would invite you to continue working with them as this may require deep troubleshooting and direct access to your account and would be the best course of action.

Thank you very much 🌟 and have a wonderful day!

Best,
Bérangère

Re: Upserting custom object from Twilio Segment into HubSpot

MBuhr — Wed, 10 Jan 2024 01:45:16 GMT

Thanks so much for replying to this, we had a few frustrating days to say the least.

Yes, we have logged a ticket and it is being worked on but it would be great to get in touch with someone who has successfully upserted a custom object from Segment into HubSpot as we are currently out of ideas.

To answer your questions:

- What are you trying to achieve exactly, please?

We have built an audience within Segment and would like to label this audience as a Segment in a custom object called 'Customer Values'. It should be recorded into the property 'segment'. We built an audience with certain criteria in Segment called 'Business Direct', we now want to push this audience into HubSpot and record the value of 'Business Direct' to the property 'segment' within the Custom Object called 'Customer Values'

- The method used (get/put...)

Put I guess, we are upserting a custom object so pushing from Segment into HubSpot

- The URL used

The primary endpoint for this request would be https://api.hubapi.com/crm/v3/objects/ - you can also find their integration code here:

· Creates a CRM object - https://github.com/segmentio/action-destinations/blob/main/packages/destination-actions/src/destinations/hubspot/api/index.ts#L73

· Updates a CRM object - https://github.com/segmentio/action-destinations/blob/main/packages/destination-actions/src/destinations/hubspot/api/index.ts#L90

- The raw body of the request (this is Page 4 as that was the page with the error on it)

{

"body": {

"filterGroups": [

{

"filters": [

{

"operator": "EQ",

"propertyName": "hs_object_id",

"value": "12345678"

}

]

}

"properties": [],

"sorts": []

"headers": {

"Accept": "*/*",

"Accept-Encoding": "gzip,deflate",

"Authorization": "REDACTED",

"Connection": "close",

"Content-Length": "126",

"Content-Type": "application/json",

"Host": "api.hubapi.com",

"User-Agent": "REDACTED"

"method": "POST",

"url": "https://api.hubapi.com/crm/v3/objects/contacts/search"

}

- The response of the request (this is Page 4 as that was the page with the error on it)

{

"body": "",

"headers": {

"Access-Control-Allow-Credentials": "false",

"Cf-Cache-Status": "DYNAMIC",

"Cf-Ray": "8428e4d41b572804-SEA",

"Connection": "close",

"Content-Encoding": "gzip",

"Content-Length": "226",

"Content-Type": "application/json;charset=utf-8",

"Date": "Tue, 09 Jan 2024 01:26:46 GMT",

"Nel": "{\"success_fraction\":0.01,\"report_to\":\"cf-nel\",\"max_age\":604800}",

"Report-To": "{\"endpoints\":[{\"url\":\"https:\\/\\/a.nel.cloudflare.com\\/report\\/v3?s=Hc8cqaOX8ri6lfPLGIi25%2BQ6ERgzLZra0wv5lZbycfE6yLXly9FznXLfeXZJyNLGLDvccy%2BJ8W6PerLthoY3uFKEh887L08lURh8nhM8V%2BXIlT0W4ImlX3l%2FXQO7qbZl\"}],\"group\":\"cf-nel\",\"max_age\":604800}",

"Server": "cloudflare",

"Strict-Transport-Security": "max-age=31536000; includeSubDomains; preload",

"Vary": "origin, Accept-Encoding",

"X-Content-Type-Options": "nosniff",

"X-Envoy-Upstream-Service-Time": "973",

"X-Evy-Trace-Listener": "listener_https",

"X-Evy-Trace-Route-Configuration": "listener_https/all",

"X-Evy-Trace-Route-Service-Name": "envoyset-translator",

"X-Evy-Trace-Served-By-Pod": "iad02/hubapi-td/envoy-proxy-57d4fb94bb-vf7wj",

"X-Evy-Trace-Virtual-Host": "all",

"X-Hubspot-Correlation-Id": "4778751a-6bfd-43aa-bc8f-e3cb30668426",

"X-Request-Id": "4778751a-6bfd-43aa-bc8f-e3cb30668426",

"X-Trace": "2BA557EF8584EAAED1D243D5036B8E1155458A0325000000000000000000"

"statusCode": 200,

"statusMessage": "OK"

}