Resources · Make integration

Unshape Make integrationAutomate Unshape with Make.

What can the Unshape Make integration actually do for your posts? Make gives Unshape 4 action modules: create a post, read one from its link, reply to one, or call the API directly. This guide walks you from the connection to a first working scenario.

Try the Unshape integration on MakeSee the 4 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the Unshape Make integration let you automate?

The Unshape Make integration links your Unshape account to Make so posts get created, read and answered without you copying anything by hand. You build a scenario (the automation itself, a chain of bricks called modules), and each Unshape module handles one post at a time.

Turn content from another tool into posts. A marketer keeps drafts in a spreadsheet or a form. A trigger from that other app starts the scenario, and Create a Post turns each new entry into an Unshape post, so nobody pastes text twice.

Answer from a link. A support lead collects post links in a shared list. Get Post by URL reads the post behind each link, then Reply to Post sends the prepared answer to that exact post.

Cover what the list does not. Only four modules exist, and none of them is a trigger. When you need another call to Unshape, Make an API Call reaches any endpoint with the same connection. If you are still weighing the tool itself, the Make review and the Make pricing guide cover the basics.

One honest limit: Make's own documentation for Unshape is thin, since little public information about the app exists. Expect to discover the fields inside each module once your account is connected. The same kind of app often exists on n8n as well; the n8n vs Make comparison helps you pick where to build.

Connect

How do you connect your Unshape account to Make?

  1. 01

    Add an Unshape module

    In any scenario, search for Unshape, pick one of its modules and click Create a connection. A connection is your Unshape account linked to Make once, then reused by every Unshape module you add later.

  2. 02

    Name it if you like

    Make offers a name field for the connection. It is optional, but a clear label such as the account or brand it belongs to helps a lot once you manage several Unshape accounts in the same organization.

  3. 03

    Authorize and save

    Depending on what Unshape asks, either approve Make on the Unshape page that opens, or paste the key Unshape gives you. Then click Save, and the connection is ready for every Unshape module.

First scenario

Build your first scenario with Unshape

GoalWhen a new entry lands in another app, Make turns it into an Unshape post with Create a Post.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the + to add the first module. Since Unshape has no trigger, this first module comes from the app that holds your content.

  2. 02

    Pick the starting app

    Search that other app, choose its module that watches for new entries and connect its account. Each new entry becomes a bundle, meaning one item that flows on to the next module.

  3. 03

    Add Create a Post

    Click the + on the right of the first module, search Unshape and choose Create a Post. Connect your account, then map the text from the previous module into the post fields Make shows you.

  4. 04

    Test with Run once

    Click Run once to execute the scenario a single time. Open the bubble above each module to read the bundle it received, and check the post in Unshape before going further.

  5. 05

    Schedule and switch it on

    Set the schedule on the first module (every 15 minutes by default), then switch the scenario on. Each module run counts as one operation, the unit Make counts on your plan.

Modules

What each Unshape module does in Make

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

Unshape1

Create a Post

ActionIn the docs only

You get a new Unshape post built from data your scenario already carries, so a draft written elsewhere goes out without a copy and paste.

When to use it
right after a module from another app, such as a form or a sheet, hands over the text you want to publish.
Watch out
the documentation does not describe the fields, so run the scenario once and check the post in Unshape before switching it on.
Unshape2

Get Post by URL

ActionIn the docs only

Paste or map the link of a post and this module brings the post itself into your scenario, ready for the next step to use.

When to use it
your team collects links in a list or a message, and you need the post behind each link before replying to it or saving it somewhere.
Watch out
it reads one post per link, so a column of links means one run of the module, and one operation, per row.
Unshape3

Make an API Call

ActionIn the docs only

This one gives you access to any endpoint of the Unshape API while reusing the connection you already created, with no extra login to manage.

When to use it
the task you have in mind is not covered by the three other modules, for instance an action Unshape offers that Make has not turned into a module.
Watch out
you write the request yourself here, so read the Unshape API reference before building it.
Unshape4

Reply to Post

ActionIn the docs only

Your scenario answers an existing post in Unshape, which means a prepared response reaches the right conversation without anyone opening the app.

When to use it
after Get Post by URL has found the post, or when an earlier module already knows which post needs an answer.
Watch out
a reply goes out as soon as the module runs, so test on a post of your own with Run once first.
Need help

Need help automating Unshape with Make?

A person reads every message.

FAQ

Unshape and Make: common questions

01Is the Unshape Make integration free?
Yes, on the Make side. Unshape is a standard app, so its modules work from the Free plan onward. That plan comes with 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 each month, one per module run. Any cost of Unshape itself sits outside Make.
02What do you need to connect Unshape to Make?
An Unshape account and a Make account. Make's documentation for Unshape lists no special prerequisite and no official connection steps, so the generic Make flow applies. Add any Unshape module, click Create a connection, give it a name if you want, then either authorize Make on the Unshape page or paste the key Unshape provides, and click Save. That connection is stored once and every other Unshape module in your scenarios reuses it, so you only go through this step a single time per account.
03Can an Unshape scenario start on its own in real time?
Not from Unshape. The app has no trigger module in Make, so nothing in Unshape can start a scenario. You have two ways around it. Start with a trigger from another app, a form or a spreadsheet for example, and place the Unshape module after it. Or start on the schedule of the first module, which runs every 15 minutes by default and can go down to 1 minute on a paid plan. In both cases the Unshape modules act once the scenario is already running.
04What if the Unshape module you need is missing in Make?
Use Make an API Call. Make only lists four Unshape modules: Create a Post, Get Post by URL, Reply to Post and the API call itself. That last one reaches any endpoint of the Unshape API with the connection you already have, so an action without its own module is still within reach. Keep in mind that Make's documentation on Unshape is limited, since little public information exists about the app. The Unshape API reference is where you confirm which request to send before you build it.
05Should you use Make or n8n for Unshape?
It depends on which modules you need. On Make, the Unshape app is confirmed with four modules: creating a post, reading a post from its URL, replying to a post, and a raw API call for everything else. The same app often has an n8n node too, but check that one exists and covers your actions before choosing. Neither tool is ranked here. If your other automations already run on one platform, keeping Unshape there means one place to watch your scenarios and one set of connections.
Same platform

Other docs you might need on this stack.

Browse all integrations