I only use Dynalist. Moo.do 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. Moo.do 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… 
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 
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.
1 Like
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?
1 Like
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”}” https://dynalist.io/api/v1/inbox/add
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.
2 Likes
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.
1 Like
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.
1 Like
An IFTTT recipe works this way:
{
“token”: “TOKEN”,
“content”:"<<<{{Subject}}>>>",
“note”:"<<<{{Body}}>>>"
}
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.
1 Like
Anyone tried making this into an IFTTT widget?
Replying to keith - Nope. This doesn’t work either. The applet runs but nothing shows up in inbox even for simple text emails.
I’ve done it a number of times, Robert, both in IFTTT and Zapier. If you’re using IFTTT, make sure you use THREE <<<>>> not just TWO <<>>.
I did 
Here is the ‘body’ section pasted exactly.
{“token”:“stringofchar”,“content”:"<<<SUBJECTINGREDIENT>>>"}
Am i missing something?
You’re using the wrong quotes symbol. Not sure it matters to dynalist, but good habit to only use " not ”.
Also this thing works for you right?
{
“token”: “TOKEN”,
“content”:"<<<{{Subject}}>>>",
“note”:"<<<{{Body}}>>>"
}
Braces {} around Subject?
API token is copied correctly?
Inbox in DL is set properly?
Otherwise, I dunno Robert. Sorry
