Dynalist
ProductivityDynalist is the outliner for structured notes and lists. Agents read and edit documents and folders, insert and update items inside a document, capture to the inbox, upload files, and read account preferences.
What This Integration Enables
Dynalist is an outliner in the strict sense: the nesting is the content, not decoration on top of it. That makes it a good home for the documents an operations team actually maintains, the runbooks and quarterly plans and meeting outlines where the shape of the thing carries as much meaning as the words. It also makes it an awkward thing to automate carelessly, because a single call can move a subtree.
FlowRunner agents read and rebuild those trees, insert and edit items, capture into the inbox, upload files, and reconcile the outline against whatever system holds the work. Two properties of this API shape every flow worth building on it. Every failure arrives as an HTTP 200 with the real verdict in the body, so a flow that reads status codes will hand a refusal to the next step as though it were data. And the batch operations report their results as an array of bare booleans in the order sent, with no message attached to any of them. FlowRunner's connector raises on the single-change operations rather than returning a quiet false, which is why the batch calls are the ones that belong behind a person.
Without FlowRunner
With FlowRunner
Use Case Scenarios
-
The runbook that stays true to the tracker
A team keeps its operational runbooks as Dynalist outlines and its live work in ClickUp. Nightly, the agent calls Check Document Versions across the watched runbooks, which returns nothing but version numbers, and pulls only the documents whose numbers moved. For each changed outline it rebuilds the tree from the flat node list and its child identifiers, then compares the checked and unchecked items against the tracker's open work. Items ticked in the outline but still open in the tracker, and the reverse, become a reconciliation list posted to Slack. Nothing is rewritten automatically in either direction; the mismatch is the deliverable.
-
Capture that survives the meeting
Notes taken during a customer call arrive as text. The agent parses out the commitments, then uses Send To Inbox to put each one where the owner has configured their inbox to be, which is a per-account setting rather than a fixed location. When the account has no inbox configured, the call fails with a specific vendor code, and the flow treats that as a settings problem to report rather than an error to retry. Supporting material goes up with Upload File and comes back as a URL the agent links from the item, so the artifact and the commitment sit together. A summary lands in Notion for people who do not live in the outline.
-
Building a quarter's plan structure in one pass
At the start of a planning cycle, the agent assembles the whole skeleton offline: sections, workstreams, owners, and placeholder milestones. Create File makes the document in the right folder and returns the new identifier, and Apply Document Changes writes the entire outline in a single call rather than a hundred. That single call is also the one nobody can audit afterwards, because Dynalist answers a batch with positional booleans and no explanation, and it is counted against its own separate budget. So the agent renders the outline as a preview first, the planning lead reads it, and the batch runs after the approval rather than before it.
Human-in-Loop Highlight
Delete Item removes an item and everything nested underneath it, and Dynalist offers no undo through the API. Apply Document Changes can carry a whole set of those in one call, and it reports back an array of bare booleans in the order sent, with no message explaining any false. Together that is a write which can remove a branch and then cannot tell you which part of it went wrong. So a FlowRunner agent runs the individually reportable operations on its own, and stops before the batch: "This rewrite touches 47 items in the Q3 Plan document, including 6 deletions that would each take their children with them. Here is the affected branch as it stands and as it would read afterwards. Apply, or send back the deletions to review?" The planning lead approves the diff. The agent's judgment is in building the diff. The decision to spend a write nobody can reconstruct afterwards belongs to a person, which is what human-in-the-loop means when the system underneath keeps no history of its own.
Agent Capabilities
16 actionsDocuments and folders
5- List Files Returns every document and folder in the account along with the root folder's identifier. The response is a flat array in which a folder carries a list of child identifiers rather than nested records, so the tree is rebuilt from those identifiers.
- Create File Creates a document or a folder inside a parent folder. The new identifier comes back in the created array and is what the next call needs.
- Rename File Changes the title of a document or folder.
- Move File Moves a document or folder into another folder at a chosen position.
- Apply File Changes Sends several file-level changes in one call, for cases the named operations do not cover. The response is an array of booleans in the order sent, with no message per change.
Reading a document
2- Get Document Returns a document's whole outline together with its version number. The nodes come back flat, each carrying a list of child identifiers, and the tree is rebuilt starting from the node whose identifier is the document root.
- Check Document Versions Returns the current version number of several documents at once. It is the cheap way to find which documents moved since the last sync without reading any of them. A document that is missing or inaccessible is dropped from the answer rather than reported, so an absent identifier is not proof of no change.
Items inside a document
5- Insert Item Adds an item under a parent item. The new identifier comes back in the response, which is what a follow-up call needs to nest anything under it.
- Edit Item Changes an item's text, note, checked state, heading, or color. Sending only the checked state is how a flow ticks off a to-do without touching anything else about it.
- Move Item Moves an item, and everything nested under it, to a new parent and position.
- Delete Item Deletes an item and everything nested under it. Dynalist offers no undo through the API, which is why this operation sits behind the review gate rather than inside an unattended sweep.
- Apply Document Changes Sends several item changes to one document in a single call, which is how a whole outline is written at once. Dynalist counts these against a separate rate budget and answers with positional booleans and no message per change.
Inbox and files
2- Send To Inbox Adds an item to the account's inbox, wherever the user has configured that to be. It fails with a specific code when no inbox location is set, which is a settings problem rather than a malformed request.
- Upload File Uploads a file and returns a URL ready to be linked from an item. This is a paid-tier feature, and a free account is refused with a distinct code, as is an account over its upload quota.
Account preferences
2- Get Preference Reads one account preference. Inbox Location is the one that matters to a flow, because it answers where Send To Inbox will actually put things.
- Set Preference Sets one account preference, including where the inbox lives and whether new inbox items go to the top or the bottom.
Frequently Asked Questions
What can FlowRunner do with Dynalist?
FlowRunner agents can run List Files, Create File, and Rename File in Dynalist, plus 13 more actions.
Does connecting Dynalist to FlowRunner require OAuth?
No. Dynalist connects to FlowRunner with an API key, no OAuth flow required.
Can Dynalist trigger a FlowRunner workflow automatically?
Dynalist doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Other Productivity integrations
Start building with Dynalist
Free plan, no card required. Connect in minutes.