Tips on email productivity and workflow automation.

One year ago, we realized there is no good service to sort and automate inbound emails. Back in the day, IFTTT let you do some of it, but that feature was killed. There are plenty of solutions to send transactional emails, newsletters, or large volumes. Yet, the average Gmail inbox gets 150 emails a day, and users are still expected to manually process their inbox for hours.

Email has become a notification center for everything.

90%+ of emails are transactional or newsletters. This means your inbox is no longer the place where discussions happen. Today's inbox resemble the notification center on your phone: each message contains a single bit of information, and a deep link to an action (such as approving a Pull Request, or opening a comment). Unlike on your phone, you can't easily snooze, dismiss, turn off, have granular control over emails.

Mailscript provides developer tools to makes it easy to program email automations. We will first offer a CLI and API for developers (find out more in our docs).

How it works

  1. We give you a address. Once you create yourname@, you can also create aliases, like You can even use + or . like you would in Gmail. This means you can create an infinity of addresses, to use in your automations.
How alias creation looks like in the CLI

2. Every time an email arrives at this address, Mailscript will analyze the email headers, participants, body, and attachments. We make everything neatly available in a JSON object. You'd be surprised how few alternatives there are for an API to deal with inbound emails!

(We're also creating parsers for prolific email senders. Currently, we understand GitHub emails (Issues, PRs, Actions), with plans to add GSuite, AWS and more soon)

3. Using our CLI and our API, you can then start creating automations. Every automation in Mailscript consists of:

  • Triggers: Mailscript looks for everything in the email body and meta data. So you can set a trigger if a specific sender, multiple senders, an attachment or file type, specific words, email headers, time of day, or even if a certain amount of emails arrive within a time interval.
  • Actions: you can output to a webhook, receive local notifications on your device, receive an SMS, send an email. We're working on adding integrations (ex: Google Drive).

Examples of workflows

Mailscript automations are called Workflows. Trigger + Action = Workflow.

Let's say you want to create a workflow called Post GitHub build failures to Discord:

  • You could have any email that arrives at
  • Use the trigger "any GitHub build failure" (our API makes it easy to parse GitHub emails)
  • The action "post a message to Discord"

That's it! There are so many ways you can automate your email work with Mailscript:


  • Trigger: any email to
  • Alias to,

SMS notifications if new version:

  • Trigger: email from this address, and body has "version"
  • Action: Send me an SMS

Run local commands (use Mailscript as a local daemon):

  • Trigger: if I send myself an email
  • Action: run this local command

This means you can securely trigger code on a machine, without having to mess with SSH or making an API!

Get in touch 🙌

We think there's a lot of exciting use cases for Mailscript. Signups are open now and we'd love to hear what you think. Please drop us an email at, join our Discord or reach us on Twitter!