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)?
Best answer by Troy Tessalone
Might be useful:
+12Hi
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.
+14Hi
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
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/issueIf I get you right,
Hi
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,
+12Yep 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
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.