Resources · Make integration

YouTestMe Make integrationAutomate YouTestMe with Make.

Can Make keep your YouTestMe user accounts in step with the rest of your tools? The YouTestMe Make integration offers 9 modules: 3 triggers, 5 actions and 1 search, all built around users. This guide links your account and walks you through a first scenario.

Try the YouTestMe integration on MakeSee the 9 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the YouTestMe Make integration let you automate?

The YouTestMe Make integration connects your YouTestMe account to Make, a no-code tool where you build a scenario (the automation itself, a chain of modules). Each module is one brick: it watches for users, creates them, updates them, reads them or removes them, so account chores stop being manual work.

Accounts ready before day one. When a person appears in another tool your team already uses, Create a User opens their YouTestMe account with the details that tool passes along, so nobody retypes names.

A clean exit. Watch User Deleted spots removed accounts, and the next module can tell a manager or tidy another system. The reverse path works too: Delete a User closes an account when someone leaves elsewhere.

Edits that travel. Watch User Updated catches changed profiles and hands each one to the app of your choice, for instance a shared spreadsheet that HR reads.

Be aware of one limit. Make states that its documentation for YouTestMe is incomplete, because little public information exists about the app. The module names are known, their fields are not described, so expect to discover them in the editor. When a listed module falls short, Make an API Call reaches the rest of the YouTestMe API. New to the editor? The Make training covers the basics, Make troubleshooting helps when a run fails, and if you are still choosing a platform, read n8n vs Make.

Connect

How do you connect YouTestMe to Make?

  1. 01

    Add a YouTestMe module

    In your scenario, click the +, search for YouTestMe and pick any of its modules. In the module panel, click Create a connection. A connection is your YouTestMe account linked to Make once, then reused by every YouTestMe module.

  2. 02

    Name the connection

    This step is optional but handy. Give the connection a name you will recognize later, such as the environment or the team that owns the account, so you pick the right one when several people share the same Make organization.

  3. 03

    Authorize and save

    Depending on what YouTestMe asks for, either approve access on its own page or paste the key it gives you. The Make docs do not say which method applies here, so follow what the window shows, then click Save.

First scenario

Build your first scenario with YouTestMe

GoalWhen a new person is added in another app, Make creates their user account in YouTestMe.

  1. 01

    Create the scenario

    Open the Scenarios page in Make and create a new scenario. Click the big + in the middle of the canvas to place the first module of the chain.

  2. 02

    Pick the source app

    Search for the app where new people show up first, for instance your form tool or HR software, and choose its trigger. Link that account with Create a connection if Make asks for it.

  3. 03

    Add Create a User

    Click the + on the right of the first module, search for YouTestMe and select Create a User. Pick your YouTestMe connection, or create it now with the three steps above.

  4. 04

    Map the person's details

    Fill each field Make displays for Create a User by clicking into it and choosing the matching value from the first module. Each new person travels as one bundle, meaning one item passed from module to module.

  5. 05

    Test with Run once

    Add a test person in the source app, then click Run once. Open the bubble above each module to read the bundle it received, and confirm the account now exists in YouTestMe.

  6. 06

    Schedule and switch on

    Click the clock on the first module to set its schedule, which is every 15 minutes by default, then switch the scenario on. From now on, new people get their account without anyone lifting a finger.

Triggers

Triggers: what starts a YouTestMe scenario

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

YouTestMe1Watch New User

Watch New User

triggerIn the docs only

Hands your scenario every account that has appeared in YouTestMe since the last check, one bundle per new user, so a welcome message or a record in another tool can follow without a manual export.

How it fires
scheduled. Make checks the app on the scenario's schedule, every 15 minutes by default, 1 minute at best on a paid plan. Make's directory gives no type for this module, so this reading comes from its name.
When to use it
when accounts get created inside YouTestMe itself and other tools need to hear about them.
Watch out
each new user costs an operation in every module that follows, so keep the chain short.
YouTestMe2Watch User Deleted

Watch User Deleted

triggerIn the docs only

Tells you which YouTestMe accounts have disappeared, so the systems around the app can close their side too instead of keeping stale entries around.

How it fires
scheduled. Make checks the app on the scenario's schedule, not the moment the account goes away. The type is inferred from the module name, since the directory lists none.
When to use it
when someone removes accounts directly in YouTestMe and a manager, a spreadsheet or a CRM should reflect it.
Watch out
the account no longer exists in YouTestMe, so a Get a User placed after this trigger has nothing left to read.
YouTestMe3Watch User Updated

Watch User Updated

triggerIn the docs only

Picks up profiles that changed in YouTestMe and passes each one down the scenario, which keeps a copy elsewhere current without anyone comparing lists by hand.

