Resources · Make integration

DotSimple Make integrationAutomate DotSimple with Make.

Can Make handle your DotSimple posts, tags and files for you? The DotSimple Make integration gives you 19 modules: 4 triggers and 15 actions. This page is for marketers who know DotSimple and are new to Make: connect your account, then build a first scenario step by step.

Try the DotSimple integration on MakeSee the 19 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the DotSimple Make integration do for you?

The DotSimple Make integration links your DotSimple account to Make, a visual tool where you build a scenario (the automation itself) out of modules (one brick each: a trigger or an action). Make can spot new posts, tags, files and connected accounts in DotSimple, then create, schedule or delete content without you opening the app.

Content that starts somewhere else. A marketing team drafts ideas in a spreadsheet or a form. With the Create a Post module, each approved idea becomes a DotSimple post, and Schedule a Post or Add a Post to a Queue decides when it goes out. Nobody copies and pastes text between tools anymore.

A log of what gets published. Watch Posts picks up every new post, and the next module can send its details to a sheet, a chat channel or your reporting tool. Managers see the pipeline without asking for access to DotSimple.

Tidy media and tags. Upload a File sends visuals into DotSimple from a shared drive, while Watch New Tags and Delete a Tag help keep your tag list clean when several people label content.

Know the limit before you start: Make's own documentation for DotSimple is short, because little public information exists about the app. You discover the exact fields inside each module once your connection works. If you are still choosing a tool, the Make review and the n8n vs Make comparison lay out the options, and the Make training walks you through your first builds.

Connect

How do you connect DotSimple to Make?

  1. 01

    Add a DotSimple module

    In a new scenario, click the big +, search for DotSimple and pick any of its modules. Make then shows a field for the connection, meaning your DotSimple account linked to Make once and reused by every DotSimple module. Click Create a connection.

  2. 02

    Name it and authorize Make

    Give the connection a clear name if you like, such as the brand or client it belongs to. Then either approve Make on the DotSimple page that opens, or paste the key DotSimple gives you, depending on what the window asks for.

  3. 03

    Save and check the lists

    Click Save. Back in the module, Make can now read your DotSimple data, so the fields fill with choices you can pick from. If the lists stay empty, the connection did not go through and needs another try.

First scenario

Build your first scenario with DotSimple

GoalWhen a new idea is approved in the tool your team already uses, Make creates the matching post in DotSimple.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the + to add the first module. Pick the app where your ideas live, for example the sheet or form your team fills in, and connect it.

  2. 02

    Add Create a Post

    Click the + on the right of that first module, search for DotSimple and choose Create a Post. Select your DotSimple connection, or click Create a connection if this is your first DotSimple module.

  3. 03

    Map the text

    Fill the post fields by clicking into them and picking data from the first module, such as the approved text. Each item that moves between modules is a bundle: here, one idea becomes one post.

  4. 04

    Test with Run once

    Add a test idea in your source app, then click Run once. Make runs the scenario one time and shows the bundles each module received. Open DotSimple and check that the post looks right.

  5. 05

    Schedule and switch on

    Click the clock on the first module to set the scheduling: every 15 minutes by default. Then switch the scenario on. Each module run counts as one operation on your Make plan.

Triggers

Which DotSimple triggers start a scenario?

4 modules start a scenario when something happens in DotSimple. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by DotSimple as soon as it happens.

DotSimple1Watch Files

Watch Files

Scheduled trigger

In Make“Triggers when a new file is uploaded.”

Every file someone adds to DotSimple can kick off a scenario, so the rest of your stack learns about new media without anyone passing it along. The file arrives as one bundle that later modules can use.

How it fires
scheduled. Make checks DotSimple on the scenario's schedule, every 15 minutes by default, and picks up the files uploaded since the last check.
When to use it
when designers drop visuals into DotSimple and a teammate should get a message or a copy in the shared drive.
Watch out
nothing happens between two checks, so a file is never seen the second it lands.
DotSimple2Watch New Account Connections

Watch New Account Connections

Scheduled trigger

In Make“Triggers when a new account is connected.”

You get told when someone links a new account inside DotSimple, which helps an agency or a team keep track of the channels each client has plugged in. Each new account comes through as its own bundle.

