Resources · Make integration

CometAPI Make integrationAutomate CometAPI with Make.

Can Make send your data to CometAPI without a line of code? Yes: the CometAPI Make integration gives you 3 modules, two actions and one search, on every plan including Free. This guide links your API key, builds a first scenario and explains when to pick each module.

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the CometAPI Make integration do?

The CometAPI Make integration links your CometAPI account to Make, so CometAPI's AI service becomes one step of a scenario, the automation you build in Make as a chain of modules. You paste an API key once, then data coming from your other apps can flow into CometAPI and back out.

Pass a text to CometAPI where it lands. A support tool, a form or a spreadsheet catches something new, and the Create a Chat action picks it up in the same scenario. Each item that moves between modules is a bundle: one message, one row, one entry.

Check what your account can reach. List Models is a search: it can return zero, one or several bundles, and whatever comes after it runs once per bundle. Place it first when a later step needs that list.

Keep a door open for the rest. Create an API Call is the second action of the app. The Make doc gives it no description, so open it in the editor before you plan a scenario around it.

What the integration does not do: it has no trigger, so CometAPI never starts a scenario by itself. Another app or the schedule does that job. The doc page for this app is flagged as AI-generated, and it asks you to verify important details with CometAPI. The same app often has an n8n node too; the n8n vs Make page lays out how the two tools differ, and the Make pricing page explains how operations are counted.

Connect

How do you connect CometAPI to Make?

  1. 01

    Copy an API key from CometAPI

    Sign in to your CometAPI account and open the API Token section of the console. Click Add Token, then copy the key that appears on screen. Make needs an active CometAPI account for this to work.

  2. 02

    Open a CometAPI module in Make

    In your Make scenario, add any CometAPI module and click Create a connection. A connection is your CometAPI account linked to Make once; every CometAPI module of your scenarios reuses it afterward.

  3. 03

    Paste the key and save

    Give the connection a clear label in Connection name if you like (the field is optional), paste your API key and confirm. Make can now read what your CometAPI account offers when you fill the module fields.

First scenario

Your first scenario with CometAPI

GoalWhen another app records a new message, Make sends it to CometAPI through Create a Chat.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the +. Pick the app where your messages arrive (a form, a helpdesk, a sheet) and choose its module as the first step.

  2. 02

    Add Create a Chat

    Click the + on the right of that first module, search for CometAPI and pick Create a Chat. Select the connection you created, or click Create a connection if this is your first CometAPI module.

  3. 03

    Map the incoming text

    Once the connection exists, Make shows the fields Create a Chat asks for. Where a field takes text, map the text from the first module instead of typing it, so each new bundle carries its own message.

  4. 04

    Test with Run once

    Click Run once to run the scenario one time. Open the bubble above each module to read the bundles it received and check what CometAPI sent back before going further.

  5. 05

    Schedule and switch it on

    Open the clock on the first module to set the schedule, every 15 minutes by default for a new scenario, then switch the scenario on. Each module run on one bundle counts as one operation on your plan.

Modules

What each CometAPI module does

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

CometAPI1

Create a Chat

ActionIn the docs only

Create a Chat hands a piece of your scenario's data to CometAPI and brings the outcome back as a bundle the next module can use. The Make doc gives no description, so once your connection exists, open the module and read which fields it asks for.

When to use it
a message, a form answer or a row from another app should go through CometAPI's AI service before landing somewhere else.
Watch out
every bundle that reaches it costs one operation, so test with Run once on a single item.
CometAPI2

Create an API Call

ActionIn the docs only

Create an API Call is the second action CometAPI puts in Make, and it keeps its own settings separate from Create a Chat. The doc says nothing more about it, so its fields are the only guide to what it covers.

When to use it
Create a Chat does not show a setting your CometAPI request needs, and you want to check whether this module does.
Watch out
it is not Make's universal Make an API Call module, which this app does not offer.
CometAPI3

List Models

SearchIn the docs only

List Models is the only search of the app: it returns what it finds as separate bundles, which can mean zero, one or several items. Its name points to the models your CometAPI account can use; Run once shows you the real output.

When to use it
a later step depends on that list, for example to store it in a sheet from another app.
Watch out
every module placed after a search runs once per bundle, which multiplies operations.
Need help

Need help automating CometAPI with Make?

A person reads every message.

FAQ

CometAPI and Make: common questions

01Is the CometAPI Make integration free?
Yes, on the Make side. CometAPI is a standard app, available from the Free plan. That plan keeps 2 active scenarios, runs a scheduled scenario at most every 15 minutes, stops an execution after 5 minutes and caps transfer at 512 MB. Paid plans lower the interval to 1 minute and allow 40 minutes per execution. CometAPI itself is another matter: the doc asks for an active account and points to the CometAPI pricing page for the subscription. Check that page before you build anything that depends on it.
02What do you need to connect CometAPI to Make?
An active CometAPI account and an API key. In the CometAPI console, open the API Token section, click Add Token and copy the key shown on screen. Then, in Make, add any CometAPI module, click Create a connection, optionally name it, and paste the key. The connection is saved once and reused by every CometAPI module in your scenarios, so you do not repeat this step for each new scenario you build later.
03Does the CometAPI Make integration react in real time?
No, because CometAPI has no trigger in Make. Nothing in CometAPI can start a scenario by itself. You start it in one of two ways. Put another app's trigger in first position, for example a form or a helpdesk that receives new entries, and let Create a Chat follow it. Or run the scenario on the schedule set on the first module, every 15 minutes by default, down to 1 minute on paid plans. Either way, CometAPI acts when the scenario reaches it.
04What if the CometAPI module you need is missing?
Start by opening Create an API Call, the second action of the app, and read the fields it offers. CometAPI does not have Make's universal Make an API Call module, so you cannot count on it to reach every part of the service. Keep in mind that the doc for this app is flagged as AI-generated and may contain mistakes; confirm important details with CometAPI directly. If the modules still fall short, another app may cover the step, or the team can look at your case with you.
05Should you use Make or n8n for CometAPI?
It depends on your setup, and this page does not rank the two. On Make, CometAPI brings 3 modules, two actions and one search, available from the Free plan, with no trigger and no Make an API Call module. The same app often has an n8n node as well, so compare the modules each side offers against the steps you actually need. The n8n vs Make comparison page, linked higher on this page, sets the two tools side by side if you want a broader view.