Resources · Zapier integration

DotSimple Zapier integrationAutomate DotSimple with Zapier.

The DotSimple Zapier integration gives you 4 triggers, 9 actions and 4 searches. They cover the posts, media files, tags and connected social accounts of your DotSimple workspace, and every one of them works on the free plan of Zapier.

See the 17 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the DotSimple Zapier integration does for a social media team

The DotSimple Zapier integration plugs your DotSimple account, the app that schedules and publishes social posts across several networks, into Zapier, the tool that chains apps together without code. A post, a file or a tag appears in DotSimple, and Zapier answers with the step you set up once: queue it, schedule it, tag it, tidy it up.

Three outcomes justify the setup.

A queue that fills itself. New Post Created spots each new post with the status you chose, and Add a Post to Queue slots it into the publishing queue without anyone opening the calendar.

Media that turns into drafts. New File Uploaded notices every file added to the media library, and Create New Post opens a new post in response, so a copywriter has something to start from.

A library that stays clean. Delete Post, Delete File and Delete Tag remove what a campaign no longer needs, while Find Post or Find a File fetch the exact item first.

Now the honest part. All four triggers are polling triggers: none is instant. The four searches look up an item by its identifier, not by a word in its caption, so a Zap needs that identifier from an earlier step. And no operation reads your post statistics, even though DotSimple itself offers analytics. If reporting is the goal, Zapier will not deliver it here.

Before you commit, compare with the DotSimple Make integration. This page was checked on October 1, 2026 against version App203269CLIAPI@1.0.3.

Vocabulary

Zapier vocabulary in one minute

Eight words, and the rest of the page reads without a dictionary.

Zap
The automation you build on Zapier: one trigger, then one or more actions that run every time that trigger event happens.
Trigger
The event in DotSimple that starts the Zap, like a new post or a new file. Once the Zap is switched on, Zapier waits for it.
Action
What the Zap does once started: the step that writes into DotSimple for you, such as queueing, scheduling or deleting a post.
Task
The unit Zapier bills. One task is one action your Zap completes successfully, and your plan counts those.
Polling trigger
A trigger Zapier checks on a timer: it asks DotSimple for new items at a set interval and keeps only what it has not seen.
Instant trigger
A trigger the app reports itself, right when the event happens. DotSimple has none, so all four of its triggers poll.
Filter
A step that lets the Zap continue only when what arrived meets your condition, and stops it on the spot otherwise.
Search step
A step that looks up something already in an app, so the steps after it can use what it found. DotSimple has four.
Cost

What a DotSimple Zap costs you in tasks

Watching DotSimple is free. You pay, in tasks, only for actions that work.

  • Trigger checks0 tasks
  • Each successful action1 task
  • Free plan100 tasks a month
  • Premium appNo

The trigger never costs a task, however often Zapier checks. Every action that succeeds counts one task, so a Zap with three actions burns three times what a one-action Zap does, and a failed action is not counted. DotSimple is not a premium app: it runs on the free plan, with 100 tasks a month, unlimited Zaps and a check every 15 minutes. The real ceiling is the shape of the Zap. On the free plan a Zap is one trigger and one action. Add a second action, a filter or a search step and it becomes a multi-step Zap, which needs a paid plan.

Connect

Connect DotSimple to Zapier in three steps

  1. 01

    Open the Apps page

    In your Zapier account, open Apps and click + Add connection. You need a DotSimple account already: Zapier links an existing account, it never creates one for you.

  2. 02

    Pick DotSimple

    Type DotSimple in the search box of the dialog, select it, then click Add connection. A new tab opens on the DotSimple side, where the rest of the connection takes place.

  3. 03

    Sign in and allow access

    Log in to DotSimple in that tab and grant Zapier access to the account. Every Zap step that touches DotSimple will reuse this connection afterwards, so you do it once per account.

First Zap

Your first DotSimple Zap: from uploaded file to queued post

GoalEach time a designer uploads a visual to DotSimple, the Zap drafts a post around it and drops that post into the publishing queue.

  1. 01

    Build: pick the trigger

    Create a new Zap, choose DotSimple as the app and New File Uploaded as the event, then select the connection you made from the Apps page.

  2. 02

    Test the trigger

    Run the test. Zapier brings back the three most recent items of the account, so pick a real uploaded file to map the next steps on.

  3. 03

    Draft the post

    Add the Create New Post action and fill in the post. Leave its optional settings empty: the next step is the one that puts it in the queue.

  4. 04

    Queue it

    Add a second action, Add a Post to Queue, and map into Post UUID the identifier shown in the Create New Post test result. If that test shows none, the post cannot be queued this way. This second action makes the Zap multi-step, so it needs a paid plan.

  5. 05

    Test, then Publish

    Run each step once and check the result in DotSimple. When the draft sits in the queue as expected, click Publish to switch the Zap on.

Triggers

DotSimple triggers: what starts a Zap

4 events start a Zap when something happens in DotSimple. Zapier checks for them at the interval your plan allows.

1

New Account Connected

Polling trigger

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

