Create New HubSpot Object
Extended Use Case
Customer escalation automatically creates a HubSpot Ticket
Imagine a high-value customer reports a critical issue. Support creates a Bug in Jira to involve Engineering.
Without automation, the Customer Success Manager (CSM) manually creates a Ticket in HubSpot, copies details, and keeps updating it as progress happens. This causes:
Delays
Duplicate data entry
Inconsistent information
Poor visibility for Sales/CS
With this action rule, every qualifying Jira issue automatically creates a corresponding HubSpot Ticket (or Deal, Contact or Company).
Engineering works in Jira.
Revenue teams work in HubSpot.
Both see the same lifecycle, without manual syncing.
Automation Setup
A. Create the Action Rule in HubSpot for Jira Configuration
Go to HubSpot for Jira Configuration → Go to Automations.
Click Create New Action Rule and set:
Name (e.g., “Create HubSpot Ticket from Escalation”)
Action = Create New HubSpot Object
Jira Project = the project where the trigger issues live
Select HubSpot object(s) to create (Ticket/Deal/Company/Contact) and map HubSpot properties ↔ Jira fields(e.g., Ticket Name ← Summary; Description ← Description; Priority ← Priority).
Save → copy the authorization value (token) from the pop-up (you’ll need it in Jira; you can’t retrieve it later).
B. Create the Jira Automation rule
In Jira, create a new Automation rule with an Issue trigger (e.g., Work item created).
Add action Send web request and fill in exactly:
URL: https://embed-j-hubspot.resolution-cloud.com/api/automation/hubspot-for-jira
Body: Issue data – Automation format
Header: authorization = Bearer <token> (token from step A4)
Turn on the Jira rule.
C. Activate the Action Rule
Go back to HubSpot for Jira Automations → find the rule → Action menu → Activate.
Outcome
A brand-new HubSpot Ticket is created instantly.
The Jira issue is linked automatically.
Sales & CS get CRM visibility without leaving HubSpot.
No one needs to ask Engineering for updates.
