Resources · Zapier integration

MarkUp.io Zapier integrationAutomate MarkUp.io with Zapier.

The MarkUp.io Zapier integration carries review feedback out of MarkUp.io and into the tools your team works in. Zapier offers 8 triggers, 0 actions and 0 searches for MarkUp.io: comments, replies, new markups and finished reviews each start a Zap, instantly.

See the 8 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the MarkUp.io Zapier integration is good for

MarkUp.io lets people leave visual comments directly on a file, on more than 30 file types including websites, PDFs and videos. Linking it to Zapier sends each review event to the rest of your stack: a comment posted, a thread resolved, a review finished. The flow runs one way, out of MarkUp.io, through eight triggers.

Three results teams build first. Feedback that turns into work: Comment Created opens a task in your project tool for each new comment, so nothing stays buried on the page. A clear signal that a round is over: Markup Project Review Created fires when a reviewer is done, and the project lead gets a message instead of checking back. A change log of decisions: Comment Resolved and Comment Unresolved write every change, resolved or unresolved, to a sheet.

All eight triggers are instant, so even on the free plan nothing waits for a timed check.

Where it stops. Zapier offers no action for MarkUp.io: a Zap cannot post a comment, reply, resolve a thread or create a markup. There is no search step either, so a Zap cannot look up an older comment. MarkUp.io is always where the Zap starts, never where it writes. To compare with other platforms, see our Make vs Zapier comparison, then our Zapier training.

Vocabulary

Zapier vocabulary, briefly

Seven terms come back throughout this page. One plain line each.

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 an app that starts the Zap, such as a new comment in MarkUp.io. Once the Zap is on, Zapier waits for it.
Action
What the Zap does after it starts: the step that writes, sends or moves something. With MarkUp.io, it always runs in another app.
Task
The unit Zapier bills: one action your Zap completes successfully. The allowance on your plan counts those.
Instant vs polling
An instant trigger is reported by the app the moment the event happens. A polling trigger is checked by Zapier on a timer.
Filter
A step that lets the Zap continue only when what arrived meets the condition you set, and stops it there otherwise.
Search step
A step that looks up something already stored in an app for the next steps to use. MarkUp.io has none on Zapier.
Cost

What a MarkUp.io Zap costs

MarkUp.io is not a premium app, so it works on the free Zapier plan. You pay in tasks, and a MarkUp.io trigger never uses one.

  • Free plan100 tasks a month, two-step Zaps
  • Premium appNo
  • MarkUp.io triggers8, all instant, never billed
  • BilledEach successful action in the next app

A comment, a reply or a finished review starting a Zap is free. Tasks come from the action in the other app: one for each action that succeeds, none when it fails. The free plan gives 100 tasks a month and unlimited Zaps, each with two steps: one trigger, one action. Add a filter or a second action and you have a multi-step Zap (any Zap beyond one trigger and one action), which needs a paid plan. Comment triggers can be busy on a lively review, so watch the task count. The interval grid below does not apply to MarkUp.io: its eight triggers are instant on every plan.

Connect

Connect MarkUp.io to Zapier in three steps

  1. 01

    Open the Apps page

    In your Zapier account, open the Apps page and click + Add connection. Keep your MarkUp.io login at hand; Zapier connects to an account that already exists.

  2. 02

    Find MarkUp.io

    Search for MarkUp.io in the dialog, pick it, then click Add connection. A new browser tab opens on the MarkUp.io side so you can sign in to your workspace.

  3. 03

    Sign in and grant access

    Log in to MarkUp.io in that tab and allow Zapier in. The connection (your account linked once, then reused by every step) appears on the Apps page. If the workspace is someone else's, your account needs read access to it.

First Zap

Your first Zap: each comment becomes a task