Starts your Zap when a new social account gets connected to DotSimple. It marks the moment a channel becomes available for publishing.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one
When to use it
a client hands over access to a new brand profile, and the Zap creates a tag for it so posts can be sorted by channel from day one.
Watch out
accounts connected before the Zap was published are never picked up, so only new channels start it.
2

New File Uploaded

Polling trigger

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

Fires on every file added to your DotSimple media library. For a team where visuals come first and captions follow, this is the starting gun.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one
When to use it
your designer drops a finished carousel image, and the Zap opens a new post for the copywriter to write.
Watch out
never pair it with the Upload File action in the same Zap, or each upload the Zap makes will start it again.
3

New Post Created

Polling trigger

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

Reacts when a new post is created in DotSimple. You set a required Status when you configure it, which narrows the trigger to posts in that state.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one
When to use it
each post your social media manager saves gets added to the publishing queue automatically.
Watch out
a Zap that answers it with Create New Post sets itself off; pick the Status carefully, since the trigger sees each post only once.
4

New Tag Created

Polling trigger

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

Triggers whenever a tag is created in DotSimple. If your tags stand for campaigns or content pillars, this one follows how your calendar is organised.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one
When to use it
a new campaign tag appears, and the Zap opens a first post with Create New Post so the campaign never starts empty.
Watch out
combined with the Create New Tag action, it loops and drains your task count.
Actions

DotSimple actions: what a Zap can do in your account

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

1

Add a Post to Queue

Action

In Zapier“Adds a post to queue in the system.”

Puts an existing post into the DotSimple queue. The only required field is the Post UUID, which identifies the post to move.

When to use it
every post saved with the right status should wait its turn in the queue instead of sitting in drafts.
2

Create New Post

Action

In Zapier“Create a new post in the system.”

Creates a post in DotSimple. None of its settings is required; the editor shows them under the labels schedule, Schedule Now, Queue and Is Original, so try each one on a throwaway post before relying on it.

When to use it
a new visual lands in the library and your copywriter wants a fresh post opened for it.
Watch out
avoid it in a Zap started by New Post Created.
3

Create New Tag

Action

In Zapier“Creates a new tag in the system.”

Creates a tag with a name and a colour, both required. The colour is a hex code, such as #60a5fa.

When to use it
each newly connected account gets its own coloured tag, so the calendar shows at a glance which brand a post belongs to.
4

Delete File

Action

In Zapier“Deletes a file by id in the system.”

Takes a file out of the media library. The only required field is the Media UUID of that file.

When to use it
a visual that a client withdrew should leave the library so nobody reuses it by mistake.
Watch out
fetch the identifier first, with Find a File or a trigger.
5

Delete Post

Action

In Zapier“Deletes an account by id in the system.”

Removes a post from DotSimple. You give it the Post UUID of the post to remove, nothing else.

When to use it
a campaign is cancelled and its pending posts must disappear before they go out.
Watch out
the UUID must come from an earlier step, such as Find Post.
6

Delete Tag

Action

In Zapier“Deletes a tag by id in the system.”

Removes a tag. It asks for one thing only, the Tag UUID of the tag to remove.

When to use it
closing a campaign also clears its tag, so the tag list stays short for the next one.
Watch out
pair it with Find Tag when the identifier is not already in the Zap.
7

Schedule Post

Action

In Zapier“Schedules a specific post now in the system.”

Schedules a given post. It needs the Post UUID and the Post Now setting, both mandatory, to decide how the post goes out.

When to use it
a post approved by the client in another tool gets scheduled in DotSimple once approval lands.
8

Update Post

Action

In Zapier“Updates a post in the system.”

Changes an existing post. The optional settings of Create New Post come back under the same labels: schedule, Schedule Now, Queue and Is Original.

When to use it
a campaign date moves, and the Zap pushes the new schedule onto the post instead of someone editing it by hand.
9

Upload File

Action

In Zapier“Upload file from the system.”

Sends a file into your DotSimple media library, where it joins the visuals your team already works with.

When to use it
visuals approved elsewhere should land in DotSimple without anyone downloading and re-uploading them by hand.
Watch out
do not use it in a Zap triggered by New File Uploaded.
Searches

DotSimple searches: fetching an item before acting on it

4 search steps look for data that already exists in DotSimple, so a later step can use it.

A search step looks up something that already exists in DotSimple and hands it to the next steps. All four DotSimple searches work from an identifier, and none of them has a find-or-create variant. Searches sit at the bottom of the action event list, under their own SEARCH heading. Each one makes the Zap multi-step.

1

Find Account

Search

In Zapier“Finds an account by id in the system.”

Looks up a connected social account from its Account UUID, the one required field, and passes its details to the following steps.

When to use it
before posting for a client, confirm that the account a previous step points to still exists in DotSimple.
2

Find a File

Search

In Zapier“Finds a file by id in the system.”

Retrieves a file from the media library through its Media UUID, which is required.

When to use it
just before Delete File, so the Zap removes exactly the visual you meant and nothing else.
Watch out
it needs the identifier, not the file name.
3

Find Post

Search

