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 use Smart Views in Close CRM (they are like standing search queries which show Leads/Contacts matching certain filters, e.g. emailed me yesterday - the list of contacts matching the filters changes dynamically).

Objective: I want to send the list of leads for each ‘smart view’ to Hubspot and tag each lead with a field identifying the smart field it is in.  e.g. I have a smart view: Leads who emailed me yesterday.  In Hubspot I have a field “Smart View” which would show “Leads who emailed me yesterday”.

Work Thus far:
**Zapier for Close has an exact trigger for this - “New Lead in Search Query / Smart View in Close” which unfortunately only seems to work some of the time.  The test cases always work, and I’ve been able to trigger it a few times, but often it does not trigger.

I assume this is because of how Close updates the smart views OR is related to timing in some way.  I’m not sure, but I cannot figure out what the cases are where it does or does not trigger.  Zapier has a 15m polling clock I believe also which may be complicating this.

But I imagine this should be possible because it’s quite simple AND because Zapier has a trigger built exactly for this.

If anyone has experience with this Close Trigger OR perhaps some way to do this more simply I haven’t thought of, would GREATLY appreciate any advice!

Thanks
 

 

 

Ok solved this problem in a rather radically different way but which is more robust - will post solution.

Hi @Orionxanomaly1138,

That's fantastic news! I'm really happy to hear that you managed to solve the problem.

If it's not too much trouble, would you mind sharing the solution you came up with? It would be incredibly helpful for our other amazing Community members who might encounter a similar issue.

Thank you! 😊

Hi @Orionxanomaly1138 

I have the same issue. When I test the task, it works perfect, but when it runs it seems like the trigger never gets activated.

How did you manage to fix this or work around it? This is very important to me.

 

Thank you!!!

Hi there @frankenstein2199,

I did some digging into our notes, and it seems like if more than 100 records exist in the Smart View, and an "older" lead is added to the Smart View, it will not trigger as the view is sorted by lead date_create descending. This also means if your lead comes into/goes out of the Smart View a couple of times, the Zap could trigger only once.

This is a polling trigger so there is no workaround for this - longer term it will be modified into a webhook trigger to alleviate this behaviour.

From Close: There is no "fix" for this at the moment, apart from ensuring your Smart View contains max ~100 leads if new leads that will come into this Smart View will be older than 100 newest ones already in there.

Hopefully, this helps.

Reply


Terms & Conditions