Resources · Make integration

Umso Make integrationAutomate Umso with Make.

Can your Umso website pass its forms, posts and publishes to the rest of your tools on its own? The Umso Make integration gives you 15 modules, 6 of them instant triggers. This guide shows how to connect your account, build a first scenario and pick the right module.

Try the Umso integration on MakeSee the 15 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Umso Make integration automate?

The Umso Make integration links your Umso websites to Make, a no-code tool where you build a scenario: the automation itself, a chain of modules. Each module is one brick, such as a trigger, an action or a search. Umso tells Make when a form is submitted, a post goes live or a site is published, and Make can also write and publish blog posts for you.

Leads that never sit in an inbox. Watch Form Submitted starts a scenario the moment a visitor sends a form on your Umso site. Each response becomes a bundle, one item passed from module to module, that you can push to a CRM, a spreadsheet or a team chat.

Posts written somewhere else, published on Umso. A marketer drafts articles in another app; Create a Blog Post drops each one into the right Umso blog and Publish a Blog Post puts it online. List blogs helps you find the target blog while you set things up.

A publishing log your team can trust. Watch Site Published and Watch Site Unpublished record every change of state of a site, so a freelancer or an agency knows which client site went live and which was taken down.

The Umso documentation lists no limits for these modules. When a module is missing, Make an API Call reaches the rest of the Umso API with the same connection. If you are also weighing n8n, the n8n vs Make comparison lays out the criteria. For the cost side of Make, see Make pricing, and to learn the editor step by step, Make training is the place to start.

Connect

How do you connect Umso to Make?

  1. 01

    Add an Umso module

    Log in to Make, open a scenario and add any Umso module. Then click Create a connection. A connection is your Umso account linked to Make once, and every Umso module reuses it afterward.

  2. 02

    Name the connection

    The Connection name field is optional, but a clear name such as the client or the site saves you from guessing later when several Umso accounts sit side by side in Make.

  3. 03

    Paste your Umso credentials

    You need an active Umso account and an API key. Enter the credentials copied from Umso or follow the on-screen instructions. For the advanced setup, create an application in Umso Settings and copy its Client ID and Client secret.

First scenario

Your first scenario with Umso and Make

GoalWhen a new article draft arrives from another app, Make creates the blog post in Umso and publishes it.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the +. Add the module of the app where your drafts live, for example a spreadsheet or a writing tool.

  2. 02

    Add Create a Blog Post

    Click the + to the right of that first module, search for Umso and pick Create a Blog Post. Click Create a connection, then choose the blog Make lists for your account.

  3. 03

    Map the draft

    Fill the post fields with data mapped from the first module: the title goes where the title belongs, the text where the text belongs. No need to type anything by hand.

  4. 04

    Chain Publish a Blog Post

    Add Publish a Blog Post after it and map the post that Create a Blog Post just returned. Your draft now goes from created to live in one pass.

  5. 05

    Test with Run once, then switch on

    Click Run once and read the bundle each module received. When the post shows up on your site, set the schedule on the first module (every 15 minutes by default) and switch the scenario on.

Triggers

Umso triggers: what starts your scenario

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

Umso1Watch Blog Post Published

Watch Blog Post Published

Instant trigger

In Make“Triggers when a post is published a blog.”

This trigger starts your scenario each time an article goes live on one of your Umso blogs, so the rest of your stack learns about it without anyone copying a link.

How it fires
instant. Umso calls Make through a webhook as soon as the post is published, with no polling interval to wait for.
When to use it
announce a fresh article in a newsletter tool or a team channel, or add it to a content calendar the moment it is public.
Watch out
when you add it, click Create a webhook before the connection, as the Umso documentation asks.
Umso2Watch Blog Post Unpublished

Watch Blog Post Unpublished

Instant trigger

In Make“Triggers when a blog post is unpublished in a blog.”