GoalEvery new comment left in MarkUp.io creates a task in your project tool, but only when a field you pick matches your rule.

  1. 01

    Pick the trigger

    Create a Zap, choose MarkUp.io as the trigger app and Comment Created as the event. It is instant: every new comment reaches Zapier without a timed check.

  2. 02

    Test on a real comment

    Run the trigger test. Zapier brings back the three most recent comments of the connected account; pick one so the rest of the Zap is mapped on real data.

  3. 03

    Add the filter

    From the plus icon, add Filter and set the field, the rule and the value. Use a text rule on a text field. The filter makes the Zap multi-step, so it needs a paid plan.

  4. 04

    Add the task step

    Add your project tool with its create-task action, and build the task title and description from the comment. Check at test time which fields come through.

  5. 05

    Test, then publish

    Test the task step once and open the task it created. When it looks right, click Publish: from then on, each new comment starts the Zap.

Triggers

MarkUp.io triggers in Zapier

8 events start a Zap when something happens in MarkUp.io, and 8 of them are instant: the app calls Zapier straight away, whatever your plan.

1

Comment Created

Instant trigger

In Zapier“Triggers when a new comment is created within a MarkUp.io workspace.”

Starts a Zap for every new comment posted anywhere in a MarkUp.io workspace. It is the broadest of the eight, the one that catches all incoming feedback before anyone reads it.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
each piece of feedback should become a task in your project tool, so the designer or developer has a to-do list rather than a page of notes.
Watch out
it covers the whole workspace, so a busy review can use many tasks; a filter narrows it down, on a paid plan.
2

Comment Reply Created

Instant trigger

In Zapier“Triggers when a new reply is created within an existing comment.”

Fires when someone answers inside an existing comment thread. Unlike the trigger above, it follows the conversation rather than the first remark, which is where a lot of decisions get made.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
the person who left the first comment wants to know when someone answers, without keeping the MarkUp.io tab open all day.
Watch out
check at test time whether the reply also carries the text of the original comment before you quote it in a message.
3

Comment Resolved

Instant trigger

In Zapier“Triggers when a comment is resolved within a MarkUp.io workspace.”

Reacts when a comment is marked as resolved in a MarkUp.io workspace. That is the moment a requested change is considered done, which makes it a good point to close the loop elsewhere.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
you log every closed point in a sheet so the client can see what has been handled since the last round.
Watch out
Zapier also lists a Comment Unresolved trigger, so a point marked resolved may not stay closed; if your log must stay accurate, pair this Zap with one on Comment Unresolved and check both at test time.
4

Comment Unresolved

Instant trigger

In Zapier“Triggers when a comment is unresolved within a MarkUp.io workspace.”

Goes off when a comment is marked as unresolved in a MarkUp.io workspace. It is the counterpart of Comment Resolved, so a point that seemed settled can come back to your team's attention.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
a reopened comment should alert the person in charge straight away, by message or by a new task, before it gets lost in the thread.
Watch out
a brand new comment goes through Comment Created, not this trigger; check at test time what an unresolved comment brings back before you build the message.
5

Markup Created

Instant trigger

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

Triggers when a new markup, the item people comment on in MarkUp.io, is created. It marks the start of a review rather than its content, which suits announcements and tracking.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
the team chat should hear about each new piece put up for review, so reviewers know there is something waiting for them.
Watch out
the source does not list the fields a markup carries, so check at test time what comes back before you build a message around it.
6

Markup Status Changed

Instant trigger

In Zapier“Triggers when the status of a Markup changes.”

Fires whenever the status of a markup changes. It follows the life of the whole item rather than single comments, which is useful when other tools track the same project.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
your project tool should mirror where each review stands, so a manager sees the state without opening MarkUp.io.
Watch out
the source does not list the possible statuses, so check at test time which values arrive before writing a filter rule on them.
7

Markup Project Review Created

Instant trigger

In Zapier“Triggers when the user is done reviewing the content.”

Signals the end of a review: it fires when a reviewer has finished going through the content. Of the eight, it is the one that says a round of feedback is complete, not just that one more remark came in.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
the project lead should get one message when a client is done reviewing, instead of a notification per comment.
Watch out
the Zapier label is Markup Project Review Created, so look for that exact name in the event list.
8

Markup Pause Comments Changed

Instant trigger

In Zapier“Triggers when the read only status of a Markup changes.”

