Add to Inbox via IFTTT


Ahh, I was looking for that! But I was looking for share not export or blueprint.

Here it is, - in the JSON tool you have to add your Dynalist API key.

The 15-minute cycle is annoying, but unless there’s some GMail web hook to trigger Integromat/IFTTT/Zapier/etc the only other choice is polling.

Make a kanban, trello or airtable like board or table based on tags

That’s the one thing really gets right. They show a little animation of it on the front page. Gmail inbox is just another to-do. And calendar is just another to-do. Dynalist is still better, but getting closer to functionality would be cool.

#30 is on my must try list.

To be honest though I tried Sortd and another Gmail overlaid organizer (but I can’t remember which other one) and neither one really worked for me. Besides the technical glitches that are inevitable when trying to skin something as complex as GMail I was also running to little quirks that made it just not work right.

It’s not clear to me whether is overlaid on top of GMail or it’s a totally separate service that pulls in your GMails?


@Schultzter thank you for sharing!


From my experience and understanding it’s a separate service that relies a lot on Google for storage and integration.

It can operate without having your Gmail open, that is.


So do you use Dynalist or or both?!

Because I was just poking around and it looks frakin’ cool!!! Maybe just because it’s shiny and new to me but WOW!

@Erica Two things that I would love to see in Dynalist from are

  1. integration with Google Contacts (dedicate the at-tags to be contacts); and
  2. like we’re discussing in this thread: tighter integration with GMail.

Dynalist already has integration with Google Calendar, so that’s perfect.

(And while I’m on the subject of features I would like to see: standard Markdown implementation)



I found this explanation of how was built: Serverless: Bootstrap your startup by only doing half of the work


I only use Dynalist. is too visually cluttered and inflexible about your style of doing things. Dynalist feels like a blank paper journal with just enough functionality and structure to be benefitial. feels like some software you need a 3 month community college course to figure out the esoteric quirks of it all.


Thanks for the input!

We’d love to integrate more closely with Google if it were easier… Google products are not very friendly to users and even less friendly to developers… :cry:


I tried following the IFTT recipe, but on the last line in body my {{Subject}} turns red and causes an error. I probably did something dumb :open_mouth:

Any help would be much appreciated!


Try this: Instead of typing {{Subject}} leave your caret there then click ingredients and click Subject. Also screenshot everything you did.


Thanks!! I don’t see the option for ‘Subject’ though, am I in the wrong menu? (I replaced my actual token with some random numbers).


You have it right. Click TextField. That’s the one you want.

You’re doing a Google Assistant IF which outputs a TextField (whatever you said after the trigger words)

I was doing an email IF which outputs a Subject.

The output of the IF becomes the input of the THEN but you can use literally anything that shows up in the ingredients, and it will scoot thru the pipeline to ur dynalist.

Email a note to dynalist using the subject works but adding notes in the body doesnt work

The only thing, that I get into my Dynalist inbox via IFTTT, is the subject of the email:

{“token”: “MY API KEY”, “index”: 0, “content”: “{{Subject}}”, “checked”: false }

When I use this extended code instead, nothing happens, besides that the activity log in IFTTT shows me, that the applet was successfully triggered:

{“token”: “MY API KEY”, “index”: 0, “content”: “{{Subject}}”, “note”: “{{Body}}”, “checked”: false }

Is anyone successfully using both; 1) content: Subject and 2) note: Body with Gmail > IFTTT > Dynalist?


I’ve tried without success we well.


It works fine from terminal so the API is working for simple text notes.

curl --header “Content-Type: application/json” --request POST --data “{“token”:“ToooooooooKeN”,“content”:“Im a task”,“note”:“Im a note”}”


Maybe there’s just too much crap in a IFTTT gmail body. Like it needs to be one line of ASCII to be safe. Who knows what it’s sending but the API is probably rejecting whatever it is.


I’m actually quite curious - what is the use case for e-mail add to inbox? Either I am at my machine with a web browser or on the go with the Quick Dynalist Android app - when would writing an email be faster?


Probably not faster, just more complete. Multiple itineraries and confirmations for travel plans are an obvious choice to simply forwatd into Dynalist rather than copy and paste information.

For me, I would forward emails related to a sales business I am a part of. Being able to take notes on the specific information in those emails, or track converations in a CRM style fashion is way more productive than bouncing between other apps.


The feature request was made before the API released and before quick dynalist app existed. People planned to jerryrig an API thru email, since it’s a universal share method. Now that an API was released, email is just a euphamism for anything you can get into IFTTT.


An IFTTT recipe works this way:

“token”: “TOKEN”,

Use the <<<*>>> brackets to escape the text content. IFTTT probably is grabbing some encoding or html in the email that is causing the failure. I just set this up for a handful of emails with success.