Hi @Nagamanickam 

Good question.

As a possible alternative to building a custom Zap app integration for Freshsales, perhaps look into using Freshsales Workflows to fire a webhook.

Zap trigger: Webhook - Catch Hook

https://support.freshsales.io/en/support/solutions/articles/228946-how-to-use-workflows-with-webhooks-in-freshsales-

Hi @Troy Tessalone ,

Is it feasible to create a trigger in Zapier that fetches an updated record based on the time it was last updated?

@Nagamanickam 

Did you look into this help article?

As a possible alternative to building a custom Zap app integration for Freshsales, perhaps look into using Freshsales Workflows to fire a webhook.

Zap trigger: Webhook - Catch Hook

https://support.freshsales.io/en/support/solutions/articles/228946-how-to-use-workflows-with-webhooks-in-freshsales-

Hey @Nagamanickam , 

As Troy suggested, webhooks typically offer the best user experience for triggers that fire on updated records. 

However, this should also be possible with a polling trigger. 

As the doc you referenced notes, it’s super important that the ids returned in the trigger are unique to each update. Otherwise, if we just used the record’s standard id, for example, the record might get caught in deduplication and be ignored.

The most common way to give each id a unique value is to combine the record’s id and the timestamp of the update, as described in that doc. It sounds like you’re already doing this, correct?

If you’re already returning update-specific ids, then two other suggestions that come to mind are:

• If possible, pass a sorting parameter in the request
• Similarly, ensure that the response is sorted in descending order, with the most-recently-updated records returned first)

Hi @connorz ,

I already have knowledge about webhooks. We are developing this feature for all users, not just for paid users. However, we are not using a webhook because it requires payment. As I mentioned before, I built this feature following the documentation provided by Zapier.

Additionally, I have taken care of appending the update time to the ID. So, I believe the deduplication process will not miss any records.

Furthermore, I have implemented sorting, and the records are retrieved in descending order only.

Now, I would like to understand why the trigger is not pulling all the data when it's published.

Thanks,

Nagamanickam.

Hi @Nagamanickam,

Regarding...

I would like to understand why the trigger is not pulling all the data when it's published 

...when turning a Zap on, the Zap will make an initial poll. For records seen in the initial poll, Zapier will remember the ids and deduplicate against them in future polls. But it’s unlikely that the Zap would receive ALL existing records. 

Non-unique ids are usually the cause of Zaps failing to trigger on updated records, but it sounds like you’ve implemented the best practices already. 

With that in mind, it’s a bit difficult to say for sure what’s happening without looking at the logs. If you haven’t already done so, it might help to check out the requests in Monitoring.

Otherwise, please feel free to reach out to our Platform Support team, who will be glad to help investigate in detail: 

https://developer.zapier.com/contact