Can't locate services tickets via Zapier

Hello,

My account is our Hubspot superuser and our Zapier superuser. We have just upgraded to Services Pro from Services Starter, so there are lots of tickets in our system.

I need to create a Zap that triggers when a customer support ticket is raised by a customer. However when Zapier searches for ticket records it can only find one: a fake record that I created to see if this thing was working. Before I created the fake ticket in Hubspot, it was returning no records at all.

As I say, there are 100s of tickets in our Hubspot. Does anyone know why the only record I’ve been able to find is the fake one I made?

Thank you.

Nigel

Hi @nigeld27 :waving_hand:

I think the community will need a little more information in order to offer support here. Specifically, can you share a little more information about the Zap you have configured (e.g. what’s your trigger and subsequent actions)? Also, when you say “when Zapier searches for ticket records”, what exactly is the configuration (e.g. HubSpot’s standard “Find Ticket” Zapier action, or maybe custom code interacting directly with HubSpot’s API)?

Looking forward to your response.

Hi,
Ok sure if you think it will help.
- The Zap is to create a task in Scoro, which is our time tracking tool, for the team to log their time solving a ticket.
- As it stands, the only data points I know I must export are the ticket name to be used as the task name, and the company name to map it to the right customer in Scoro.
- If I can do this to work, I would then try and create a new Zap to close a task when the ticket is closed.
- I have not done any Scoro Actions in Zapier because I have no real ticket records to work with.
- As far as I can see, the only Zap triggers available are New Ticket and when I ticket is updated. I am using the New Ticket Trigger for this.
One other thing… I was trying to figure out why there are no ticket records being returned so I tried other Zaps. We get no returns on Company or Contact Updates but we do get returns on Form submissions. Therefore I do not think my issue is Ticket data specific.
Is there a latency in the records Zapier can find, ie it cannot find a test record if the ticket is older than 24h or something?

Hi @nigeld27 :waving_hand:

Thanks for the additional context.

There should be very little latency between data creation in HubSpot and subsequent invocation of Zapier triggers. Zapier triggers are generally webhook-based, so this should be nearly immediate in the great majority of cases.

Again, I’m struggling to understand what you mean by “there are no ticket records being returned” in Zapier. I’m guessing you mean you have a Zap enabled where the trigger is HubSpot > “New Ticket”. Then, when you create a new Ticket in HubSpot, the Zap doesn’t get executed -- is this correct? If not, please clarify.

Please let me know if you have any follow-up questions.

Thanks for continuing to try to help.
Maybe it is easier if I just use screenshots. I have created a new Zap from fresh for this:
[cid:1ffa8a8c-29d8-4f1e-8c3e-f294f9302803]
[cid:49e90c99-9eb3-4438-8523-b7400bfa2aa5]
[cid:bce9d1aa-6c3e-4d53-97bf-52d35d00c303]
[cid:fc22252d-b10f-43f7-b9e0-898f96f15b9d]
Hopefully this shows how Zapier cannot find a ticket.
For reference, our tickets (based on our Hubspot Starter Config) in Hubspot look like this. There was a ticket created yesterday.
[cid:6afa2e05-960e-4baf-a9eb-714179365e06]
Does this explain it better?

Hi @nigeld27 :waving_hand:

Unfortunately, I can’t see the screenshots you’ve shared. Can you try again please? If you haven’t already, try using the insert photos feature (the camera icon when making a post).

Let’s try again!

Hi @nigeld27 :waving_hand:

Thanks for sharing these screenshots.

Given the Zapier trigger you’re using is HubSpot > “New Ticket”, I’m nearly certain it’ll only be possible to test your Zaps with newly created Tickets. This is because this trigger is webhook-based (consistent with the great majority of Zapier triggers).

In short, Zapier won’t go searching through your HubSpot CRM looking for an example record to test with. It’ll only make available records that have triggered a webhook subscription since you configured the corresponding trigger.

I hope that proves helpful. Please let me know if you have any follow-up questions.

Hi Zach, I think this is correct although haven’t fully checked. I have marked as solved. I will update if it turns out I need more help.