Resources · Make integration

TinyPages Make integrationAutomate TinyPages with Make.

Can Make keep TinyPages in step with the rest of your tools? Yes: the TinyPages Make integration offers 12 modules, with 4 triggers, 7 actions and 1 search. This page shows marketers and ops teams how to link the account, build a first scenario and pick the right module.

Try the TinyPages integration on MakeSee the 12 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the TinyPages Make integration do for you?

The TinyPages Make integration links your TinyPages audience to your other tools without code. In Make you build a scenario, the automation itself, out of modules: each module is one brick, a trigger that starts the flow, an action or a search. TinyPages brings 12 of them.

A CRM that respects opt-outs. Watch Unsubscribed Contacts hands every opt-out to your CRM, so sales stops writing to people who already left the list.

Sign-ups from anywhere, one clean audience. A form or a shop collects an email, Find a Contact checks whether the person already exists, and Add a Contact or Update a Contact keeps a single record.

Tags that start a follow-up. Watch New Contact Tag notices when your team tags a lead, and the next module alerts the right person in another tool.

Know the limits before you start. Make flags its TinyPages documentation as limited, with no field detail for any module, and the four triggers are typed as scheduled from their names alone. Make an API Call covers the gaps with the same connection. If n8n is also on your shortlist, the n8n vs Make comparison lays out the criteria, and the Make troubleshooting guide helps when a run fails.

Connect

How do you connect TinyPages to Make?

  1. 01

    Add a TinyPages module

    Open a scenario, click the + and search for TinyPages. Pick any module, Watch New Contact for example, then click Create a connection. The connection is your TinyPages account linked to Make, set up once and reused by every TinyPages module.

  2. 02

    Name it and authorize Make

    Give the connection a name if you handle several accounts; a client name works well. Then authorize Make on the TinyPages page, or paste the key TinyPages gives you, depending on what the window asks for.

  3. 03

    Save and check the module

    Click Save. Back in the module, Make can now list what it reads from your account. If nothing shows up, the link did not take: open the connection again and repeat the authorization.

First scenario

Your first TinyPages scenario, step by step

GoalWhen someone signs up through a form in another app, Make adds that person to TinyPages as a contact.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the large + to place the first module. Nothing runs until you switch it on, so feel free to try things.

  2. 02

    Start from your form

    Search the app that collects sign-ups, a form tool for instance, and pick its trigger. Each new entry will travel through the scenario as one bundle, the item a module hands to the next.

  3. 03

    Add the TinyPages module

    Click the + on the right, search TinyPages, choose Add a Contact and click Create a connection to link your account. Make can then show what TinyPages expects.

  4. 04

    Map the form data

    In Add a Contact, click each field and pick the matching value from the form module, the email going where TinyPages asks for one. That mapping is how data moves between modules.

  5. 05

    Test with Run once

    Click Run once, then send a test sign-up. Make shows the bundles each module received; check in TinyPages that the contact appeared with the right details.

  6. 06

    Schedule and switch on

    Set the schedule on the first module, every 15 minutes by default, then switch the scenario on. Each module run on each sign-up counts as one operation on your plan.

Triggers

What can start a TinyPages scenario?

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

TinyPages1Watch New Contact

Watch New Contact

triggerIn the docs only

Watch New Contact hands your scenario every contact that appears in TinyPages, one bundle per person, so the rest of the flow can copy, greet or sort that contact without anyone exporting a list.

How it fires
scheduled. Make checks the app on the scenario's schedule, every 15 minutes by default, so a contact arrives at the next check rather than the moment it signs up.
When to use it
a new subscriber on a landing page should also appear in your CRM or a team spreadsheet.
Watch out
the scheduled type is inferred from the module name, since the documentation is thin; click Run once to see what a contact carries.
TinyPages2Watch New Contact Tag

Watch New Contact Tag

triggerIn the docs only

Turn a tag into a switch: Watch New Contact Tag starts your scenario when a contact receives a tag in TinyPages, so tagging someone by hand can set off work in another tool.

How it fires
scheduled. Make checks the app on the scenario's schedule, not at the instant the tag is set.
When to use it
your team marks promising leads with a tag and sales should hear about them in the tool they already watch.
Watch out
the documentation does not say whether you can narrow it to one tag, so open the module and look at its settings before relying on it.
TinyPages3Watch New Member

Watch New Member

triggerIn the docs only

New members reach your scenario on their own with Watch New Member: each one becomes a bundle the next module can use, and onboarding no longer depends on someone checking the member list.

How it fires
scheduled. Make checks the app on the scenario's schedule and brings back the new members found at each check.
When to use it
a new member should receive access, a welcome message or a line in a tracking sheet held in another app.
Watch out
the documentation does not explain how a member differs from a contact in TinyPages; compare this trigger and Watch New Contact with Run once before choosing.
TinyPages4Watch Unsubscribed Contacts

Watch Unsubscribed Contacts

triggerIn the docs only

Every person who opts out in TinyPages becomes a bundle your scenario can act on, which stops your other tools from writing to people who said no.

How it fires
scheduled. Make checks the app on the scenario's schedule, so the opt-out reaches your other tools at the next check.
When to use it
the same people also live in a CRM or a sales tool that has to stop contacting them.
Watch out
each unsubscribed contact uses one operation per module it passes through, and operations are what Make counts on your plan.
Modules

What can each TinyPages module do?

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

TinyPages1

