Public API for entry automation (not just via IFTTT)
-
I don’t like to be forced to use IFTTT in order to create DayOne entries automatically. Please make the API public so that we can use other integrations using e. g. Make, Zapier, n8n, or just custom code.
-
I agree, same situation here.
Forcing users to use a specific integration service is not the way to go. -
Thanks for the feedback, @brsma & @jcdichant
We have added it to our ideas board for consideration!
-
i’m also interested in this. Is there any update here or a link to the idea board where this could get an up vote.
-
-
Adding my voice here to support a public API. If that does not fit the DO business model, then at least provide an API to those of us who subcribe to One Day (like me),
Thanks!! -
Hi @rspears1966,
We are currently working on a Zapier integration for Day One. Stay tuned for the release of that feature.
-
-
I’m sure this will be well received; but I hope this won’t be locked to Zapier. Those of us asking for an API option are doing so because we understand and build our own workflows. I, personally, use n8n. Thanks again for the response and I will keep an eye out for the announcement.
-
+1.
Zapier is a nice platform, but more and more expensive and complex to do basic things like sending anything to a journal.
An API allowing any automation service would be much more appreciated and convenient.
BTW, also using n8n on my private server, if this helps. -
+1 to the last two comments. Zapier is yet another closed service. An API would allow to connect _any_ tool (including Zapier). I want that freedom.
As a product management executive I understand why you might prioritise less technical offerings for a big part of your user base. Yet, I’d really appreciate if you also supported more technically inclined users at building their own integrations and workflows. Even more so with the current AI coding and workflow tools making that route already much more accessible than previously.
Now imagine if we could not only do that but also share our solutions with the community. You would not only both gain product use insights and inspiring solutions from the long tail that your own product team would not have come up with or does not have the bandwidth to ship. You might also unlock further growth potential for DayOne – see e. g. Miro’s and Notion’s approach. -
Hi @brsma, @jcdichant, @rspears1966, and @centaurefox!
I logged all your requests for this feature! Thanks for your input. We appreciate it.
-
Totally agree with brsma, we are on the same page. The world of AI has unlocked a whole host of integration possibilities and much greater opportunities to increase the frequencies and quality of journaling entries through a range of activities and triggered by a range of applications.
We are also using n8n as an agency, and one thing I would say is that integrating with n8n and perhaps with Zapier to a lesser extent is a marketing boon for many platforms that show up in the n8n marketplace.
The n8n channels on YouTube have exploded over the past year, and I know of several startups that have received great traffic and awareness as well as new customers simply by being visible on the n8n marketplace and by making it easy for the ever increasing population of people who are automating things there.
So for you folks in product management for the Day One Journaling App, there is an opportunity here that I’m sure you should at least be considering from a visibility and marketing perspective. -
I’ve been using DayOne for a very long time and think I requested a public api feature almost 10 years ago and have periodically checked back in to see if its available. Definitely supportive of this feature – would love to have an api to use.
-
-
Thank you @juergenberkessel238406411, @codenutz, and @rml2000 – I have added your feedback to our internal feature request.
-
-
I would definitely like to add to this as well, please. Something when I’m looking for apps like this, having access to the API is really important,
Day One Forums 