In Zapier“Finds a post by id in the system.”

Fetches one post by its Post UUID, the single required field, so later steps can read or change it.

When to use it
before Update Post, to check the post an earlier step points to is still there before you change it.
4

Find Tag

Search

In Zapier“Finds a tag by id in the system.”

Returns a tag from its Tag UUID, which you must provide.

When to use it
a campaign-closing Zap first finds the campaign tag, then hands it to Delete Tag.
Watch out
searching by tag name is not offered; only the identifier works.

The three settings every search exposes

  1. Successful if no search results are found?
    Left on its default, a search that finds nothing stops the Zap there and the steps after it are skipped. Switch it on and the Zap carries on empty-handed.
  2. Create X if it doesn't exist yet?
    This box turns a search into find-or-create on apps that offer it. None of the four DotSimple searches has that variant, so a missing item is never created for you.
  3. If multiple search results are found?
    Three ways out when several items match: keep the first one, which is the default, stop the Zap, or pass all of them on at once.
When it breaks

When a DotSimple Zap breaks

Zapier lists no help article and no rate limit of its own for DotSimple. What breaks is what breaks on any Zapier app.

Four cases explain nearly every surprise. Two are design mistakes you can avoid today, two are Zapier behaviours to know before you trust a Zap with a client's publishing calendar. If a Zap still misbehaves, the Zapier troubleshooting guide takes it step by step.

  • Older posts and files are ignored

    A Zap only reacts to what happens after you publish it. Posts, files and tags that already existed are never picked up; moving that backlog is a separate job.

  • The Zap keeps restarting itself

    A Zap that writes where its own trigger watches restarts on its own output: Create New Post after New Post Created, Upload File after New File Uploaded. Tasks vanish fast.

  • A big batch is held back

    After a bulk import or a migration, a trigger can return a huge batch at once. Zapier's flood protection can hold it back instead of running every item.

  • The same post never runs twice

    Zapier remembers what it has already seen on a polling trigger, so one post or one file never starts the Zap a second time.
Need help

Need help automating DotSimple with Zapier?

A person reads every message.

FAQ

DotSimple Zapier integration: frequent questions

01Is the DotSimple Zapier integration free?
Yes, as long as the Zap has two steps. DotSimple is not a premium app, so it runs on the free plan, which includes 100 tasks a month, unlimited Zaps and a check every 15 minutes. The limit is the shape of the Zap: one trigger and one action. Add a second action, a filter or one of the four search steps and the Zap becomes multi-step, which Zapier reserves for paid plans. Queueing each new post stays free; drafting a post and then queueing it does not.
02How many Zapier tasks does a DotSimple Zap use?
One task per successful action, and nothing for the trigger. Zapier can check DotSimple for new posts as often as your plan allows at no cost. Only completed actions are billed, and a failed one is not counted. A Zap that queues a post uses one task per run; one that creates a post and then queues it uses two. On the free plan's 100 tasks a month, that second Zap gives you about half as many runs as the first.
03Does the DotSimple integration work in real time?
No. All four DotSimple triggers are polling triggers: Zapier asks DotSimple for new items at a fixed interval and keeps only what it has not seen yet. That interval is 15 minutes on Free, 2 minutes on Professional and 1 minute on Team and Enterprise. None of the triggers is instant, so DotSimple cannot push an event to Zapier the second it happens. On paid plans you can also run a check by hand from the editor.
04What does it take to connect DotSimple to Zapier?
An existing DotSimple account and access to the items the Zap should touch. You add the connection from the Apps page of Zapier, choose DotSimple, sign in on the tab that opens and grant access. After that, every step reuses the connection. Keep in mind that most actions ask for a UUID, so the account you connect must be the one that owns those posts, files and tags, or have read or write access to them.
05Why does a DotSimple action ask for a UUID?
Because DotSimple identifies posts, files, tags and accounts by a unique identifier, and the actions and searches work from it. Add a Post to Queue, Schedule Post and Delete Post need a Post UUID; Delete File needs a Media UUID; Delete Tag a Tag UUID. None of the searches accepts a name instead. In practice, the identifier must come from a trigger or from an earlier step in the same Zap, so design the Zap around where that value comes from.
06What if the DotSimple operation you need is not in Zapier?
Then Zapier cannot do it directly, and it is better to know before building. The integration covers posts, files, tags and accounts: create, queue, schedule, update and delete, plus four searches by identifier. Nothing reads post statistics, and no search works from a caption or a name. In that case, compare what other automation platforms list for DotSimple instead of stretching the available operations into a workaround that will be fragile.
07Zapier, Make or n8n for DotSimple?
It depends on your criteria, not on a winner. Start with the operations: on Zapier, DotSimple brings 4 triggers, 9 actions and 4 searches, so check the same events exist on the other platform. Then look at the shape of your scenarios: Zapier's free plan runs DotSimple only in two-step Zaps, and any search makes the Zap multi-step. Finally weigh timing, since every DotSimple trigger on Zapier polls. Compare those three points with your own publishing volume.
Same platform

Other docs you might need on this stack.

Browse all integrations