Resources · Make integration

Comeet Make integrationAutomate Comeet with Make.

Need your open Comeet roles somewhere else, without copying them by hand? The Comeet Make integration gives you 4 modules: 2 actions and 2 searches that read positions. This page shows HR and ops teams how to connect Comeet and build a first working scenario.

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Comeet Make integration do for you?

The Comeet Make integration lets a Make scenario read the positions you publish in Comeet and hand them to other tools. A scenario is the automation you build in Make, a chain of modules, and a module is one brick of that chain: here, a search or an action on Comeet.

A careers page that stays in sync. Make describes Get a Specific Position as a module that fetches a role using a position UID supplied by a Webflow response. So when another app hands your scenario a UID, Comeet returns that one position, ready to map into the next module.

A full list of what is live. List Positions gets every position currently published in Comeet. Each role arrives as its own bundle, meaning one item passed from module to module, so you can send a digest to a recruiting channel or fill a spreadsheet row by row.

Anything the modules skip. Make an API Call reaches any endpoint of the Comeet API with the same connection, which covers needs the three other modules leave open.

What Make does not do here: Comeet has no trigger in Make, so nothing fires on its own when a role changes. Your scenario starts on a schedule, or on a trigger from another app. The Comeet documentation on Make also warns that its content is AI-generated and may contain mistakes, so check important details with Comeet. If you want a second opinion on the platform itself, read the Make review; if you are still choosing a tool, the n8n vs Make comparison lays out the criteria, and Make training helps a team build this kind of flow alone.

Connect

How do you connect Comeet to Make?

  1. 01

    Find your Comeet credentials

    In Comeet, open Settings from your avatar at the top right, go to Sourcing, then Careers Website. Scroll to Integrated website, find Careers API, and copy both the API token and the UID shown there.

  2. 02

    Open the connection window

    In a Make scenario, add any Comeet module and click Create a connection. A connection is your Comeet account linked to Make once, then reused by every Comeet module you add later.

  3. 03

    Paste and save

    Optionally give it a clear label in Connection name, such as the company or workspace it points to. Then paste the credentials you copied from Comeet and confirm. Make can now read your positions.

First scenario

Your first scenario with Comeet

GoalWhen another app sends a position UID, Make fetches that position from Comeet and passes its details on.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the +. Pick the app that holds the position UID, such as your website builder, and set up its first module.

  2. 02

    Add the Comeet module

    Click the + on the right of that first module, search for Comeet and choose Get a Specific Position. Select the connection you created, or click Create a connection if this is your first Comeet module.

  3. 03

    Map the UID

    In the module fields, map the position UID coming from the previous module instead of typing it. That way each run asks Comeet for the exact role the other app pointed to.

  4. 04

    Test with Run once

    Click Run once to execute the scenario a single time. Then read the bundle Get a Specific Position received, to check that the right position came back.

  5. 05

    Schedule and switch on

    Set the schedule on the first module; a new scenario runs every 15 minutes by default. Then switch the scenario on. Each module run counts as one operation on your Make plan.

Modules

What each Comeet module does

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

Comeet1

Get a Specific Position

Action

In Make“Gets a specific position from Comeet, using position UID supplied by Webflow response.”

Hands your scenario the details of a single Comeet position once you know its UID, so the next module can publish or store that role.

When to use it
another app, such as a site built on Webflow, already sends the position UID and you need the matching record from Comeet.
Watch out
the module needs a UID to work with; without one mapped from an earlier step, there is nothing for it to look up.
Comeet2

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Opens the whole Comeet API to your scenario, using the same connection as the other modules, so you are not stuck with only three ready-made moves.

When to use it
the task you have in mind is not covered by the listing or lookup modules and you know which Comeet endpoint handles it.
Watch out
you write the request yourself here, so keep the Comeet API documentation open while you fill it in.
Comeet3

Get a Specific Position - Private

Search

In Make“Gets specific position from Comeet, using position UID supplied by Webflow response.”

Returns one position from Comeet based on a UID, and Make labels it as a search, so the result arrives as a bundle you can filter or route like any search output.

When to use it
you are building a lookup from a UID and want the private variant listed next to the standard one.
Watch out
the documentation does not explain how it differs from the public module, so run both once and compare the bundles before picking.
Comeet4

List Positions

Search

In Make“Gets all the positions currently published in Comeet.”

Brings back every role currently published in Comeet, one bundle per position, which gives you the full picture of what candidates can apply to right now.

When to use it
you want a recap for the hiring team or a sheet that mirrors your open roles.
Watch out
each returned position flows on as its own bundle, so every module after it runs once per role and counts operations accordingly.
Need help

Need help automating Comeet with Make?

A person reads every message.

FAQ

Comeet and Make: common questions

01Is the Comeet Make integration free?
Yes, on the Make side. Comeet is a standard app, available from the Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between scheduled runs, up to 5 minutes per execution, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams, Enterprise) lower the interval to 1 minute and remove the cap on active scenarios. You still need your own Comeet subscription, which Make does not cover; check the Comeet pricing page for that part.
02What do you need to connect Comeet to Make?
An active Comeet account with access to an API key. The credentials live in Comeet under Settings, then Sourcing, then Careers Website: scroll to Integrated website, find Careers API, and copy the API token and the UID. In Make, add a Comeet module, click Create a connection, optionally name it, and paste those two values. The connection is then reused by every Comeet module in your scenarios, so you only do this once per account.
03Does the Comeet integration in Make react in real time?
No. Comeet has no trigger in Make, neither scheduled nor instant, so Make is never told when a position changes. You start the scenario another way: with the schedule on its first module, every 15 minutes by default and down to 1 minute on paid plans, or with a trigger from another app that then passes a UID to Get a Specific Position. For a regular snapshot, a scheduled scenario that opens on List Positions is the simplest route.
04What if the Comeet module you need is missing in Make?
Use Make an API Call. It sends a request to any endpoint of the Comeet API with the connection you already have, so you are not limited to the three other modules, which only read positions. You will need to know which endpoint to call and what it expects. Keep in mind that the Comeet documentation on Make is flagged as AI-generated and may contain mistakes, so confirm important details with Comeet directly.
05Should you use Make or n8n for Comeet?
It depends on the tool your team already runs. On Make, Comeet comes with 4 modules: List Positions, two ways to get one position by UID, and Make an API Call for the rest. The same app often has an n8n node as well, so check what each tool offers for Comeet before you commit. The deciding criteria are the ones you use for every app: who builds the scenarios, which other tools they connect to, and whether they already work in Make every day.