Resources · Make integration

Tiiny Host Make integrationAutomate Tiiny Host with Make.

Need a page online the moment something happens in another tool? The Tiiny Host Make integration gives you 6 action modules to create, update and delete sites. This guide walks you through the connection and a first scenario.

Try the Tiiny Host integration on MakeSee the 6 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the Tiiny Host Make integration do?

The Tiiny Host Make integration lets a Make scenario (the automation you build, a chain of steps) publish, refresh and remove sites on your Tiiny Host account. Every step is a module, one brick of the scenario, and all 6 Tiiny Host modules are actions: they act when an earlier step hands them data.

A page per new item. An agency builds client previews in another tool. Each time a new one is ready, Create a site from html puts it online, so nobody uploads files by hand.

A page that stays current. A price list or an event page changes often. Update a site from html or Update a site pushes the new version to the existing site instead of creating another one.

Clean-up when a project ends. When a campaign closes in your project tool, Delete a site takes the page down, and it does not come back.

What Make does not do here: Tiiny Host has no trigger, so it never starts a scenario by itself. The first step always comes from another app or from the schedule. For anything the 6 modules skip, Make an API call reaches the Tiiny Host API with the same connection. The same app sometimes exists as an n8n node too; if you are weighing both tools, read n8n vs Make. New to the editor? The Make training covers the basics, and Make pricing explains how operations (one run of one module, what your plan counts) add up.

Connect

How do you connect Tiiny Host to Make?

  1. 01

    Generate your API key in Tiiny Host

    In your Tiiny Host account, open the API Key section of the settings, click Generate and copy the key shown on screen. Keep it handy: Make asks for it in the next step.

  2. 02

    Add a Tiiny Host module in Make

    In your scenario, add any Tiiny Host module and click Create a connection. A connection is your Tiiny Host account linked to Make once, then reused by every Tiiny Host module. The Connection name field is optional.

  3. 03

    Paste the key and save

    Paste the API key you copied, or follow the instructions Make shows on screen, then save. The module now shows your connection and you can fill in its fields.

First scenario

Your first scenario with Tiiny Host

GoalWhen a new item with HTML content appears in another app, Make publishes it as a new site on Tiiny Host.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the +. Pick the trigger of the app that holds your content, for example a new record in a database or a new form entry.

  2. 02

    Add Create a site from html

    Click the + on the right of that first module, search for Tiiny Host and pick Create a site from html. Click Create a connection and paste your API key.

  3. 03

    Map the content

    Fill the module fields with data from the first module. Each bundle, one item passing from one module to the next, carries the content of one page, so one new item gives one new site.

  4. 04

    Test with Run once

    Click Run once to execute the scenario one time. Open the bubble above each module to read the bundles it received, then check that the site appears in Tiiny Host.

  5. 05

    Schedule and switch on

    On the first module, set the schedule (every 15 minutes by default) and switch the scenario on. If that first module is a scheduled trigger, Make checks for new items at that interval and publishes each one.

Modules

What can the Tiiny Host modules do?

Tiiny Host gives you 6 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Tiiny Host1

Create a site

ActionIn the docs only

As its name says, it adds a new site to your Tiiny Host account, created by the scenario rather than by hand. Make gives no official description, so open it in the editor and read the fields it asks for.

When to use it
your content is not HTML already in the scenario, and you want each new item from another app to end up as its own site.
Watch out
every bundle that reaches it creates another site, so test with Run once on a single item.
Tiiny Host2

Create a site from html

ActionIn the docs only

Straight from HTML to a live page: when an earlier step produces HTML, this module turns it into a new Tiiny Host site without any file to upload yourself. It is the natural pick for pages generated by another app.

When to use it
a form, a database or a document tool already holds the page content as HTML.
Watch out
map the HTML from the previous module, not a static test value, or every run publishes the same page.
Tiiny Host3

Delete a site

ActionIn the docs only

Removing a page you no longer want online is what this module does for you, triggered by an event elsewhere rather than by a manual clean-up. It keeps your Tiiny Host account tidy when projects or campaigns close.

When to use it
a project is marked finished in another tool and its preview site should disappear.
Watch out
a deletion cannot be undone, so make sure only finished projects reach it and test on a throwaway site first.
Tiiny Host4

Make an API call

ActionIn the docs only

Anything the five other modules do not cover, you can still reach: this module calls any endpoint of the Tiiny Host API and reuses the connection you already created, so there is no second key to set up.

When to use it
you need an operation of the Tiiny Host API that has no dedicated module in Make.
Watch out
you write the request yourself, so keep the Tiiny Host API reference open while you fill it in.
Tiiny Host5

Update a site

ActionIn the docs only

Your existing address stays the same while its content changes: this module refreshes a site that already lives on Tiiny Host, which saves you from publishing a new copy each time something moves.

When to use it
a page shared with clients or a team has to reflect the latest version without a new link to send around.
Watch out
the scenario has to know which site to change, so run it once on a test site before pointing it at a live one.
Tiiny Host6

Update a site from html

ActionIn the docs only

Fresh HTML replaces what a site shows today, and visitors keep using the same page. It pairs with a step that rebuilds the HTML, such as a template filled with data from another app.

When to use it
the page content is produced as HTML inside the scenario, and you want to refresh an existing site rather than open a new one.
Watch out
judging by its name, the new HTML takes the place of the old content, so check the result of Run once before switching the scenario on.
Need help

Need help automating Tiiny Host with Make?

A person reads every message.

FAQ

Tiiny Host and Make: common questions

01Is the Tiiny Host Make integration free?
Yes on the Make side: Tiiny Host is a standard app, available from the Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between two scheduled runs, 5 minutes of execution at most, files up to 5 MB and 512 MB of data transfer. Paid Make plans lower the interval to 1 minute and remove the cap on active scenarios. On the Tiiny Host side, the API key you need for the connection requires a Solo plan or higher, so check your Tiiny Host subscription before you start.
02What do you need to connect Tiiny Host to Make?
A Tiiny Host account on the Solo plan or higher, and an API key from it. Open the API Key section in your account settings, click Generate and copy the key shown. In Make, add any Tiiny Host module, click Create a connection, give it a name if you want, then paste the key. That single connection is reused by all 6 Tiiny Host modules, including Make an API call, so you only go through these steps once.
03Does Tiiny Host have a trigger in Make?
No. The 6 Tiiny Host modules are all actions, so Tiiny Host cannot start a scenario on its own. The scenario begins with another step: the trigger of another app, such as a new form entry or a new database record, or a schedule set on the first module. A new scenario runs every 15 minutes by default, and the Free plan does not go below that interval. A scenario can also start when an app calls Make, then the Tiiny Host modules act on the data it passes along.
04What if the Tiiny Host module you need is missing in Make?
Use Make an API call. It reaches any endpoint of the Tiiny Host API from the scenario and reuses your existing connection, so no extra setup is needed. It asks you to write the request yourself, which takes a look at the Tiiny Host API reference. Keep in mind that the Make documentation for this app is AI-generated from the Tiiny Host documentation and may contain mistakes: when a detail matters, confirm it with Tiiny Host directly before you build on it.
05Should you use Make or n8n for Tiiny Host?
It depends on the tool your team already works in. In Make, Tiiny Host comes with 6 action modules and an API call module, set up through one connection and an API key, with no code for the listed operations. Many apps also have an n8n node, so check whether Tiiny Host has one before you compare. Then weigh what matters to you: which modules cover your need, how your team learns the editor, and how each tool counts usage on your plan.
Same platform

Other docs you might need on this stack.

Browse all integrations