Resources · Make integration

Common Ninja Make integrationAutomate Common Ninja with Make.

Every quiz answer, booking or chatbot message in a Common Ninja widget can start an automation. The Common Ninja Make integration gives you 6 modules: 5 instant triggers and one API call. This guide links your account and walks you through a first working flow.

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Common Ninja Make integration automate?

The Common Ninja Make integration listens to your widgets. When a visitor books a slot, finishes a quiz, scratches a card, spins a wheel or writes to your AI chatbot, Common Ninja tells Make right away, and Make runs the scenario you built (a scenario is the automation itself: a chain of steps, called modules).

Bookings that reach your team. Watch New Booking Submission fires on each appointment request, so the details can land in your calendar, your CRM or a team chat without anyone copying them by hand.

Quiz results that feed your follow-up. Watch Quiz Submission hands over the answers of each completed quiz. A lead-generation quiz can then log every participant in a spreadsheet or send a follow-up email that matches the result.

Chatbot conversations you can act on. Watch AI Chatbot Submission starts a scenario when someone messages your AI Chatbot, a good entry point for support tickets or a chat log.

What Make does not give you here: there is no ready-made action to create or edit anything in Common Ninja. For that, the Make an API Call module reaches the Common Ninja REST API with the same connection. Access also depends on Common Ninja approving you for its developer program. If you are weighing the options, the n8n vs Make comparison helps, and the Make training covers the basics of the editor.

Connect

How do you connect Common Ninja to Make?

  1. 01

    Get your developer access

    Common Ninja only opens its API to approved developers. Create your Common Ninja account, apply for the developer program and wait for the invitation that gives you your API credentials. Without them, Make has nothing to log in with.

  2. 02

    Add a module and open the connection window

    In your scenario, add a Common Ninja module. A trigger shows Create a webhook first: click it, then Create a connection. You can type a label in Connection name so you recognize this account later.

  3. 03

    Paste the credentials

    Enter the credentials Common Ninja gave you, or follow the instructions shown on screen, then save. The connection (your Common Ninja account linked to Make) now serves every Common Ninja module you add afterward.

First scenario

Your first scenario with Common Ninja

GoalWhen a visitor books through a Common Ninja widget, Make receives the booking and sends a request to the Common Ninja API with it.

  1. 01

    Create the scenario

    Open the Scenarios page in Make, create a new scenario and click the big + to place the first module on the canvas.

  2. 02

    Pick the booking trigger

    Search for Common Ninja and choose Watch New Booking Submission. Click Create a webhook, then link your account with Create a connection.

  3. 03

    Add the API call

    Click the + on the right of the trigger and add Make an API Call. Point it at the Common Ninja endpoint you need and map booking data from the trigger into the request.

  4. 04

    Test with Run once

    Click Run once, then make a test booking in your widget. Each module shows the bundle it received (one bundle is one item, here one booking), so you can check the data before going live.

  5. 05

    Switch it on

    When the test looks right, switch the scenario on. From then on, each booking made in the widget starts one run, and each module that runs counts as an operation on your Make plan.

Triggers

What starts a Common Ninja scenario?

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

Common Ninja1Watch AI Chatbot Submission

Watch AI Chatbot Submission

Instant trigger

In Make“Triggers when a user sends a message to your AI Chatbot. Use this to automate responses, log chats, trigger support tickets, personalize follow-ups, or sync data with tools like Slack, HubSpot, or Google Sheets — all without code. Great for lead capture, support automation, and user engagement.”

Turns every message a visitor sends to your Common Ninja AI Chatbot into the start of a scenario, so a question on your site can open a ticket, reach a support channel or end up in a chat log.

How it fires
instant, Common Ninja calls Make through a webhook as soon as the message is sent.
When to use it
your chatbot answers the easy questions and you want a human to see the ones that deserve a follow-up.
Watch out
the key is spelled aiChatbotSubmmision in Make, with a double m, so search the module by its name rather than by key.
Common Ninja2Watch New Booking Submission

Watch New Booking Submission

Instant trigger

In Make“Triggers when a user submits a booking through a Common Ninja widget. Use this module to automate scheduling workflows — add bookings to your calendar, notify your team, send confirmation emails, or update your CRM. Ideal for appointments, consultations, events, and service-based businesses. Connect effortlessly with Google Calendar, Zoom, Airtable, Slack, and more via Make.com. No coding required — streamline your booking process in minutes.”

Hands Make each booking a visitor submits through a Common Ninja widget, which is the cleanest way to get appointments, consultations or event sign-ups out of the widget and into the tools your team already checks.

How it fires
instant, the app calls Make through a webhook the moment the booking is submitted.
When to use it
a consultant who takes calls through a booking widget and wants each request in a calendar and a CRM record.
Watch out
click Run once and then submit a real test booking, so you can read the bundle Make received before mapping it.
Common Ninja3Watch Quiz Submission

Watch Quiz Submission

Instant trigger

In Make“Triggers when a user submits a quiz through a Common Ninja widget. Use this module to automate actions based on quiz results — store responses in a database, send personalized follow-up emails, notify your team in Slack, or update CRM records. Ideal for lead generation, knowledge checks, and interactive marketing campaigns. Easily connect with tools like Google Sheets, Airtable, Mailchimp, HubSpot, and more. No coding required — just drag, drop, and automate.”

