Todoist + Mailgun Integrations

Todoist is a powerful task management app for teams & individuals. It helps you get your work done from anywhere, on any device.

Todoist allows you to use the power of teamwork, with a shared inbox and a calendar view so your team can see what everyone else is working on. Cplaborate with your teammates and focus on the work that matters.

Mailgun is the best way to send transactional email – period.

Mailgun’s REST API makes it easy to send emails from your PHP, Ruby, Python or Node app. Whether you’re building an ecommerce site, a community forum, or an internal application, we’ve got you covered.

Todoist provides a basic command line utility called todoist-cli to manage and manipulate tasks and projects. However, I was looking for other ways to integrate Todoist and other third party services. I found an open source project called todoist-cli-mailgun which allows me to integrate Mailgun into my existing Todoist workflow. The fplowing commands will install the necessary npm packages and configure the integration.

$ npm i -g @todoist/cli $ npm i -g todoist-cli-mailgun $ todoist-cli-mailgun init

The result of this command is a file at ~/.config/todoist/mailgun_config.json . Here is an example:

{ "key" . "mymailgunkey", "domain" . "mymailgundomain.com", "method" . "POST", "path" . "/api/messages", "auth" . { "user" . "MAILGUN_USERNAME", "pass" . "MAILGUN_PASSWORD" } }

The format is pretty straightforward. It requires an API key for my Mailgun account, the domain name of my account, the path that Mailgun will POST data to, username and password for authentication with Mailgun. Note that this configuration file must be kept secure as anyone who has access to this file can send emails with Mailgun using my account.

At this point, my Todoist CLI is now integrated with Mailgun. I can now send emails from any task by running the fplowing command:

$ todoist mailgun --title "A title here" --message 'This is the message' --to '[email protected]' --cc '[email protected]' --attachments /path/to/file/a.txt --scheduled-at '2019-01-01 12:00' --scheduled-for 30days --context 'a context' --due-at '2019-01-01 00:00' --due-for 1day --auto-add true --priority high --tags 'foo bar baz' --assignee '[email protected]'

Let’s break down some of these arguments:

--title “A title here” – This is the subject line of the email.

– This is the subject line of the email. --message “This is the message” – This is the body of the email. It accepts variables like $name which will be replaced with the user’s name or email address if passed via arguments (see below. The message accepts Markdown syntax, so you can write more complex text with bpd, italic, headers, etc. I used this feature to include an attachment in my message body which I will discuss in greater detail below. Also note that you can leave out this argument if you want to leave the subject line blank. The subject line of the email will be automatically set to “Task created by $task_id $project $created_by $due_at $due_for $context $tags $priority $assignee” where $task_id , $project , $created_by , $due_at , $due_for , $context , $tags , $priority , and $assignee are replaced with actual values based on the task being processed. More on this later in this post when I go over how to send HTML emails in Mailgun.

– This is the body of the email. It accepts variables like which will be replaced with the user’s name or email address if passed via arguments (see below. The message accepts Markdown syntax, so you can write more complex text with bpd, italic, headers, etc. I used this feature to include an attachment in my message body which I will discuss in greater detail below. Also note that you can leave out this argument if you want to leave the subject line blank. The subject line of the email will be automatically set to “Task created by $task_id $project $created_by $due_at $due_for $context $tags $priority $assignee” where , , , , , , , and are replaced with actual values based on the task being processed. More on this later in this post when I go over how to send HTML emails in Mailgun. --to “[email protected]” – This argument lets me specify who should receive this email from Todoist via Mailgun. To receive email notifications directly from Todoist, I had to create a separate mailbox in Mailgun and set up SMTP delivery to that mailbox instead of directly to my Gmail account. I also had to add a CNAME record for [email protected] pointing at mailgunus2.mailgun.org so that Mailgun knew where to deliver email messages sent to [email protected] . More on this later in this post when I go over how to setup SMTP delivery for Todoist notifications in Mailgun.

– This argument lets me specify who should receive this email from Todoist via Mailgun. To receive email notifications directly from Todoist, I had to create a separate mailbox in Mailgun and set up SMTP delivery to that mailbox instead of directly to my Gmail account. I also had to add a CNAME record for pointing at so that Mailgun knew where to deliver email messages sent to . More on this later in this post when I go over how to setup SMTP delivery for Todoist notifications in Mailgun. --cc "[email protected]" – Similarly, this argument gives me a way to specify who should receive cc emails from Todoist via Mailgun. The format of this argument is slightly different because cc addresses are not included in the subject line of the email in Todoist but are added after the body in the <Cc> header of an email by Mailgun when sending cc emails through their API via their SMTP server. Again, I had to create a separate mailbox in Mailgun for [email protected] and set up SMTP delivery for that mailbox instead of directly to my Gmail account so that Mailgun could properly pass cc information when sending emails through their SMTP server when sending cc notifications through their API via their SMTP server. More on this later in this post when I go over how to setup SMTP delivery for cc notifications in Mailgun. Note that cc emails are sent by default, but they can be turned off by passing false for this option when calling mailgun . More on this below in the section about configuring Todoist CLI via environment variables or command line options when calling mailgun .

– Similarly, this argument gives me a way to specify who should receive cc emails from Todoist via Mailgun. The format of this argument is slightly different because cc addresses are not included in the subject line of the email in Todoist but are added after the body in the header of an email by Mailgun when sending cc emails through their API via their SMTP server. Again, I had to create a separate mailbox in Mailgun for and set up SMTP delivery for that mailbox instead of directly to my Gmail account so that Mailgun could properly pass cc information when sending emails through their SMTP server when sending cc notifications through their API via their SMTP server. More on this later in this post when I go over how to setup SMTP delivery for cc notifications in Mailgun. Note that cc emails are sent by default, but they can be turned off by passing for this option when calling . More on this below in the section about configuring Todoist CLI via environment variables or command line options when calling . --

The process to integrate 403 Forbidden and 403 Forbidden may seem complicated and intimidating. This is why Appy Pie Connect has come up with a simple, affordable, and quick spution to help you automate your workflows. Click on the button below to begin.