This article demonstrates a way to get the name of a custom deal stage using its ID obtained in the response of any of the HubSpot journeys in Quickwork.
What you'll need:
Skill level: Easy
Time required: 4 minutes
- HubSpot account
- A few custom deal stages in your HubSpot account
Whenever a new deal is created in a pre-created default deal stage of HubSpot, Quickwork showcases the stage name in the response. For example, consider a deal called L&T demo is created in the CONTRACT SENT stage as shown here:
The Output block of the Quickwork displays the stage name:
The above image emphasizes that the value
key is associated with a value called contractsent
under the dealstage
object. This is the name of the stage in which a deal is created.
However, if a deal is created in a custom stage, which is not pre-created in HubSpot, the value key associates a number to it rather than the actual name of the stage. For example, consider a deal called Infosys Automation Process is created in the CUSTOM STAGE stage as shown here:
The Output block of the Quickwork displays the ID of the stage rather than the stage name:
The above image emphasizes that the value
key has an ID called 17557226
under the dealstage
object. This is the ID of the stage in which a deal is created.
To get the stage name in which a deal is created, log in to your HubSpot account and click the gear (Settings) icon. Then go to Objects | Deals:
Scroll down the window. You'll get a list of stages created in your account. Now, hover over these stages. You'll get the code icon and Delete option for each stage. Upon clicking the code icon, a small dialog box appears displaying the ID of the respective stage. Hover over all the stages and check the ID you received in the Output tab with the ID getting displayed on HubSpot UI:
By referring to the above image, it is confirmed that the ID we received in the Output block belongs to Custom stage of Hubspot in which a new deal was created.
You can now use this stage name, tweak with queries and use it in other journeys.
Comments
0 comments
Please sign in to leave a comment.