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â,
â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.
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
If you know how to use terminal try to add something to dynalist from there as a test. If you dont have curl installed you can also use google colab website to run it if you add a ! to the front of curl
curl --header "Content-Type: application/json" --request POST --data "{\"token\":\"BoOtYbOoTy\",\"content\":\"blah\"}" https://dynalist.io/api/v1/inbox/add
I have tried every method suggested. No luck! After entering content=textfield i couldnât save the applet at all!
I am sure i have entered all parameters right. Iâll try with the terminal. Thanks for all the help.
As long as that is the email registered to the IFTTT account. Is that the problem?
Robert youâre leaving out info. Screen shot the whole ifttt receipt. Whatâs your trigger? If your trigger is âemailâ then you are sending an email to a @ifttt.com address. It doesnât matter where it comes from. If your trigger is âGmailâ then you log into your Gmail. If your trigger is Google Assistant then nowhere is email used.
Iâm sorry, George. Youâre right. There is another thread floating around about sending emails into Dynalist. This one is kind of a hodge podge of a few choices. Iâve been mixing the two of them up so I apologize if Iâm leading anyone astray.
Sorry about the delayed reponse.
@BigChungus I have attached screenshots of my current setup, but note that I have tried all other suggestions as well, and none work.
The trigger is email, and itâs the one registered to dynalist. The token is accurate.
I am giving up on this for now,since I donât use this this feature much, I am replying mostly to thank you guys for assisting,
and in case someone else could use this info to troubleshoot.
ok, just in case you ever come back to it - maybe the IF side (the part not screenshotted) is to blame. Try a different THAN (not dynalist). Thatâd be the next troubleshooting step. Maybe IFTTT isnt even processing your email. You whitelisted which email its coming from? I forget how the email IF works.
Use application/json instead of plain text