Here you learn when a post leaves the public side of a blog. Make receives the unpublished article and can tidy up wherever that article was shared.

How it fires
instant. Umso notifies Make by webhook the moment the post is unpublished.
When to use it
pull the article out of a sheet of live content, or warn the editor who owns it that it is no longer visible to readers.
Watch out
every event becomes one bundle, and each module that processes it counts as one operation on your Make plan.
Umso3Watch Form Submitted

Watch Form Submitted

Instant trigger

In Make“Triggers when a form response is submitted.”

Every response sent through a form on your Umso site lands in Make as its own bundle, ready to reach the tool where your team actually follows up.

How it fires
instant. Umso sends each submission to Make through a webhook as soon as the visitor clicks submit.
When to use it
turn contact requests into CRM records, or post a demo request in the sales chat while the prospect is still on your site.
Watch out
if you run several forms, List Forms helps you see which ones exist before you decide what to do with each response.
Umso4Watch New Blog Post

Watch New Blog Post

Instant trigger

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

With this trigger, Make hears about a blog post as soon as it exists in Umso, before anyone publishes it. That makes it the natural start of a review flow.

How it fires
instant. The app calls Make by webhook as soon as the post is created.
When to use it
ping an editor to proofread a new draft, or log each new article in a tracking sheet with its author.
Watch out
a newly created post is not yet live; if you need the moment it goes public, Watch Blog Post Published is the better pick.
Umso5Watch Site Published

Watch Site Published

Instant trigger

In Make“Triggers when a site is published.”

Each time one of your Umso sites is published, Make gets the news and can pass it on, which gives you a record of releases without any manual note.

How it fires
instant. Umso calls Make through a webhook right after the publish.
When to use it
an agency that manages sites for clients can email the client or update a project board the moment their changes are online.
Watch out
to pull more details about that site in the same scenario, add Get a Site right after the trigger.
Umso6Watch Site Unpublished

Watch Site Unpublished

Instant trigger

In Make“Triggers when the site is unpublished.”

This one tells Make when a site goes offline in Umso. It is the safety net for a page nobody expected to disappear.

How it fires
instant. Umso notifies Make by webhook as soon as the site is unpublished.
When to use it
alert the site owner and the marketing lead in chat, so a mistaken unpublish gets caught and reversed fast.
Watch out
pair it with Watch Site Published in a separate scenario if you want a complete history of both states, since each trigger listens to a single event.
Modules

Umso modules: what Make can do in your account

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

Umso1

Create a Blog Post

Action

In Make“Create a new blog post.”

You get a new article inside the Umso blog you pick, filled with text mapped from an earlier module, so drafts written elsewhere reach your site without copy and paste.

When to use it
a writer finishes a piece in a shared doc or a spreadsheet row and wants it in Umso straight away.
Watch out
creating a post does not put it online; chain Publish a Blog Post when it should go live.
Umso2

Get a Blog Post

Action

In Make“Retrieves a blog post.”

This module fetches one blog post from Umso, so the next modules can work with that post, not only with the event that started the scenario.

When to use it
right after Watch Blog Post Published, to send the article itself to a newsletter or an archive rather than a bare notification.
Watch out
it works on a single post; to go through a whole blog, List Blog Posts is the right module.
Umso3

Get a Site

Action

In Make“Retrieves a site.”

Pulling the details of one Umso site into your scenario is what this module is for, which gives later modules the site information they need to label a message or a record.

When to use it
after Watch Site Published, when the alert should say which site went live rather than just that something changed.
Watch out
if you manage many sites and do not know which one to target, start with List Sites.
Umso4

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

When none of the listed modules covers what you need, this one lets you call any endpoint of the Umso API from your scenario, with the connection you already set up.

When to use it
a task that the other Umso modules do not handle, where you know which API request does the job.
Watch out
you write the request yourself, so keep the Umso API documentation open while you fill it in.
Umso5

Publish a Blog Post

Action

In Make“Publishes a blog post.”

