How do you handle getting only new items/deduplicating your APIs/services?

Announcements
#1

Hi everyone,

We’re currently working on a new feature in n8n that will allow you to only get new items from your APIs/services. This means that you won’t have to worry about duplicates or missing items when running your workflows on a schedule.

We’d love to get your feedback on this! Here are a few questions to get the conversation started:

  • How do you currently handle getting only new items from your APIs/services?
  • What are some of the challenges you’ve faced with this?
  • How would this new feature help you and your workflows?

I’m excited to hear your thoughts!

Thanks, Nik

3 Likes
#2

Hi Nik,

Firstly, thank you for your work on this. Here are my 2 cents:

  • I’ve explored few options with static data, grabbing the last ran execution’s webhook input etc but found the solution with state-machine community node.
  • The need to setup an external service (Redis) or any other method could incur additional costs in general.
  • Having a native and maintained resolution to this problem without any extra dependencies would be amazing to say the least.