How it fires
scheduled. Make polls the app at the rhythm set on the first module, 15 minutes by default. As with the two other triggers, the scheduled type is read from the name, not stated by Make.
When to use it
when a sheet or directory mirrors YouTestMe users and must follow their edits.
Watch out
a scenario that also runs Update a User on the same accounts will feed this trigger again, so avoid pairing them in a circle.
Modules

What the YouTestMe modules do

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

YouTestMe1

Create a User

ActionIn the docs only

Opens a fresh YouTestMe account from data that arrives in the scenario, which spares your admins from typing the same names twice.

When to use it
right after a trigger in another app announces a new person, such as a signed form or a hire in your HR tool.
Watch out
Make does not document the fields, so run a test first to see which ones YouTestMe requires.
YouTestMe2

Delete a User

ActionIn the docs only

Removes an account from YouTestMe on your signal, so access ends when the person leaves rather than whenever someone remembers.

When to use it
when an offboarding event in another tool should close the matching YouTestMe account.
Watch out
Make has no undo for this step. Test it against a dummy account and add a filter so only the intended users reach it.
YouTestMe3

Get a User

ActionIn the docs only

Fetches one known YouTestMe account so the modules after it can use that person's details, for example in a message or a spreadsheet row.

When to use it
when a trigger in another app names one person and you need their YouTestMe profile rather than a list.
Watch out
you must know which user to ask for; to search across accounts, use List Users.
YouTestMe4

List Users

SearchIn the docs only

Returns the accounts held in YouTestMe as separate bundles, which gives you a starting point for an export or a check across everyone.

When to use it
when you need several users at once, for example to copy them into a spreadsheet before a review.
Watch out
it can return zero, one or many bundles, and each bundle runs the next modules again, costing operations.
YouTestMe5

Make an API Call

ActionIn the docs only

Lets you call any endpoint of the YouTestMe API from your scenario, reusing the same connection, when the eight named modules do not cover your need.

When to use it
when you want something beyond user accounts that the listed modules never mention.
Watch out
Make does not describe that API, so you must know the endpoint and the expected request before you build this step.
YouTestMe6

Update a User

ActionIn the docs only

Rewrites the details of an existing YouTestMe account, so a change made in your main tool reaches YouTestMe too.

When to use it
when someone changes team or name in your HR software and YouTestMe should follow.
Watch out
if another scenario runs Watch User Updated, each update here wakes it up, so check that the two do not keep triggering each other.
Need help

Need help automating YouTestMe with Make?

A person reads every message.

FAQ

YouTestMe and Make: common questions

01Is the YouTestMe Make integration free?
Yes, YouTestMe is a standard app in Make, so its 9 modules work on the Free plan. That plan has limits worth knowing: 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. Make counts usage in operations, one per module per bundle. This page does not cover what YouTestMe itself costs.
02What do you need to connect YouTestMe to Make?
You need a YouTestMe account and access to Make. Make lists no specific prerequisite for this app. You add any YouTestMe module, click Create a connection, optionally name it, then either approve access on the YouTestMe page or paste the key the app gives you, and save. The documentation does not say which of those two methods YouTestMe uses, because Make describes its coverage of this app as incomplete. If you are unsure, ask the person who administers your YouTestMe account which access method is available before you start.
03Do the YouTestMe triggers in Make fire in real time?
No. All three triggers, Watch New User, Watch User Deleted and Watch User Updated, are treated as scheduled, a type inferred from their names since Make's directory gives none. Make checks YouTestMe on the scenario's schedule, not the instant something changes. A new scenario runs every 15 minutes by default. On the Free plan, 15 minutes is also the shortest interval; paid plans go down to 1 minute. If a change must be acted on sooner, shorten the schedule on the first module within what your plan allows.
04What if a YouTestMe module is missing in Make?
Use Make an API Call. This module can reach any endpoint of the YouTestMe API through the same connection you already set up, which covers what the eight named modules do not. The catch is documentation: Make says it lacks enough public information to describe YouTestMe in detail, so you will need to know the endpoint and the request format yourself. Test the call with Run once and read the bundle it returns before switching the scenario on. If the API does not offer what you need, another app in Make may hold the data instead.
05Should you use Make or n8n for YouTestMe?
It depends on the tool your team already works with. In Make, YouTestMe comes with 9 modules focused on user accounts, three scheduled triggers and an API call module for the rest, and it runs on the Free plan. Many apps also have an n8n node, so check whether one exists for YouTestMe before deciding. There is no ranking to give between the two for this app. Compare them on the modules you need, how scenarios are scheduled and what your team can maintain; the n8n vs Make comparison linked above walks through those criteria.
Same platform

Other docs you might need on this stack.

Browse all integrations