Starts your scenario each time someone completes a quiz in a Common Ninja widget and passes the submission along, so the result can shape what happens next instead of sitting in the widget.

How it fires
instant, Common Ninja notifies Make by webhook as soon as the quiz is submitted.
When to use it
a lead-generation quiz on a landing page, where each participant should reach your email tool with the right follow-up.
Watch out
take the quiz yourself while Run once is waiting, then map the answers from the bundle you see.
Common Ninja4Watch Scratch Card Submission

Watch Scratch Card Submission

Instant trigger

In Make“Triggers when a user completes a scratch card interaction in a Common Ninja widget. Use this module to automate follow-ups based on user participation or prize outcomes — send winning notifications, update loyalty programs, log data in your CRM, or trigger promotional emails. Perfect for gamified campaigns, giveaways, and engagement-driven experiences. Easily integrate with tools like Google Sheets, Mailchimp, Slack, or any other Make.com app — no code needed.”

Reacts when a visitor finishes scratching a card in a Common Ninja widget, giving you the participation and its outcome so a giveaway can reward winners and keep track of everyone who played.

How it fires
instant, the widget tells Make through a webhook once the card is revealed.
When to use it
a promotion where every winner must get a message and every participant belongs in a list for later campaigns.
Watch out
look at the first bundle after Run once before deciding how your scenario tells a winner from a player.
Common Ninja5Watch Spinning Wheel Submission

Watch Spinning Wheel Submission

Instant trigger

In Make“Triggers when a user completes a spinning wheel interaction in a Common Ninja widget. Use this module to automate follow-ups based on user participation or prize outcomes — send winning notifications, update loyalty programs, log data in your CRM, or trigger promotional emails. Perfect for gamified campaigns, giveaways, and engagement-driven experiences. Easily integrate with tools like Google Sheets, Mailchimp, Slack, or any other Make.com app — no code needed.”

Sends Make the result of each spin on a Common Ninja wheel, the moment a visitor completes it, so the prize they landed on can drive the next step: a notification, a loyalty update or a promo email.

How it fires
instant, Common Ninja pushes the spin to Make by webhook right after it ends.
When to use it
a wheel on an online store where the reward should reach the customer and your CRM without manual work.
Watch out
every completed spin starts a run, winning or not, and each module that runs uses an operation on your plan.
Modules

What else can Make do with Common Ninja?

Common Ninja gives you 1 module. For each one: what it does for you, when to reach for it, and what to watch out for.

Common Ninja1

Make an API Call

Action

In Make“Sending custom HTTP requests to any Common Ninja REST API”

Sends a custom request to any endpoint of the Common Ninja REST API, reusing the connection you already created, which is how you cover everything the five triggers do not.

When to use it
you need Common Ninja to do something after an event, and no dedicated module exists for it.
Watch out
you pick the endpoint and build the request yourself, so keep the Common Ninja API documentation open while you set it up.
Need help

Need help automating Common Ninja with Make?

A person reads every message.

FAQ

Common Ninja and Make: common questions

01Is the Common Ninja Make integration free?
Yes, on the Make side. Common Ninja is a standard app, so it works on the Free plan. That plan allows 2 active scenarios, runs of up to 5 minutes, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) remove the cap on active scenarios and allow runs of up to 40 minutes. Usage is counted in operations, one per module run. What Common Ninja charges for its own widgets is a separate question to check with Common Ninja.
02What do you need to connect Common Ninja to Make?
You need a Common Ninja account and approval to its developer program. Common Ninja hands out API credentials by invitation, and those credentials are what you paste into Make when you click Create a connection. For a trigger, Make first asks you to click Create a webhook. Some setups also ask for a widget key, which sits in the settings of each widget in your Common Ninja dashboard. Once the connection exists, every Common Ninja module in your scenarios reuses it.
03Do Common Ninja triggers in Make fire instantly?
Yes. All 5 Common Ninja triggers are instant: Common Ninja calls Make through a webhook as soon as a visitor submits a booking, a quiz, a scratch card, a wheel spin or a chatbot message. Make does not have to check the widget on a timer, so the scenario starts on the event itself. That is also why each trigger needs its webhook, created from the module with Create a webhook before the connection. Test it with Run once and a real submission.
04What if the Common Ninja module you need is missing in Make?
Use Make an API Call. The Make catalog lists 5 triggers for Common Ninja and no ready-made action, so anything beyond catching submissions goes through this module. It calls any endpoint of the Common Ninja REST API with the connection you already have. You write the request yourself, based on the Common Ninja API documentation. Note that Make flags its Common Ninja documentation as AI-generated from the vendor docs, so confirm important details with Common Ninja directly.
05Should you use Make or n8n for Common Ninja?
It depends on what you already run. In Make, Common Ninja comes with 6 modules: 5 instant triggers for the widgets and one API call for everything else, plus a visual editor where you test each step with Run once. Many apps also have an n8n node, so check whether one exists for Common Ninja before choosing. The better option is usually the tool your team already uses for its other automations, so all your flows live in one place.