Reacts when the read-only status of a markup is switched, meaning comments are paused or opened again. It lets the rest of your tools know when feedback on an item is frozen.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
once comments are paused, you want reviewers told that the round is closed, so nobody tries to add a late remark.
Watch out
it fires on both switches, pausing and reopening, so check at test time how the two cases differ before you filter.
When it breaks

When a MarkUp.io Zap breaks

Zapier links no help article to MarkUp.io, and the source records no limit specific to the app. The cases below come from how Zapier works in general.

Four cases to know before you publish. Each has a simple workaround. If a Zap still misbehaves, our Zapier troubleshooting page is the next stop.

  • Earlier feedback stays put

    A Zap only reacts to what happens after you switch it on. Comments, replies and reviews from before stay in MarkUp.io; moving them is a separate job.

  • A busy review eats tasks

    Every comment that starts a Zap leads to an action, and each successful action costs a task. On a review with many remarks, the 100 free tasks go quickly.

  • A bulk batch held back

    When a trigger suddenly returns a huge batch, after an import or a migration, Zapier's flood protection can hold those items back instead of passing them all on.

  • The next step fails

    MarkUp.io only starts the Zap; the work happens in the other app. If that action fails, for example on an empty required field, it costs no task, but nothing is written.
Need help

Need help automating MarkUp.io with Zapier?

A person reads every message.

FAQ

MarkUp.io Zapier integration: what people ask

01Is the MarkUp.io Zapier integration free?
Yes. MarkUp.io is not a premium app, so it runs on the free Zapier plan. That plan gives 100 tasks a month and unlimited Zaps, each with two steps: one trigger and one action. A Zap from Comment Created to a task in your project tool fits that model. Add a filter to keep only some comments, or a second action, and the Zap becomes multi-step, which needs a paid plan. Plan the Zap's shape before you build it.
02How many tasks does a MarkUp.io Zap use?
MarkUp.io triggers use none: a new comment, reply or review starting a Zap is free. Tasks come from the actions that follow in other apps, one per successful action, none when one fails. That is why comment triggers deserve attention: a review with many remarks means many tasks. A Zap on Markup Project Review Created, by contrast, fires once per finished review. Count the actions and the expected events before you estimate a month.
03Does MarkUp.io send comments to Zapier in real time?
Yes. All eight MarkUp.io triggers are instant: the app tells Zapier itself when a comment, a reply, a status change or a review happens, so the Zap does not wait for a timed check. The plan interval grid does not apply to them, even on the free plan. In the editor, instant triggers carry a lightning bolt, which is the quickest way to confirm it. The speed of the next step depends on the other app.
04What do you need to connect MarkUp.io to Zapier?
A MarkUp.io account and a few clicks in Zapier. Open the Apps page, click + Add connection, search for MarkUp.io, sign in in the tab that opens and grant access. If the workspace belongs to someone else, the account you connect needs read access to it. Testing a trigger then brings back the three most recent items of that account, a quick check that the right workspace is linked. Once linked, every Zap that starts from MarkUp.io reuses that connection, so the setup is done only once.
05Which MarkUp.io trigger tells you a review round is finished?
Markup Project Review Created. It fires when a reviewer has finished going through the content, rather than on each remark, so it gives one clear signal per review. Comment Created, by contrast, fires on every new comment. If you want a single message to the project lead when a client is done, build the Zap on the review trigger and keep comment-level Zaps for the people who handle each point.
06What if the MarkUp.io operation you need is not in Zapier?
Then Zapier cannot do it with MarkUp.io for now. The editor offers eight triggers and no action, so a Zap cannot post a comment, reply, resolve a thread or create a markup, and there is no search step to look up older feedback. The list follows the version of the app that Zapier publishes and can change, so check the MarkUp.io page on zapier.com again before ruling the idea out.
07Zapier, Make or n8n for MarkUp.io?
Choose on criteria, not on a ranking. Coverage first: on Zapier, MarkUp.io gives eight instant triggers and no action, so check whether the other tool connects to MarkUp.io with the events you need. Then billing: Zapier never charges for the trigger, only each successful action, which matters with busy comment threads. Then the free plan: two steps per Zap, so any filter means paying. How much each point weighs depends on your review volume.
Same platform

Other docs you might need on this stack.

Browse all integrations