How it fires
scheduled. Make asks DotSimple for new accounts on the scenario's schedule, not at the moment the account is added.
When to use it
when onboarding a client, to post a note in your team channel or add a row to your client tracker.
Watch out
on the Free plan, the shortest gap between two checks is 15 minutes.
DotSimple3Watch New Tags

Watch New Tags

Scheduled trigger

In Make“Triggers when a new tag is created.”

This trigger keeps other tools in sync with the tags your team invents in DotSimple, so campaign labels stay the same everywhere. Every tag created since the last check becomes one bundle.

How it fires
scheduled. Make polls DotSimple on the scenario's schedule and collects the tags created in between.
When to use it
when a new campaign tag should also appear in your planning sheet or reporting tool.
Watch out
pair it with Get a Tag only if you need more than the trigger already returns, since each extra module uses one more operation.
DotSimple4Watch Posts

Watch Posts

Scheduled trigger

In Make“Triggers when a new post is created.”

Your scenario starts from every post created in DotSimple, which makes it the natural base for a publishing log or an approval alert. Each new post travels as a bundle to the next module.

How it fires
scheduled. Make checks DotSimple for new posts on the scenario's schedule, every 15 minutes by default, and never instantly.
When to use it
when a manager wants a line in a sheet or a chat message each time the team drafts a post.
Watch out
it reacts to posts being created, not edited, so changes to an existing post will not start the scenario.
Modules

What can Make do in DotSimple?

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

DotSimple1

Add a Post to a Queue

Action

In Make“Adds a post to queue.”

A post lands in a DotSimple queue without you dragging it there, so a steady flow of content keeps going out in the order your queue decides.

When to use it
after an idea is approved and has no fixed date, so it simply joins the line.
Watch out
use Schedule a Post instead when the date matters.
DotSimple2

Create a Post

Action

In Make“creates a new post.”

Text from another app becomes a real DotSimple post, ready to review, schedule or queue. It is the module most scenarios start with on the action side.

When to use it
when drafts live in a sheet, a form or a notes tool and retyping them wastes your time.
Watch out
run a test with Run once, since every run creates a new post.
DotSimple3

Create a Tag

Action

In Make“Creates a new tag.”

With this module, a new label appears in DotSimple the moment your scenario decides it is needed, which saves someone from creating it by hand before tagging content.

When to use it
when a new campaign or client starts in your CRM or project tool.
Watch out
every run creates a tag, so test with Run once before you switch the scenario on.
DotSimple4

Delete a File

Action

In Make“Deletes a file by id.”

Old visuals disappear from DotSimple automatically, which keeps the media library light and stops outdated images from being reused by mistake.

When to use it
when a file is marked as retired in your drive or asset tracker.
Watch out
the module needs the file's ID, and a deletion cannot be undone from Make, so test on a dummy file.
DotSimple5

Delete a Post

Action

In Make“Deletes a post by id.”

One specific post gets removed from DotSimple by its ID, which lets a scenario pull content that should no longer go out.

When to use it
when a campaign is cancelled in your planning tool and its draft must go too.
Watch out
there is no undo from Make, so test it on a throwaway draft before you switch the scenario on.
DotSimple6

Delete a Tag

Action

In Make“Deletes a tag by id.”

Removing tags you no longer use keeps the DotSimple label list short and easier for the whole team to pick from.

When to use it
when a campaign closes and its tag should not be offered anymore.
Watch out
this module works on one tag at a time by its ID, so an earlier module, such as Watch New Tags, has to provide it.
DotSimple7

Deletes multiple posts

Action

In Make“Deletes multiple posts.”

Several DotSimple posts go away in a single step, instead of one module run per post, which is handy for clearing a batch of drafts.

When to use it
when a whole campaign is dropped and every post tied to it must be removed.
Watch out
a wrong selection wipes many posts at once, so test on a small set first.
DotSimple8

Get a File

Action

In Make“Retrieves a file by id”

Fetching one DotSimple file by its ID gives the next modules everything Make knows about it, so you can copy, share or log it elsewhere.

When to use it
when an earlier step only holds the file's ID and you need the file itself.
Watch out
on the Free plan, Make handles files up to 5 MB.
DotSimple9

Get an Account

Action

In Make“Retrieves an account by id.”

This action pulls the details of one connected account in DotSimple, which helps you label reports or messages with the right account instead of a bare ID.

