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:
-
I read this thread with a sinking heart. I know it can be chaos in SW development, but a five year thread that says it will go on the roadmap then later says there is no roadmap gives no faith that this feature will ever land, if it's even really intended to build it. Maybe stakeholders are worried about losing their moat if WF becomes more open.
I'm a long time paid user and loved the simplicity of WF before dates, coloured tags, to-do and paragraphs and boards. THIS WHOLE TIME I have been missing the ability to extract data in an open way, and to implement my own forwarding mechanisms between bullets, in other words, a client- or server-side API for walking the tree, read, insert, delete bullets, and create mirrors. -
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.
-
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
-
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 -
[ChatGPT generated] Out of Office Reply: The Mysterious Odyssey of the Workflowy Team
Hello,
Thank you for contacting the Workflowy team. We regret to inform you that we are currently unable to respond to your queries due to a series of extraordinary and unexpected events that have unfolded in rapid succession.
It all started when we were unexpectedly recruited by a notorious but surprisingly organized drug kingpin. He admired our expertise in structuring data and enlisted our help to organize his empire. Just as we were planning our escape, something incredible happened – we discovered our latent lizard people heritage, which required us to adapt to a new lifestyle, mainly consisting of sunbathing on warm rocks to maintain our energy levels. This, as you can imagine, severely limited our productive hours.
However, our lizard basking was rudely interrupted when a band of surprisingly articulate and angry orphans, who had apparently been following the kingpin, mistakenly identified us as part of his empire. In a bizarre turn of events, they relieved us of our electronic devices, thinking they were treasure maps.
We’re currently navigating this complex situation, trying to balance our newfound lizard identities, negotiate with the orphans, and somehow escape the clutches of the drug lord. This has, understandably, delayed our work on the API – and everything else, for that matter.
As your patience wears thinner than our chance of a speedy resolution, we ask for your continued understanding. Rest assured, this experience will greatly enrich the depth of our organizational tools, assuming we make it back to civilization with our newfound knowledge and devices.
In the meantime, we recommend seeking alternative organizational tools or perhaps joining a sunbathing club – it’s quite rejuvenating.
Sincerely,
Not The Workflowy Team
-
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! :)
-
We’re currently navigating this complex situation, trying to balance our newfound lizard identities, negotiate with the orphans, and somehow escape the clutches of the drug lord. This has, understandably, delayed our work on the API – and everything else, for that matter.
Oh my GOD.
Someone close down the topic. Nothing will ever top this response.
Please sign in to leave a comment.
Comments
92 comments