Add a Contact

ActionIn the docs only

Add a Contact creates a person in TinyPages from data another module brings, so sign-ups collected elsewhere end up in the same audience without copy and paste.

When to use it
a form, a shop or an event tool collects emails and those people belong in TinyPages.
Watch out
the documentation says nothing about duplicates, so place Find a Contact before it when the same person can arrive twice.
TinyPages2

Add a Member

ActionIn the docs only

Registering someone as a member no longer needs a person at the keyboard: Add a Member does it from your scenario, as the counterpart of the Watch New Member trigger.

When to use it
a payment or an approval in another app should grant membership without anyone stepping in.
Watch out
the documentation gives no field list, so add the module, connect it and read what it asks for before you map anything.
TinyPages3

Add a Tag

ActionIn the docs only

Your scenario can label people for you: Add a Tag applies a tag in TinyPages where a teammate would otherwise click through profiles.

When to use it
a purchase, a webinar sign-up or a support ticket in another app says something about a contact worth recording.
Watch out
the name alone does not tell whether it tags one contact or creates a new tag in the account; open the module once to see which it expects.
TinyPages4

Add an Email

ActionIn the docs only

Add an Email lets your scenario hand TinyPages something email-shaped, but beyond the module name the documentation does not say what it creates.

When to use it
your flow produces an email that TinyPages should keep, and neither Add a Contact nor Update a Contact fits.
Watch out
add it to a test scenario, click Run once with sample data and check in TinyPages what it really created before you build on it.
TinyPages5

Delete a Tag

ActionIn the docs only

Segments stay accurate when situations change, because Delete a Tag removes a tag in TinyPages from inside a scenario.

When to use it
a lead becomes a customer in your CRM and the old prospect tag should go.
Watch out
the name does not say whether it strips the tag from one contact or removes it from the whole account, so try it on a throwaway tag first.
TinyPages6

Find a Contact

SearchIn the docs only

Before writing anything, Find a Contact looks a person up in TinyPages and returns what it finds, so later modules update the right record instead of creating a double.

When to use it
ahead of Update a Contact or Add a Contact, whenever the incoming email may already exist.
Watch out
like every search module, it can return zero, one or several bundles, and each following module runs once per bundle.
TinyPages7

Make an API Call

ActionIn the docs only

Anything the listed modules miss is still reachable: Make an API Call sends a request to any endpoint of the TinyPages API with the connection you already set up.

When to use it
you need an action none of the other eleven modules offers and TinyPages documents the endpoint for it.
Watch out
Make marks its TinyPages documentation as limited, so the endpoint details have to come from TinyPages itself.
TinyPages8

Update a Contact

ActionIn the docs only

Update a Contact changes an existing person in TinyPages, so their record follows what happens in your other tools without anyone retyping it.

When to use it
a customer edits their details in your shop or CRM and TinyPages should show the same thing.
Watch out
the module has to know which contact to change, so put Find a Contact before it when the incoming data only carries an email.
Need help

Need help automating TinyPages with Make?

A person reads every message.

FAQ

TinyPages and Make: common questions

01Is the TinyPages Make integration free?
Yes. TinyPages is a standard app in Make, so its modules work on the Free plan. That plan allows 2 active scenarios, at least 15 minutes between two scheduled runs, 5 minutes per execution, files up to 5 MB and 512 MB of data transfer. Paid plans, namely Core, Pro, Teams and Enterprise, lower the interval to 1 minute, remove the cap on active scenarios and allow 40 minutes per run; usage is counted in credits, meaning operations, per month. Your TinyPages subscription is a separate matter this page does not cover.
02What do you need to connect TinyPages to Make?
A TinyPages account and a Make account; the documentation lists no other prerequisite for this app. Add any TinyPages module, click Create a connection, name it if you like, then either authorize Make on the TinyPages page or paste the key TinyPages provides, and click Save. The connection is stored once and reused by every TinyPages module in all your scenarios. If the window asks for a key you cannot locate, TinyPages support is the right place to ask, since Make's documentation for this app is marked as limited.
03Does the TinyPages trigger fire in real time?
No. The four TinyPages triggers are typed as scheduled, a type inferred from the module names because the directory entry was unavailable. Make checks TinyPages on the scenario's schedule, every 15 minutes by default, with 15 minutes as the floor on the Free plan and 1 minute on paid plans. A new contact, member, tag or opt-out therefore reaches your scenario at the next check, not the second it happens. If that gap matters, a paid plan lets you shorten the interval, and the rest of the flow runs right after the trigger.
04What if a TinyPages module is missing in Make?
Use Make an API Call. It calls any endpoint of the TinyPages API from your scenario with the same connection, so an action outside the 12 listed modules is still within reach. The catch is documentation: Make marks its TinyPages page as limited because little public information exists about the app, so endpoint and field details have to come from TinyPages. When the API does not cover the need either, another app in your stack may hold the same data and offer the module you want.
05Should you use Make or n8n for TinyPages?
It depends on the flow you have in mind. On the Make side the facts are clear: 12 modules, 4 scheduled triggers, 7 actions counting the API call, and 1 search. n8n often has a node for the same app, so check its catalog for TinyPages, then compare what each tool offers against the exact steps you need. No ranking applies here; pick the tool that covers your case with the fewest workarounds. The comparison page linked in the section above sets out the general criteria side by side.
Same platform

Other docs you might need on this stack.

Browse all integrations