Currently, the application relies on Zapier to notice when new matters have been created and create labels and entries in the spreadsheet for those matters. This could conceivably be implemented in a Zapier-esque way through google scripts.

The script is designed to be run at a certain interval. If the sequence of events is...

1. Script runs.
2. Email #1 Arrives.
3. Email #2 Arrives.
4. Email #2 is labelled
5. Script Runs
6. Email #1 is labelled.
7. Script Runs

Email #1 will never be archived. The reason for this is that the script uses the last time at which it archived an email to determine whether an email is "new." Once Email #2 is archived, only emails that arrived after the date on which Email #2 arrived will be considered "new."

Note that the same thing happens for emails that have been relabelled, or have had a second label attached, after a later-in-time email for that label has already been archived.

Note also that if Email #2 and Email #1 are both labelled, but in the wrong order, and are processed in the same running of the script, it will behave as expected. This is little comfort, though, because you won't necessarily know when the script is running.

If you can come up with a way of solving that problem without keeping a list of all emails in the spreadsheet, let me know. I haven't yet.

The work-around is to label emails in the order you receive them, and label them properly the first time. You can also use the clio gmail extension app to file individual emails to the appropriate matter.

Currently testing having the script make entries into a spreadsheet sheet for emails that should be added to clio communications. Idea is that Zapier zap on new spreadsheet row will be used to move them into Clio communications, and the script here will delete the sheet every time it runs.

So that there's a README

This would eliminate the need to use Zapier for the purpose of uploading the emails into communications. Instead, the app would directly communicate with Clio and input the data directly.

I will be branching this.