Resources · Make integration

Dynalist Make integrationAutomate Dynalist with Make.

Can Make keep your Dynalist outlines up to date without copy and paste? Yes. The Dynalist Make integration offers 14 modules, 12 actions and 2 searches, but no trigger. This guide is for people who already live in Dynalist and walks you from the connection to a first working scenario.

Try the Dynalist integration on MakeSee the 14 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the Dynalist Make integration let you automate?

The Dynalist Make integration links your Dynalist account to Make, a no-code tool where you build a scenario: a chain of modules, each one a single step such as an action or a search. With it, Make can file items in your inbox, rename or move documents and folders, and read an outline so another app can use it.

Capture ideas that arrive elsewhere. Send to Inbox drops a new item into your Dynalist inbox whenever another app hands Make something worth keeping, such as a form answer or a support request. Your outline becomes the one place where loose notes land.

Keep the tree tidy. Move a Document and Move a Folder reorganize your structure when a project changes status, while Edit a Document renames a file so its title matches the project name in your other tools.

Reuse what you already wrote. Get the Content of a Document reads an outline so the next module can send it somewhere else, and Insert Content to a Document adds new nodes to an existing document, for example the preparation steps of a new order.

What Make does not do here: Dynalist has no trigger, so nothing starts the moment you edit a node. A scenario runs on its schedule or after another app's trigger. File uploads also require a Dynalist Pro account. If you are weighing both tools, the n8n vs Make comparison sets them side by side, Make pricing explains how credits work, and the Make training covers the editor from scratch.

Connect

How do you connect Dynalist to Make?

  1. 01

    Copy your API key from Dynalist

    Log in to Dynalist and open the developer section. The page displays your API key, a secret token that lets Make act on your account. Copy it and keep it private, the way you would treat a password.

  2. 02

    Add a Dynalist module and create the connection

    In Make, add any Dynalist module to your scenario and click Create a connection. A connection is your Dynalist account linked to Make once, then reused by every Dynalist module. The Connection name field is optional, yet a clear name helps later.

  3. 03

    Paste the key and save

    Enter the API key you copied, or follow the instructions Make shows on screen, then save. Once the connection exists, Make can list what it reads from your Dynalist account while you fill in a module.

First scenario

Your first scenario: send new requests to your Dynalist inbox

GoalWhen a new entry arrives in another app, Make sends it to your Dynalist inbox as a new item.

  1. 01

    Create the scenario

    Open the Scenarios page in Make, create a new scenario and click the + in the middle of the editor. This first bubble is where the whole flow starts.

  2. 02

    Pick the app where requests arrive

    Dynalist has no trigger, so choose the app that receives your requests, a form tool for instance, and select its trigger. Each new entry becomes a bundle, one item passed on to the next module.

  3. 03

    Add Send to Inbox

    Click the + on the right of that module, search for Dynalist and choose Send to Inbox. Create the connection with your API key if it does not exist yet.

  4. 04

    Map the data from the first module

    Fill in Send to Inbox with data from the previous module, such as the request subject and the sender name, so each entry reaches your inbox with enough context to act on.

  5. 05

    Test with Run once

    Click Run once, then send a test entry in the other app. Open the bundles each module received and check that the new item shows up in your Dynalist inbox.

  6. 06

    Schedule and switch it on

    Set the schedule on the first module; a new scenario runs every 15 minutes by default. Switch the scenario on, and new entries reach your inbox with no manual copying.

Modules

What each Dynalist module does in Make

Dynalist gives you 14 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Dynalist1

Delete the Content of a Document

Action

In Make“Deletes the content of a specific document.”

You get an empty outline back: this module wipes content out of a document you choose, which is what you need when a page must start fresh before new items arrive.

When to use it
you keep one document as a running checklist per client and want it cleared once the job is closed.
Watch out
nothing among the Dynalist modules restores what was deleted, so try the scenario with Run once on a test document before touching a real one.
Dynalist2

Edit a Document

Action

In Make“Edits the title of a specific document.”

Your document titles stay in step with the rest of your stack, because the scenario renames a document for you. Only the title changes; the nodes inside stay as they are.

When to use it
a deal moves to a new stage in your CRM and the matching Dynalist document should carry the new label.
Watch out
to change what is written inside the document, pick Edit the Content of a Document instead.
Dynalist3

Edit a Folder

Action

In Make“Edits the title of a specific folder.”

Folder names follow the real world with this one: the scenario renames a folder so your Dynalist tree mirrors how clients and projects are called elsewhere.

When to use it
a client changes its company name and you want its folder to follow without opening Dynalist.
Watch out
the module has to know which folder to rename, so place List Folders before it when the folder is not always the same.
Dynalist4

Edit the Content of a Document

Action

In Make“Edits the content of a specific document.”

Text already sitting in a document gets corrected or updated in place, rather than piling new lines underneath the old ones.

When to use it
a task status changes in your project tool and the matching line in Dynalist should show the update.
Watch out
run Get the Content of a Document earlier in the scenario to see the current nodes, then point the edit at the one you mean to change.
Dynalist5

Get the Content of a Document

Action

In Make“Fetches the content of a specific document.”

Your outline turns into data the next modules can use: this module reads a document so a scenario can email it, copy it into another tool or check a node before editing it.

When to use it
a meeting ends and the agenda written in Dynalist should reach the team chat.
Watch out
the module only reads; nothing changes in Dynalist until an edit or insert module follows it.
Dynalist6

Insert Content to a Document

