Hi there @Visa Geeza,

Before we dig deeper into this, would you mind sharing a detailed screenshot of how your Zap is configured? Also, a screenshot of the “Action” section of your action step that shows all of its fields.

(view larger)

Please don't include personal information in the screenshot, or be sure blur out any personal information.

Thanks!

Hey Ken,

Thank you very much for your reply! Here you go:

Zap steps:

You don’t need to care about the previous steps, they are parsing emails, formatting text etc.

The idea is to: 12) create a document from template; 13) Append some formatted text from the previous steps; 14) Create a loop that runs how many times a keyword is found; 15) Lookup these keywords against a table in our GDrive that has additional info for each keyword; 16) Append that info if the keyword is found against the Excel table - HERE IS WHERE I WANT THIS DATA TO BE ADDED AS ROWS IN A TABLE. NOT A SEPARATE TABLE; 17) continue only if this is the last loop iteration; 18) Append some more text from the parsed email; 19) send an email to the sender from the parser; 20) delete the document that has been sent.

Here are screenshots of the action of the Append text steps, IDK why you need them since everything in the zap itself runs fine :)

Cheers!

Hi @Visa Geeza!

Hope you don’t mind me hopping in to see if I can lend a hand with this.

I wonder if it might be worth adding the different table rows data and HTML into a Digest and have the Zap release the digest on the last loop iteration, which would collate necessary table rows together. Then in the Google Docs action you’d select the “rows” digest before the closing of the surrounding table HTML tags.

You’d need a Append Entry and Schedule Digest action set to have a Frequency of Manual. In there you’d create the necessary table row HTML and data so that for each loop that runs a new set of table row HTML and data would be added to the digest.

Then, after the Filter action that checks whether it’s the last loop iteration that’s running, you’d have a Release Existing Digest action which would output the entire digest of all the table rows. Then in your Append Text to Document action you’d have the necessary closing HTML tags for the table and you’d select the output from the second digest action. For example:


You can learn more about how to use Digest by Zapier here: Compile data in a digest in Zaps

Do you think that approach could work for this? If I’ve misunderstood what you’re looking to do here or you run into any issues on that at all just let me know! 

Hey Sam,

Thank you so much for your answer! I was looking into Digest, but didn’t think it would support this. Will try and get back here with the result.

Thank you very much again!!!

Cheers!

Hey,

Thank you very much!!! It works great, except for one thing - the Digest doesn’t clear out when I run the Release Existing Digest action (I am only Testing). I saw that there is no way to delete a Digest automatically after using it and I don’t want to create new ones for each time this ZAP runs. Will it clear out in Run Mode and how can I clear it in Test Mode?

Thank you in advance and take a bow, Sam :)

You are most welcome, @Visa Geeza! 

When the Release Existing Digest action runs (while the Zap is switched on) it will then clear the entries in the digest so that the next time the Zap runs a new set of digest entries will be generated. 

To clear the digest when testing in the Zap Editor you can change the Title of the digest in the Append Entry and Schedule Digest action to generate a new digest. 

Hope that helps to clarify. Do let me know if I can assist with anything else - always happy to help! 

Perfect! Thank you again very, very much!

Glad I could help, @Visa Geeza!

Seems like you’re all set on this for now but please do feel free to reach back out to the Community again if you need any assistance in future. In the meantime, happy Zapping!