# Connect your waitlist to Make

The LaunchList app on Make works in both directions. A new signup, a confirmed email, a credited referral or a redeemed invite can start a scenario, and any app Make connects can add a signup to your waitlist, move it to a stage, tag it or invite it in. You connect it with one key made in LaunchList. The app is on the Launch plan and the Grow plan, and every plan can still send events to Make through a webhook.

How it connects: Official app. Canonical page: https://getlaunchlist.com/plugins/make. Updated 2026-10-19.

[Get the LaunchList app on Make](https://www.make.com/en/hq/app-invitation/7aabe1e3821a3a7d4194ae6b14f91c3e)

## Set it up

1. **Create a key for Make.** In LaunchList, open **Embed & API**, then **Overview**. Under **Connectors**, press **Connect** on the Make row. LaunchList makes the key and shows it once, so copy it with **Copy key and open Make**.
2. **Connect LaunchList in Make.** Open the [LaunchList app on Make](https://www.make.com/en/hq/app-invitation/7aabe1e3821a3a7d4194ae6b14f91c3e) and install it in your Make organization, once. Then, in a scenario, add a **LaunchList** module and press **Create a connection**. Paste the key into **API key** and save. Make names the connection after your workspace.
3. **Pick a trigger or an action.** Start a scenario with a LaunchList trigger such as **New Signup** or **Referral Credited**, or add a LaunchList action such as **Add Contact** or **Move Contact to Stage** after another app's module. A trigger asks you to create a webhook for it. Choose your project when Make asks.
4. **Map the fields and turn it on.** Make lists every field a LaunchList module gives, such as **Email**, **Name** and **Referral link**, before the first event arrives. Map them into the next module, turn the scenario on, and the next signup runs it.

## Make triggers for your waitlist

A trigger starts a scenario the moment something happens in LaunchList. Each one fires for the project
you pick, so two launches never mix.

| Trigger               | Starts a scenario when                                               |
| --------------------- | -------------------------------------------------------------------- |
| New Signup            | Someone joins your waitlist for the first time                       |
| Signup Confirmed      | A signup confirms their email address                                |
| New Form Submission   | Any of your forms gets a response, from a new person or one you know |
| Contact Stage Changed | A contact moves to another stage of your funnel, such as invited     |
| Referral Credited     | A referral counts for the person who shared their link               |
| Invite Issued         | An early-access code is created                                      |
| Invite Redeemed       | Someone uses their code, or you mark them as in                      |
| Invite Revoked        | An early-access code is taken back                                   |
| Invite Expired        | An early-access code reaches its expiry date                         |
| Contact Unsubscribed  | A contact unsubscribes from your emails                              |

New Form Submission can be limited to one form, and Contact Stage Changed to moves into one stage.
An event that does not match does not start the scenario.

Every trigger about a contact hands the scenario the details your next module needs, as fields ready to
map: the email and name, the form answers, the stage, the person's referral link and their position
in line. Referral Credited also carries the ID, name, email, referral count and link of the person who
shared.

## Make actions for your waitlist

An action lets any app Make connects read or change your list in LaunchList.

| Action                  | What it does                                                                  |
| ----------------------- | ----------------------------------------------------------------------------- |
| Add Contact             | Adds a signup, with the same duplicate check and referral credit as your form |
| Find or Create Contact  | Finds a contact, and adds them only when nobody matches                       |
| Update Contact          | Changes a contact's email, external ID or other details                       |
| Move Contact to Stage   | Moves a contact to a stage of your funnel                                     |
| Add Tag to Contact      | Tags a contact, and creates the tag if it is new                              |
| Remove Tag From Contact | Takes a tag off a contact                                                     |
| Invite Contact          | Gives a contact early access, the same as inviting them in LaunchList         |
| Mark Invite as Redeemed | Records that a person got into your product                                   |
| Unsubscribe Contact     | Unsubscribes a contact, to pass on an opt-out from another tool               |
| Get Position            | Returns a contact's place in line and how far one more referral moves them    |
| Get Contact Count       | Returns how many contacts a project has, by status and by stage               |

**Find Contact** looks a person up by email, identifier or the ID they have in your own app, and
returns their stage, position and referral link. **Make an API Call** reaches any other part of the
[LaunchList API](https://app.getlaunchlist.com/help/docs/api/authentication) the key is allowed to use, such as your segments.

## Two-way scenarios founders build

- **Mark paying customers as converted.** When a payment succeeds in Stripe, find the contact by the
  customer's email with Find Contact, then move them to your converted stage with Move Contact to
  Stage. Your funnel shows who paid without a spreadsheet in between.
- **Collect signups from Typeform or Tally.** A new response in either one runs Add Contact, so the
  person gets a referral link and a place in line, the same as on your launch page.
- **Tell people who share where they stand.** Start from Referral Credited, run Get Position with the
  referrer's ID, and email them their new place in line from Gmail.
- **Post your count each morning.** Run Get Contact Count on a schedule and post the total to Slack,
  so the team sees the list grow without opening LaunchList.
- **Hear when someone gets in.** Start from Invite Redeemed and post to Slack, so the team knows the
  moment a person from the waitlist starts using the product.
- **Keep your other tools up to date.** Start from New Signup and add a row in Google Sheets, or a
  contact in HubSpot or Mailchimp. Use Signup Confirmed instead when you only want people who
  confirmed their email.
- **Let your own app open the door.** When someone creates an account in your product, run Mark
  Invite as Redeemed with the ID they have in your app. LaunchList records that they are in, and
  Invite Redeemed hands that ID to your other scenarios.
- **Honor unsubscribes everywhere.** Start from Contact Unsubscribed and unsubscribe the same address
  in your email tool, or run Unsubscribe Contact when someone opts out somewhere else.

## On any plan: a custom webhook

The official app is on the Launch plan and the Grow plan. On every plan, LaunchList can still send
events to Make through a webhook. It takes a little more setup, and you map the event's JSON fields
yourself.

1. In Make, start a scenario with **Webhooks** and the **Custom webhook** trigger, add a webhook and
   copy its address.
2. In LaunchList, open **Embed & API**, then **Developers**, then **Webhooks**. Press **New endpoint**,
   paste the address and choose the events, such as `signup.created`.
3. While Make waits for data, press **Send test** on the endpoint, so Make learns the event's fields.
   Then map them into the next module.

An endpoint can listen to any of the 27 event types. Each event arrives as JSON with the signup
under `data.object`. To add people from Make this way, call the API's
[create contact endpoint](https://app.getlaunchlist.com/help/docs/api/contacts-create) from Make's **HTTP** module with an API key. The
[webhook guide](https://app.getlaunchlist.com/help/docs/plugins/webhook) has every event, the payload and the signature.

## Frequently asked questions

### Is there an official LaunchList app on Make?

Yes. Install it from [its page on Make](https://www.make.com/en/hq/app-invitation/7aabe1e3821a3a7d4194ae6b14f91c3e), then search for LaunchList when you add a module to a scenario. It has 10 triggers, 11 actions, a Find Contact search and Make an API Call, and it connects with a key you make in LaunchList.

### Which plans include the Make app?

The Launch plan and the Grow plan. On the Free plan and the Collect plan, the API and webhooks still work, so you can reach Make with a custom webhook instead. The steps are at the end of this page.

### Can Make add people to my waitlist?

Yes. The Add Contact action runs a signup through the same steps as your own form, which are the duplicate check, referral credit and any emails your form sends. Someone who is already on your list is not added twice. Find or Create Contact adds a person only when nobody matches.

### Will my test signups start my scenarios?

No. Signups from your project's test mode are left out, unless you turn on **Include test signups** when you create the trigger's webhook.

### What is the difference between New Signup and New Form Submission?

New Signup fires once per person, the first time they join. New Form Submission fires for every response, including a second response from someone already on your list. Pick one of the two for the same job, or a signup can run two scenarios.

### What happens if I revoke the key or disconnect Make?

LaunchList stops sending events to your scenarios and removes their triggers. Make has no way for LaunchList to pause a scenario, so your scenarios simply stop getting events, and their LaunchList steps fail. To start again, create a new key from the Make row, connect LaunchList in Make with it, and create each trigger's webhook again.

### What happens to my scenarios if I change plans?

On a plan without the app, LaunchList stops sending events to your scenarios and keeps their triggers, and LaunchList steps fail with a message that names the plans. Move back to the Launch plan or the Grow plan and the triggers start again. Events from the time in between are not sent later.

### Why did a trigger stop after a few days?

Make switches off a webhook that has not been in any scenario for 5 days, and LaunchList then stops sending to it. Adding that webhook to a scenario later does not bring it back. Create a new webhook in the LaunchList trigger instead.

### Do I need a paid Make plan?

That depends on Make, not on LaunchList. Check what your Make plan allows, such as how many credits a month you get, before you build a longer scenario.

### Does LaunchList work with n8n?

Yes, through a webhook, on every plan. Start the workflow with a Webhook node set to POST, add that URL to LaunchList as a webhook endpoint and pick the events to send.

## Related

- [Make in the docs](https://app.getlaunchlist.com/help/docs/plugins/make): Every trigger and action, step by step, with what to do when a scenario stops getting events.
- [Zapier](https://getlaunchlist.com/plugins/zapier): The same triggers and actions, as an official app on Zapier.
- [The webhook guide](https://app.getlaunchlist.com/help/docs/plugins/webhook): Payloads, headers, signatures and retries in full.