Action

In Make“Inserts content to a specific document.”

An outline you already use can grow on its own, since this module adds new nodes inside an existing document instead of creating a fresh one.

When to use it
a new order comes in and its preparation steps should appear as items in your fulfillment document.
Watch out
for quick capture with no target document in mind, Send to Inbox is simpler; Insert fits when the destination is known.
Dynalist7

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Whatever the other modules leave out stays within reach: this module calls any endpoint of the Dynalist API, using the connection you already set up.

When to use it
you need a Dynalist API feature that has no dedicated module in this list.
Watch out
you write the request yourself, so keep the Dynalist API reference open and check each response with Run once before switching the scenario on.
Dynalist8

Move a Document

Action

In Make“Moves a specific document under another folder.”

Documents change folders without you dragging them around: the module places a chosen document under another folder of your tree.

When to use it
a project is marked as finished in your task tool and its Dynalist document should leave the active folder for the archive.
Watch out
Make needs both the document and the destination folder; List Documents and List Folders provide them when they vary from one run to the next.
Dynalist9

Move a Folder

Action

In Make“Moves a specific folder under another folder.”

Reorganizing at folder level spares you from moving documents one by one, because this module places a chosen folder under another folder.

When to use it
a client leaves your active list and its folder belongs under a past clients folder.
Watch out
check the target parent with Run once first; a folder dropped under the wrong parent is easy to lose in a deep tree.
Dynalist10

Move the Content of a Document

Action

In Make“Moves the content of a specific document.”

Items change position inside your outline without being retyped: this module moves content of a document from one spot to another.

When to use it
a task gets done in another tool and its line should drop into a done section rather than stay on top of the list.
Watch out
it works on content, not on the file itself; to relocate the whole document between folders, use Move a Document.
Dynalist11

Send to Inbox

Action

In Make“Sends a new item to your inbox location.”

The fastest capture Dynalist offers in Make: Send to Inbox creates a new item in your inbox location, with no document to pick first.

When to use it
ideas, requests or links arrive in another app and you want them waiting in one place for later sorting.
Watch out
items land in the inbox location of your Dynalist account, so check where it points before the first Run once.
Dynalist12

Upload a File

Action

In Make“Uploads a file.”

Files coming from other apps can end up in Dynalist, since this module uploads a file handed over by a previous module of the scenario.

When to use it
a client sends an attachment by email and you want a copy in Dynalist alongside the rest of that client's work.
Watch out
uploads need a Dynalist Pro account; on a free Dynalist plan, this is the one module to leave aside.
Dynalist13

List Documents

Search

In Make“Lists all documents.”

Every document comes back as its own bundle, which gives later modules something to act on, one document at a time.

When to use it
you do not know in advance which document to edit or move, and the scenario has to find it first.
Watch out
each bundle runs the following modules again, and every run of a module counts as an operation on your Make plan.
Dynalist14

List Folders

Search

In Make“Lists all folders.”

Your folder structure comes back as a list, and that is how a scenario finds the folder it needs for a move or a rename.

When to use it
before Move a Document or Edit a Folder, when the target folder changes from one run to the next.
Watch out
if nothing narrows the list down, every folder passes to the next module, which can rename or move more than you meant.
Need help

Need help automating Dynalist with Make?

A person reads every message.

FAQ

Dynalist and Make: common questions

01Is the Dynalist Make integration free?
Yes. Dynalist is a standard app, so its 14 modules are available on the Make Free plan. That plan allows 2 active scenarios, at least 15 minutes between scheduled runs, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) bring the interval down to 1 minute and lift the cap on active scenarios, with usage counted in credits per month. On the Dynalist side, Upload a File needs a Pro account, so that module is the exception if you use Dynalist for free.
02What is needed to connect Dynalist to Make?
An active Dynalist account and its API key. Log in to Dynalist, open the developer section and copy the key displayed there. In Make, add a Dynalist module, click Create a connection, give it a name if you like and paste the key. That single connection then serves every Dynalist module in your scenarios. If you plan to upload files, the account has to be on Dynalist Pro, since file upload is a paid feature. The Make documentation lists no other prerequisite for this app.
03Does Dynalist start Make scenarios in real time?
No, because Dynalist has no trigger module in Make, neither scheduled nor instant. A scenario that uses Dynalist starts in one of two ways. It can run on its own schedule, set on the clock of the first module: every 15 minutes by default, down to 1 minute on paid plans. Or it can open with another app's trigger, a new form answer for instance, and then call Dynalist modules. Changes you make inside Dynalist do not start anything by themselves.
04What if a Dynalist module is missing in Make?
Use Make an API Call. It reaches any endpoint of the Dynalist API with the connection you already have, so a feature without its own module is still available. You write the request yourself, which means reading the Dynalist API reference, and Run once lets you check the response before the scenario goes live. The other limit to keep in mind comes from Dynalist itself: file upload is reserved for Pro accounts. When a scenario fails for another reason, the Make troubleshooting guide on this site walks through the usual checks.
05Make or n8n for Dynalist?
It depends on where your automations already live. Make gives you 14 ready modules for Dynalist, a visual editor and Run once for testing each step. Many apps also have an n8n node, so if your team already runs its workflows in n8n, check whether Dynalist is covered there before adding a second tool. Neither choice changes what the Dynalist API allows. Weigh the modules you actually need, the tool your other scenarios run on, and who will maintain them over time.
Same platform

Other docs you might need on this stack.

Browse all integrations