Skip to main content

Get Support
Have a question? Let's get you an answer!

How Do I...? Troubleshooting Code & Webhooks Developer Zone

Other Help Resources
Wait, there's more! Check out these Community sourced spaces for additional resources.

Zapier Help Center Hire an Expert

Learning Resources
All of our best learning resources can be found here.

Featured Articles Show & Tell Zapier's products AI Hub Zapier Tools Hub

Share your knowledge
Give back to the Community by sharing your automation wins and helping to answer questions.

Share your success See unanswered questions User Groups

Other Learning Resources
Some of our favorite additional ways to upskill your Zapier knowledge.

Zapier Learn Zapier Blog Zapier Webinars

Product Updates
Check out what is new and upcoming with Zapier with our regular product updates.

Product Updates

Early Access Program
Want to join Early Access? Learn more here.

I have a field in a Hubspot ticket that stores an appointment date for a contact. I have figured out how it would send a reminder 2 days before that date using a delay. 

How it works currently: 

  • Trigger: Ticket Property Change
  • Add delay based on date retrieved from ticket
  • Send message

My problem: If the contact decided to change their appointment date. The appointment date field in the ticket would change and trigger a new reminder to be sent. But the old reminder would also be sent. 

Is there a way to stop from the old reminder from being sent?

I have tried using Get Ticket  action after a delay expecting it would get the new appointment date. Adding a filter if the new appointment date is not equal to the old one, don’t continue. 

But it doesn’t retrieve new ticket updates when using Get Ticket so it doesn’t work. 

Any ideas how to solve this? 

Hi @adamm 

Perhaps explore using native HubSpot scheduling features: https://www.hubspot.com/products/sales/schedule-meeting

Hi @adamm,

 

Welcome to the Community.

 

In Zapier, delays and triggers can't be updated once set, even if the underlying data changes. A workaround involves using Zapier Storage and two Zaps. The first Zap stores the ticket ID and appointment date when a HubSpot ticket property changes. The second Zap sets a delay based on the new appointment date and checks if the stored date matches the current one. If they match, the message is sent; if not, it's skipped. This solution requires two Zaps, which count towards your task usage.

 

Let us know if this helps you jump-start your Zap. Thank you.

Terms & Conditions