The result is simple: a post that already exists in Umso goes live on your blog, triggered by your scenario instead of a click in the Umso editor.

When to use it
after Create a Blog Post, or when an approval in another tool, such as a status changed to ready, should publish the article.
Watch out
publishing makes the post public, so test on a draft with Run once before switching the scenario on.
Umso6

List Blog Posts

Search

In Make“Retrieves the posts of a blog.”

Need every article of one blog at once? This search returns the posts of a blog, each as its own bundle, so you can copy them to a sheet or check them one by one.

When to use it
building an inventory of your content before a redesign, or feeding each post to another app.
Watch out
a search returns zero, one or many bundles, and every module after it runs once per bundle, which adds up in operations.
Umso7

List blogs

Search

In Make“Retrieves a list of blogs.”

This search brings back the blogs in your Umso account, which is handy when one account holds several sites and you are not sure which blog a post should land in.

When to use it
as a first step before List Blog Posts or Create a Blog Post, to route content to the right blog.
Watch out
each blog it finds becomes a separate bundle, so the modules that follow repeat for every one of them.
Umso8

List Forms

Search

In Make“Retrieves a list of forms.”

With this search, you see the forms your Umso account holds, each as a bundle, which clears up which form feeds which part of your process.

When to use it
auditing the forms spread across your sites, or preparing a scenario that treats each form differently.
Watch out
it lists forms, not their responses; to receive what visitors send, use Watch Form Submitted.
Umso9

List Sites

Search

In Make“Retrieves a list of your websites.”

Here you retrieve the websites of your Umso account in one go, a useful map when you manage several brands or several client sites from the same login.

When to use it
keeping a sheet of all your sites up to date, or finding the site to pass to Get a Site.
Watch out
like any search, it can return no bundle at all, so check the output of Run once before chaining actions.
Need help

Need help automating Umso with Make?

A person reads every message.

FAQ

Umso and Make: common questions

01Is the Umso Make integration free?
Yes, on the Make side. Umso is a standard app, available from the Make Free plan. That plan allows 2 active scenarios, a minimum interval of 15 minutes between scheduled runs, 5 minutes of execution at most, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams, Enterprise) lower the interval to 1 minute, remove the cap on active scenarios and allow 40 minutes of execution; usage is counted in operations each month. You still need an active Umso account, whose price depends on Umso.
02What do you need to connect Umso to Make?
An active Umso account and an API key. In Make, add an Umso module, click Create a connection, optionally name it, then enter the credentials copied from Umso or follow the on-screen steps. For the advanced setup, the Umso documentation describes creating an application in Settings, under API or Integrations, and copying the Client ID and Client secret it shows. With an instant trigger, click Create a webhook first, then Create a connection.
03Do Umso triggers in Make fire in real time?
Yes. All six Umso triggers are instant: Umso calls Make through a webhook as soon as a form is submitted, a blog post is created, published or unpublished, or a site is published or unpublished. There is no polling interval to wait for, unlike a scheduled trigger that Make checks on the scenario's schedule. Each event arrives as one bundle, and every module that handles it counts as one operation on your plan.
04What if an Umso module is missing in Make?
Use Make an API Call. It is part of the Umso app in Make and calls any endpoint of the Umso API with the connection you already created, so you are not limited to the 15 listed modules. You write the request yourself, which means reading the Umso API documentation. The Umso documentation on Make lists no specific limits for the modules, and it notes that its content is AI-generated, so check important details with Umso directly.
05Make or n8n for Umso?
It depends on your criteria. On Make, Umso comes with 15 ready modules, six instant triggers and a generic API call, all driven from a visual editor. Whether n8n offers an Umso node is not covered by the sources used for this page, so check the n8n catalog before choosing. Compare the two on the modules you actually need, how you prefer to build and how each tool counts usage, rather than on a general ranking.
Same platform

Other docs you might need on this stack.

Browse all integrations