Catch Buying Intent in Zendesk Tickets
When a customer asks about buying, upgrading, or expanding, have Notis turn that ticket into a HubSpot deal for follow-up.
Trigger
New Zendesk Ticket
Triggers when a new ticket is created in a specified Zendesk view.
Action
Create batch of deals
Creates multiple deals in hubspot crm; ensure any associated object ids, deal stages, and pipeline ids specified are valid and exist within the hubspot account.
Why this helps
Purchase questions can sit in the support queue while sales teams miss a timely opportunity to respond.
- Surface explicit purchase interest for sales follow-up
- Include relevant ticket context in the deal details
- Reduce the chance that buying questions stay in the support queue
Setup
Build it in a few focused steps.
- 1Connect Zendesk and HubSpot once in the Notis portal.
- 2Create an automation in Notis and give it a name.
- 3Describe in one instruction when a ticket counts as buying intent and what context to include in a HubSpot deal.
- 4Pick the Zendesk New Zendesk Ticket trigger and choose where run reports should go.
- 5Test with one real ticket and verify the account's required deal pipeline and stage values.
Questions about this workflow
Will every new ticket create a deal?
No. In your instruction, tell Notis to create a deal only when the ticket clearly expresses buying, upgrade, or expansion intent.
What does HubSpot need to create a deal?
The action supports batch deal creation and requires valid pipeline and deal stage values if you specify them. Use values that exist in your HubSpot account.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Zendesk to Hubspot. A trigger fires from one place; an action lands in another.
Zendesk triggers
Hubspot actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Add asset association
Associates an existing asset ('form', 'object list', or 'external web url') with a specified hubspot marketing campaign.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Add token to event template
Adds a new custom data token to an existing event template for a specified hubspot application, optionally populating a crm object property if objectpropertyname is provided.
New User Created
Triggered when a new user is created in Zendesk.
Archive email
Archives the hubspot email specified by `emailid` by moving it to the recycling bin, making it inaccessible unless restored.
New Zendesk Ticket
Triggers when a new ticket is created in a specified Zendesk view.
Archive a batch of emails by ID
Archives multiple hubspot crm emails by id; ids must exist as archiving is irreversible.
Archive a batch of quotes by id
Archives a batch of existing, non-archived quotes by their ids; this action is irreversible and useful for managing outdated or irrelevant quotes.
Archive batch of companies by id
Archives a batch of companies by their unique ids; targeted companies must exist, not be previously archived, and this api operation is irreversible.
Archive batch of contacts by id
Archives a batch of existing contacts by their hubspot crm ids, rendering them inactive; this action is irreversible via the api and requires manual restoration or a separate unarchive endpoint.
Archive batch of deals by id
Archives a batch of existing deals by their unique hubspot ids, removing them from active views and reports (soft delete); archived deals may be restorable.
Connect any two apps with Notis in the middle.
Zendesk and Hubspot, or any other combination from 1,000+ integrations.
When this happens · Trigger
Do this · Action
Save your first hour today.
7-day trial of any paid plan, with 20$ of usage included.
No card. Works with personal or business Hubspot.