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 am building a zap involving the digest step. It basically logs changes from an issue tracker for a weekly review.

However, there are quite a few duplicate entries at the end of the week which is to be expected, given the trigger setup (unfortunately there is no way around that).

Is it possible to remove duplicate entries from the digest before sending it to the next step (Slack in my case)?

Hi @ubuntudroid 

can you share screenshots of the zap that sends to slack? including the data? You may need code to remove the entries but it should be doable. 

Hi @ubuntudroid 

Try logging these in a GSheet or Airtable, then check against that log to determine if a new record should be created or if an existing record is found (e.g. Find else Create), before proceeding to be added to the Digest.

Hi @ubuntudroid 

can you share screenshots of the zap that sends to slack? including the data? You may need code to remove the entries but it should be doable. 

The digested data is just a simple list of URLs:

https://link/to/first/issue
https://link/to/second/issue
https://link/to/first/issue
https://link/to/third/issue

If I get you right, @GetUWired, you are suggesting a code step in between which takes care of deduplicating?

Hi @ubuntudroid 

Try logging these in a GSheet or Airtable, then check against that log to determine if a new record should be created or if an existing record is found (e.g. Find else Create), before proceeding to be added to the Digest.

That’s a good idea, @Troy Tessalone. I’m going to try this out if the code step proposed by @GetUWired doesn’t work for some reason, as I would prefer to not add another tool to the chain if possible.

@ubuntudroid 

Might be useful:

 

Yep and it looks like that article Troy shared is perfect! 

Sheets would be no code of course but would just work out okay as you would have to loop through everything returned from the digest ( sheets can only find/create 1 row at a time ) and then you’d have to figure out a way to get everyone back into 1 output or you’d end up sending multiple notifications to Slack.. 

Deduplication with @Troy Tessalone’s code step works great, exactly what I needed! Thanks both of you!

Terms & Conditions