API
Workflowy does not yet have an official API available.
We definitely plan on building one, but it isn't at the top of our priorities and we don't have an estimate for when we'll do it.
However, there is an unofficial API written by one of our users in PHP:
-
Such endpoints do exist they just don't appear to be documented or officially supported. In addition to the php library mentioned by support there also appears to be a javascript library:
https://github.com/malcolmocean/opusfluxus
This library also has a command line interface for exporting the data which might be useful to you.
I was exploring integration with workflowy for personal project so started reverse engineering the data schema and dumped few sample responses into https://jvilk.com/MakeTypes/ to infer the schema and cleaning them up a bit. This may not be complete, but I have a fair bit of workflowy data so seems to have captured most things even sharing which I didn't even realized existed until I was reverse engineering this, super excited about sharing!
https://gist.github.com/kurtharriger/4fa6da3a28419f76099920c1c38ce94f
-
I've been a paying pro user since 2012. In the last few years I've come to find Zapier incredibly useful for automating important parts of my business and life workflows.
I've found recently that I'm very slowly switching more workflows out of Workflowy and into Trello, GitHub, Calendar, and even GMail just so I can avoid small bits of repeated work duplication.
I'd absolutely love it if Workflowy added Zapier support or at least a public-facing API. I'd love to keep as many of my important workflows as possible inside Workflowy.
-
You can add one more pro user to the +1 list for API service.
I would like:
- API integration via REST or GraphQL.
- Node.js SDK package.
How I can help:
- I would be happy paying more to unlock the feature. (It could be a separate service you could charge extra for.)
- I would help create and support the Node.js SDK for you.
https://www.linkedin.com/in/f1lt3r/
https://github.com/f1lt3r -
Hey guys, I'm a Pro user here too since 2016. But I just recently learned that there is a site that we can submit feature request.
Workflowy team should prioritize this next year. I'm starting to become a Voice Assistant developer and I'm imagining a wonderful future where just talking to my smart speaker/display, TVs, watch, etc. to brainstorm ideas and log my thoughts in my Workflowy account. It has been 3 years and nothing was delivered regarding the API...
I think the best way to do this is to deliver an MVP and then iterate. So what are the MVPs? Here's my suggestion:
- Ability to add new notes to the root node
- Ability to add new notes to a specific parent note
- Ability to add tag to the added note
- Ability to return all child notes of a specific parent note
Delivering those 4 features next year is an achievable goal. Workflowy is already in the cloud, adding another layer for the REST API would be a very simple thing to do.
-
Yes, i agree that API development for workflowy would be heavilly time comsuming and non trivial.
But still - having workflowy opened for automation would be an explosion of possibilities, and i cannot stop dreaming about having it ;)
Maybe some kind of crowdfunding this functionality would be a solution? Let users vote with their wallets! :)
-
Hi, I'm with Alistair. Please add an integration API for Workflowy!
I love this product and I'm not going anywhere, but I would love to be able to read/write/reogranize my lists via API.
Ever read/write/reorder would be amazing right now (nothing to do with moving items in and out of trees, just changing their order with siblings).
I pay for the paid version, and would even pay more just for this functionality!
-
Dan, correct. Although a server-side API is not off the table for the not-too-distant future, as I understand it.
Kay, why don't you join the Slack WorkFlowy User Group and chat to a couple of people who do have access to an (experimental) list. One of those being @rawbytz. Send me a DM here and I'll send you an invite to your email address to join the Slack group :-)
-
One of the difficulties with them building an API, is they have put so much of the essential logic into the front-end (you can pop the Developer Console and see how the everything works under the hood). Unwinding that ball of string would be non-trivial. So the cost of making such a large overhaul would have to make sense for a large enough base of users to make it financially viable. It's a small team, so I doubt it will happen.
-
During recent discussions about note-taking in a few discord servers I frequent I've been pushing workflowy pretty hard (been an avid user since 2012)... but am having a hard time handling the objection: why no api? Why no integrations?
I'd like an API for my own use as well... So, bump. Any developments here? I'd be interested in contributing to node module.
Please sign in to leave a comment.
Comments
59 comments