It works - I so far have email, Alexa, Google home, and Google watch sending to dynalist inbox.
You click make your own applet since there is no recipe since you have to paste your personal API key in.
Make an applet then click THIS and choose something like email or Google assistant or anything, then fill out the form, itâs straightforward.
Then it will let you click THAT and you search âWebhooksâ and thatâs the form I screenshotted. If you Google dynalist API documentation youâll find your API key, itâs a long string you copy and paste like fjg74jrbdowjtbf7tbrkaifbrj.
Try it, hopefully I described it well enough and you donât get stuck.
Aweome thank you for sharing that. If you guys are using IFTTT it would be awesome if you could recomment Daynalist as Service as well. Maybe it getâs added in the near future as ârealâ Service. (ifttt.com)
âIf Send trigger@applet.ifttt.com any email from [myemail]@gmail.com, then make a web requestâ and am using the API key as recommended, but nothing is coming through.
Yes, thatâs why I asked about the trigger previously. I had the âemailâ trigger originally and it wasnât working. The activity log is empty, even after sending to trigger@applet.ifttt.com.
I wonder if the issue is that my IFTTT email is different from the one associated with Dynalist. But I assume at that the API is all you really need for this.
Iâve check the details many times, but Iâm stumped by it doesnât work.
Focus on fixing that first. In the email trigger, it asks you what address to expect the message from. Check your sent folder that the email was TO: trigger@applet.ifttt.com FROM: that address you typed in the trigger
my IFTTT email is different from the one associated with Dynalist
Itâs fine if theyâre different. The trigger just looks at all the emails its getting and finds the one from the address you told it to watch out for.
OK. The thing is that I was sending it from the appropriate email address but in a different gmail account (Send mail asâŚ). If I log in under the same gmail account as I send the email address, it works. It must read the deep structure of the email to work out its originating address.
Now that I have it working, Iâve also created a trigger when I add a label to an Evernote note, which promises to enable a working system between the two.
Do you know if there is documentation about how to send information to the Dynalist note as well as the item?
Iâve added note as below:
{âtokenâ:"[MY API]",âcontentâ:"{{Subject}}",ânoteâ:"{{Body}}"}
When I send an email to the trigger with a Subject and Body, it appears successful in the Activity Log, but doesnât appear in the Inbox. Iâm interested to know if anyone has had more success with this.
It works more perfectly than I thought, it stripped the signature from the body of the email before adding it as a note to the item (the part starting with â and below).
I tried setting up an IFTTT trigger to add a task to my Dynalist Inbox every time I star an email in Gmail, but IFTTT is complaining thereâs a problem with Gmail service.
If find that IFTTT does not facilitate debugging and often wonder if the problem is my trigger or my action - like did I bugger up the Dynalist API call in this case but IFTTT reports it as a Gmail problem.
well first see if the number of times the trigger ran number is increasing by 1 every time you do the thing, you see the number?
to debug if it is the trigger or the action just change the action to something else, like add a row to google sheets with the variable instead, leave dynalist out entirely, then youâll know dynalist wasnt the reason
p.s. that is a clever idea to put starred emails in dynalist â can you send the url to email itself as a variable so the dynalist item is a hyperlink? I always kind of thought the moo.do integration with gmail was kind of cool, so your inbox is just tasks like any other, this might let dynalist have that same functionality, i.e. to send an email to ur task list u star then archive, so ur inbox is empty but its on your to-do list.
edit: you cannt get gmail email as url as a variable in IFTTT kind of ruins it.