When to use it
right after Watch New Account Connections, or when a post only carries an account ID.
Watch out
it reads one account per run and needs its ID.
DotSimple10

Get a Post

Action

In Make“Retrieves a post by id.”

You receive the full content of one DotSimple post from its ID, so a later module can archive it, send it for approval or copy it elsewhere.

When to use it
when your scenario starts from another app that only stores the post's ID.
Watch out
after Watch Posts it is often redundant and costs one more operation.
DotSimple11

Get a Tag

Action

In Make“Gets a tag by id.”

Looking up one tag by its ID tells the rest of your scenario what that label is called, which keeps reports and messages readable.

When to use it
when an earlier module only returns tag IDs and you need the readable label.
Watch out
the module works from the ID, so an earlier module has to provide it.
DotSimple12

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Anything the other modules miss can still be reached: this module calls any endpoint of the DotSimple API with the connection you already set up.

When to use it
when you need an action that none of the 15 listed actions covers.
Watch out
Make's DotSimple documentation is limited, so you must know the endpoint from DotSimple's side before you build the call.
DotSimple13

Schedule a Post

Action

In Make“Schedules a post.”

A post gets its publishing slot in DotSimple straight from your scenario, so dates set in a content calendar or a project tool are respected without manual work.

When to use it
when each piece of content has a fixed date decided elsewhere.
Watch out
run once with a test post to confirm the date lands as expected.
DotSimple14

Update a Post

Action

In Make“Updates a post.”

Changes made elsewhere reach the existing DotSimple post, so the version that goes out is always the latest one approved.

When to use it
when a reviewer edits the text in a shared doc or sheet after the post already exists.
Watch out
keep the post ID from Create a Post so this module knows which post to change.
DotSimple15

Upload a File

Action

In Make“Uploads a new file.”

Images and documents move into DotSimple on their own, ready to attach to posts, without anyone downloading and uploading them again.

When to use it
when your designer saves final visuals in a shared drive folder.
Watch out
on the Free plan, Make handles files up to 5 MB and 512 MB of data transfer.
Need help

Need help automating DotSimple with Make?

A person reads every message.

FAQ

Questions people ask about DotSimple and Make

01Is the DotSimple Make integration free?
Yes, DotSimple is a standard app in Make, so you can use it on the Free plan. That plan has real limits: 2 active scenarios, at least 15 minutes between two 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) lower the interval to 1 minute, remove the cap on active scenarios and allow 40 minutes of execution. Usage is counted in operations per month. Your DotSimple subscription is a separate matter.
02What do you need to connect DotSimple to Make?
You need a DotSimple account and a Make account. Make's documentation lists no specific prerequisites for DotSimple and gives no official connection steps, so you follow the standard flow: add a DotSimple module, click Create a connection, name it if you want, authorize Make or paste the key DotSimple provides, then save. Once saved, the connection is reused by every DotSimple module in your scenarios, so you only do this once per account.
03Do DotSimple triggers fire instantly in Make?
No. All 4 DotSimple triggers (Watch Files, Watch New Account Connections, Watch New Tags and Watch Posts) are scheduled. Make checks DotSimple on the scenario's schedule, which is every 15 minutes by default for a new scenario. On the Free plan the shortest gap is 15 minutes, while paid plans can go down to 1 minute. There is no instant trigger for DotSimple, so plan for a short delay between the event and the scenario run.
04What if a DotSimple module is missing in Make?
It depends on what you need. DotSimple has the Make an API Call module, which lets you call any endpoint of the DotSimple API with the same connection, so the 15 listed actions are not a hard ceiling. The catch is that Make's documentation for DotSimple is limited, because little public information exists about the app. You will need DotSimple's own API details before building that call. If the scenario itself fails, a troubleshooting guide helps you read the error.
05Should you use Make or n8n for DotSimple?
It depends on the tool you already run. On the Make side, DotSimple brings 19 ready modules, including 4 scheduled triggers and Make an API Call for anything else. Many apps also have an n8n node, so check whether DotSimple has one before you choose. Pick the platform your team already knows and maintains, then compare how each covers the posts, tags and files you actually automate. The n8n vs Make comparison on this site goes through the criteria in detail.
Same platform

Other docs you might need on this stack.

Browse all integrations