Good Afternoon,
I work for a company that has multiple Hubspot accounts. I need to be able to create a new ticket in an account other than my own.
I have tested a basic ticket creation in Postman using a private app key setup in the other Hubspot account. I would now like to automate this within a Hubspot workflow under my divisions account.
Can someone help me translate my Postman code over to a custom code solution? I'm not sure if I still need to use the "SECRET" drop down or "Property to Include in code" drop down if those are embedded in the code below. I know I have to put my API key within "YOUR_API_KEY" and I expect I have to change the properties to what I want to send to the new ticket but I'm unsure about what else to change.
I am including three snips. One of my working Postman code.
One of the raw code I copied from the Hubspot developer page.
One with as much info as I know to include so far. Row 17 is marked as having en error so I expect there's a few items I missed here. Maybe the "string" in row 14 for the contact association. I just want to get the most BASIC code working first.
Language set as "Node.js 20.x. This is the code copied from the developer page
This is what I have filled in so far:
7 Accepted solutions
@SMCNULTY - It definitely seems you are 90% of the way to using the API for your purpose. I only have a couple of suggestions that I use in my custom code Python templates:
- Confirm run-time configurtion at the startup of the code:
def main(event):
#get standardized run-time context information
objectType = event.get('object').get('objectType')
objectId = event.get('object').get('objectId')
print("Type: ", objectType, objectId)
- Yes, use the "secret" functionality so that you can rotate you access key as required and not have to find/edit a lot of hard coded values at some point in the future:
#Get the API key as environment variable
api_token=os.getenv('CUSTOM_TOKEN')
#HS API Request Headers
hs_headers = {
'Content-Type': 'application/json',
'Authorization': 'Bearer ' + api_token,
}
- Use property values passed into the code as required and return confirmation value to the containing workflow.
return {
"outputFields": {
"error": hs_error
}
}
I hope that's helpful.
Steve
| |||||||||||||||||
| |||||||||||||||||
| Create Your Own Free Signature |
OK so I quickly tried your code. Confirm this is correct:
I made two private apps with appropriate permissions. I copied the API from each and created two secrets within the workflow custom code. I named them WF_KEY_001 and WF_KEY_002. I didn't touch anything else in the code. I got a whopping error response below.
OK I swapped out the contact ID over to my email. After so many weeks of struggling I finally got the GREEN light! First ever in custom code. I've seen a hundred red/fails. THANK YOU! I just needed somewhere to start, I can tweak from here for additional properties and associations.
Great thank you for that addional information. Especially about the error catching and review. I haven't experimented with output variables but that's definitely next. I'd like to make the code robust with error handling. I would even like to be notified when it fails, so I can go in and troubleshoot. Our every day customer service reps will just be changing ticket status to trigger this code, they won't know or care if it actually worked on the back end or not.
I do get this warning from within the hubspot custom code response. I don't think it's hurting anything, but if I can supress it or modify the code to meet the Node.JS 24 standard, all the better. I noticed you used callback in your above examle and it seems support for that will be gone soon.
I will carefully strip back what I don't really need at a later date. (like the rotating key) As long as it's working I'm under some pressure to get my demo done for this project. In case you couldn't tell I'm not a programmer, I just play one on TV. No one else is willing to do this stuff here.
While I have your attention, My next step was to include a property in the data push from one account to another. When I hardcode the property value, (pipeline/status/ticket name etc) those transfer over fine to the new ticket but when I try to use a property, it's not working. (I am giving the property a value in the workflow) I think it has to do with my GET command, but I've tried every combo of:
'Unitec Ticket'
Unitec Ticket
'unitec_ticket'
unitec ticket
I have IDENTICAL properties between the two accounts with Identical internal names.
For both - Unitec Ticket is the Property Label and unitec_ticket is the internal name.
One problem I just found for sure was this:
processingData.properties["Unitec Ticket"] = UnitecTicketNumber
should use the internal name
processingData.properties["unitec_ticket"] = UnitecTicketNumber
but still erroring out so I must have multiple issues here
I coded it that way (as an experiment) because if you follow the link to the HS documentation that's what it showed. but now that I look back, that's a Python example. That was my mistake.
The HS JS example is this:
which is like what you suggested. Instead of defining "unitecticketnumber" as a VAR up top. I took that out and just put in this line.
Works!! Thanks again! i'm creeping toward success here. I can now create a ticket and push over whatever properties I want. Next will be different objects(?) like you mentioned Ticket Owner (hubspot_owner_ID) and I also want to look into pulling contact/company internal ID's. I can do that in Postman and I've been using the lame method of checking the URL for the ID but I have to get that into code.
This is likely a dumb question but I looked through your (working) code and I don't see where the URL is called out. Like api.hubspot.com/crm/v3/objects/tickets.
For some reason I have no problem at all getting these API calls to work in Postman. It would be so much more helpful/easier if I could just copy the JSON code over from Postman to Hubspot but there are almost always errors.
This took all of 5 minutes to get working:
But when I try all four of these JS Postman "conversions" none work. (I am copying in my API code)
NodeJS - Axios
const axios = require('axios');
let data = JSON.stringify({
"properties": {
"otis_ticket": "12345"
}
});
let config = {
method: 'patch',
maxBodyLength: Infinity,
headers: {
'Content-Type': 'application/json',
'Authorization': '••••••',
'Cookie': '__cf_bm=yZkctTLsozMjwzvhVHKJzQ8xuEdN0fBrIkewSin4mpc-1753715052-1.0.1.1-dpEsJkgVM_EHcb5QfaTjLl3KyNIsezUFg4JtoDvR2jwB7bW9UN5bVLgTxRnHGA_L7AGgKRarHNiE6nUsoOQuUMTbaTk0wqqat1FHrIjq2rk'
},
data : data
};
axios.request(config)
.then((response) => {
console.log(JSON.stringify(response.data));
})
.catch((error) => {
console.log(error);
});
NodeJS - Native
var https = require('follow-redirects').https;
var fs = require('fs');
var options = {
'method': 'PATCH',
'hostname': 'api.hubapi.com',
'path': '/crm/v3/objects/tickets/26941972792',
'headers': {
'Content-Type': 'application/json',
'Authorization': '••••••',
'Cookie': '__cf_bm=yZkctTLsozMjwzvhVHKJzQ8xuEdN0fBrIkewSin4mpc-1753715052-1.0.1.1-dpEsJkgVM_EHcb5QfaTjLl3KyNIsezUFg4JtoDvR2jwB7bW9UN5bVLgTxRnHGA_L7AGgKRarHNiE6nUsoOQuUMTbaTk0wqqat1FHrIjq2rk'
},
'maxRedirects': 20
};
var req = https.request(options, function (res) {
var chunks = [];
res.on("data", function (chunk) {
chunks.push(chunk);
});
res.on("end", function (chunk) {
var body = Buffer.concat(chunks);
console.log(body.toString());
});
res.on("error", function (error) {
console.error(error);
});
});
var postData = JSON.stringify({
"properties": {
"otis_ticket": "12345"
}
});
req.write(postData);
req.end();
NodeJS - Request
var request = require('request');
var options = {
'method': 'PATCH',
'headers': {
'Content-Type': 'application/json',
'Authorization': '••••••',
'Cookie': '__cf_bm=yZkctTLsozMjwzvhVHKJzQ8xuEdN0fBrIkewSin4mpc-1753715052-1.0.1.1-dpEsJkgVM_EHcb5QfaTjLl3KyNIsezUFg4JtoDvR2jwB7bW9UN5bVLgTxRnHGA_L7AGgKRarHNiE6nUsoOQuUMTbaTk0wqqat1FHrIjq2rk'
},
body: JSON.stringify({
"properties": {
"otis_ticket": "12345"
}
})
};
request(options, function (error, response) {
if (error) throw new Error(error);
console.log(response.body);
});
NodeJS - Unirest
var unirest = require('unirest');
.headers({
'Content-Type': 'application/json',
'Authorization': '••••••',
'Cookie': '__cf_bm=yZkctTLsozMjwzvhVHKJzQ8xuEdN0fBrIkewSin4mpc-1753715052-1.0.1.1-dpEsJkgVM_EHcb5QfaTjLl3KyNIsezUFg4JtoDvR2jwB7bW9UN5bVLgTxRnHGA_L7AGgKRarHNiE6nUsoOQuUMTbaTk0wqqat1FHrIjq2rk'
})
.send(JSON.stringify({
"properties": {
"otis_ticket": "12345"
}
}))
.end(function (res) {
if (res.error) throw new Error(res.error);
console.log(res.raw_body);
});
@SMCNULTY - It definitely seems you are 90% of the way to using the API for your purpose. I only have a couple of suggestions that I use in my custom code Python templates:
- Confirm run-time configurtion at the startup of the code:
def main(event):
#get standardized run-time context information
objectType = event.get('object').get('objectType')
objectId = event.get('object').get('objectId')
print("Type: ", objectType, objectId)
- Yes, use the "secret" functionality so that you can rotate you access key as required and not have to find/edit a lot of hard coded values at some point in the future:
#Get the API key as environment variable
api_token=os.getenv('CUSTOM_TOKEN')
#HS API Request Headers
hs_headers = {
'Content-Type': 'application/json',
'Authorization': 'Bearer ' + api_token,
}
- Use property values passed into the code as required and return confirmation value to the containing workflow.
return {
"outputFields": {
"error": hs_error
}
}
I hope that's helpful.
Steve
| |||||||||||||||||
| |||||||||||||||||
| Create Your Own Free Signature |
I was able to get this chunk of code working. Basically cut and paste luck. It is producing an error but still actually makes a new ticket.
