Mocy

Hmm, sounds like an interesting idea but I do may want to focus on Gmail native actions at the moment. Do you have a ready to share repo I could...

That sounds useful. Just a reminder that you are the contributor so you could write and push. If you'd like to some input on the change, then create a pull...

I don't have a good answer for now. But I imagine that it could only be resolved if Gmail supports it, or there is some better way to intercept into...

Yes, it process the entire thread. See [Processor.ts](https://github.com/ranmocy/gmail-automata/blob/master/Processor.ts). The script itself doesn't have any storage, so it rely on email data to keep tracing. So it uses processed/unprocessed label to...

So you have two rules, A targets CI message, B targets comment message. A has action ARCHIVE, B has action INBOX. I think you could move A before B (with...

Updated in the master sheet to add "next action" field.

Not sure how much can be automated, but Sheet has API to manipulate a given sheet. However maybe not possible to create one since the script needs to be bundled...

It may due to the second Gmail filter: ``` Matches: from:([email protected]) to:([email protected]) Do this: Apply label "0unprocessed" ``` My idea was since the email is sent to you directly, it's...

That sounds reasonable. Notice that the script processes by thread, so I think it's possible to retrieve the information. But it may require some change around how action is applied....

Related to forwarding an email #33. I think we could provide an generic "send_email" action. Idea of syntax could be a list of actions: ``` (forward-to "[email protected]") / (reply-to (all/default/sender))...