How to create a link or reference to a node already existing if I know the ID?
@anatoliy
@anatoliy it would be nice to have a property “tags”
Will definitely play with this! One comment right off the bat is the API doesn’t seem very RESTful. Would expect a schema more like: /items/{id}/children
1 Like
Is there any way get-item could include a count for the children that the item might have? Or, failing that, even just boolean indicating if it did/did not have children would be great. Then you wouldn’t have to try to get children with list-children before discovering that it didn’t have children. (i.e. one less operation)
1 Like
Is there a way to create a mirror node of an already existing node?
2 Likes
I often use WF as the single source of truth and build many integrations for it. On top of ‘opusfluxus’, I’ve written high-level wrapper functions.
The most commonly used methods are getItemsByTag and getLastItemByTag. The required items are pre-labeled with the necessary tags. This makes the system more flexible and dynamic compared to hardcoding IDs directly into the code.
And the often-used methods are addChildItem and updateItem.
In the ideal API for my integrations, I would like to have webhooks for adding/editing items.
1 Like
I have view access to some bullets from other users and have added the content to my Workflowy, but the API does not seem to work with those items. Is there a reason why items from other users with view access are not compatible with the API?
Hello Workfellas! I use an API for organizing my tasks like on Tweek. I work on the board view. Timestamp in child item designate in which parent item must be. The script works on CRON and analyzing items in each parent items and searching for timestamps. Parents items for examples is TODAY and TOMORROW, or THIS WEEK, NEXT WEEK etc. Every day CRON seggregate items and move it to suitable parent. For example: item in parent item TOMORROW, tomorrow will be in TODAY parent item.
But, every move trigger two API calls, create-item and delete-item… When item had a childs, then this operation require two API calls for each child. And it’s complicated logic, create-item parent, create-item child, create-item child etc, and next in reverse order delete-item, delete-item for move-like operation.
So, my request is - Do you have plan to make an endpoint for this spectfic operation, that move item with its childs? In the response I’d expect new Id’s of created items.
Someone need this apart from me? I think it will reduce API calls a lot.
And other question… What is happen with orphans items? When parent item has a childs, but were deleted via API delete-item call?
1 Like
I need some way to use /api/beta/create-item/ without the user having to specify the parent node. I want to let the user choose a default save location for new tasks, similar to how sending information from mobile to WorkFlowy works - to the inbox.
But ideally I want to avoid having to have my end user use the browser developer console to get the UUID of the bullet where they want to save new items.
Can we have this function call save to the user’s inbox if no parent UUID is specified?
1 Like
I think you would be helped if the edit-item API call would let us edit the parent_id, allowing us to move the item to another branch.
however upon testing this doesn’t work. https://beta.workflowy.com/api/beta/edit-item/
{“item_id”: “752168cb-9eb9-2272-7442-ba72beff0cd4”, “name”: “Test Task for Moving to other branch.”, “note”: “test note”, “parent_id”: “d6fae20a-1601-fdba-80ac-bf996a57c391”}
Interesting the API responds OK but doesn’t do anything with the parent_id parameter.
Would be cool indeed if we can pass a new parent_id on when editing an item. I can imagine it is trickier because in the background the priority field mustn’t match an already used priority field, but the Workflowy Dev Gods have also solved this issue in the UI somehow, so I think they can figure something out.
If we use the delete item API call, ALL the children will be deleted permanently as well. I just tested this. And I believe this is by design as it mirrors the behavior when the user deletes a bullet in the UI.
I am for sure not going to add any option to delete a bullet in my application, the user can go ahead and do destructive operations inside the workflowy UI 
2 Likes
not a coder, but would love to see capacity for pulling up random nodes
That’s easy. One first gets the full list, creates an index, and then uses a random function to get one of the indexes - then we launch a get-item API call to ensure we show the user the most recent details.
Thanks for this, it’s definitely appreciated! We only use the create-item endpoint at this point, but it is functioning exactly as we need, and is much quicker than our previous solution.
Any chance there were updates from the initial release regarding escaping of inputs?
I was able to do “workflowy native” dates on the beginning, but now they appear as text in all cases…
I notice the same with text formatting. I used <code> text </code> which since yesterday doesn’t work anymore.
It works the markdown format: text
No problem with dates so far…
How u input dates?
1 Like
First off, THANK YOU, for providing the API in it’s current state. It’s nearly transformed my workflow and my life! Couple requests I’d like to see:
- Add an optional “parent_id” param to “Update a node” to effectively provide “move to” functionality
- Add an optional “levels” param to “List nodes” that would also return n “levels” below the “parent_id” (default to 0, -1 for all, or 1+ to recurse so many levels). Totally understandable if only a few levels offered at first for performance reasons
- Add an optional “query” param to “List nodes” that would do the same as performing a search
This is a very important addition. I made a small webapp based on it. But how do I access images? I can access the nodes and their text notes. Images are very important as I use it to save screenshots.
4 Likes
I am not a programmer, so, I doubt I’ll be using the WF API myself any time soon. However, I thought it would be interesting to try using AI to explain all of Workflowy’s features and give AI a list of all the things the Workflowy API can do at the present time. Here is a link to a shared WF list of possibilities that AI generated that perhaps will spark some ideas for someone who can use the API: Potential uses for WorkFlowy API - WorkFlowy
Read back a node with “Workflowy dates” and see! 
I’m on my phone sorry!