Ce guide n’est pas encore disponible dans votre langue. Vous lisez la version anglaise.

Connect Crisphive to Make

Dernière mise à jour le 30 octobre 2026

Configurez-le avec votre assistant IA

De quoi s’agit-il: Un fichier de configuration : ce guide Make réécrit sous forme d’instructions pour ChatGPT, Claude ou tout autre chat IA.
Pourquoi l’utiliser: Seul, un assistant IA ne fait que deviner comment connecter Crisphive à Make, de mémoire, et cette mémoire peut être fausse ou dépassée. Avec ce fichier, il suit exactement ce guide et vous accompagne étape par étape : il vous demande où vous en êtes, vous dit exactement où cliquer et vérifie le résultat avec vous.
Ce qu’il contient: Chaque étape de cette page, avec les écrans, boutons et valeurs actuels
Des règles pour l’assistant : une étape à la fois, commencer en Rehearsal, finir par le test
Des liens vers cette page et vers le support Crisphive
Est-ce sûr ?: Oui. C’est du texte brut (Markdown) — aucun programme, rien à installer, aucune clé. Utilisez Aperçu pour le lire dans votre navigateur avant d’enregistrer quoi que ce soit.

Le fichier est en anglais. Ne collez jamais de clé API ni de mot de passe dans le chat.

By the end of this guide, each time a job is confirmed in Crisphive, Make sends one email from your Gmail to your office within a few seconds — with the customer, the visit time in your local time, the technician, the address, the job type and the job code.

Make is a visual automation tool: a scenario is a chain of modules, each one a step in an app, run from left to right. Crisphive is a field operations platform: constraint-based scheduling on a deterministic solver that books each job and assigns the right technician automatically — and it is manageable from Claude or ChatGPT too. The Crisphive app for Make connects the two.

To add the Crisphive app to your Make account, email support@crisphive.com and we’ll send you the invite link.

What you will have at the end

One email per confirmed job, sent from your Gmail. It looks like this:

Subject: Job confirmed: REQ-CA-8K2M4Q7X

Customer: Alex Martin
Phone: +16135550177
When: Wednesday, October 14, 2026 10:00 AM
Technician: Jordan Lee
Address: 145 Laurier Avenue West, Ottawa
Job type: General
Job: REQ-CA-8K2M4Q7X

The scenario has three modules, left to right. It takes about 15 minutes to build.

Crisphive — Watch events  →  Crisphive — Get a job  →  Gmail — Send an email

Why Get a job? Watch events hands Make only three fields of the job: id, status and short_code. The customer, schedule, address and technician come from Get a job, which reads the job back by its ID. Reading the job back is also the safe pattern: Make receives the event already parsed, so it cannot check Crisphive’s webhook signature, and Get a job returns the real data from Crisphive.

Before you start

You need	Notes
A Crisphive login as Owner	Turning on an event trigger needs the Owner role, or a role the Owner gave the Developer module.
The Crisphive Make invite link	Email `support@crisphive.com` and we’ll send it to you.
A Make account	The Free plan is enough for this scenario. Each run uses 3 operations (one per module).
A Gmail (or Google Workspace) account	The email is sent from this mailbox.

Test in Rehearsal first. Make then sees only test data. In the left sidebar of the Crisphive dashboard, click Rehearsal in the Rehearsal | Live switch, then click Switch. Rehearsal is Crisphive’s sandbox: isolated test data, and no real customer or technician is ever texted or emailed. The connection works in the environment your dashboard is in at the moment you click Approve.

Step 1 — Install the Crisphive app on Make

Open the invite link

If you are not signed in, Make shows its Sign in page. Sign in, or click Sign up and create an account.

Answer the Welcome survey (new accounts only)

A new account goes through a short Welcome survey first: What would you like to automate?, How would you describe your technical experience?, What apps do you use the most? (Skip is offered), What size is your workplace? and How did you discover Make?.

Install into your organization

Make shows the Crisphive app page: “You are installing application Crisphive, select organizations to which you want to install the application.” Tick your organization (for a new account: My Organization) and click Install.

Go to the dashboard

The page reads Crisphive installed successfully. Click Go to dashboard.

If the app page says “No modules have been created in the app yet or they have a private status…”, the app is not ready for your account yet. Email support@crisphive.com.

Step 2 — Create the scenario and the trigger (Watch events)

In this step you create the webhook that listens for confirmed jobs, and — inside the same box — the connection to your Crisphive account. Make connects with sign-in and approval: you never paste a password or an API key into Make.

Étape 1 sur 4On the dashboard click Create scenario. Click the big +, type Crisphive and click Watch events (badge Instant). Under Webhook, click Create a webhook.

Toutes les étapes

On the dashboard click Create scenario. Click the big +, type Crisphive and click Watch events (badge Instant). Under Webhook, click Create a webhook.
In the Create a webhook box, type a Webhook name you will recognise, for example Crisphive job confirmed.
Next to Connection, click Create a connection. A Create a connection box opens.
Type a Connection name that says which environment it is, for example Crisphive sandbox. Leave Advanced settings off, then click Save. A Crisphive window opens.

Étape 1 sur 2If you are not signed in to Crisphive in this browser, type your email and click Send Verification, then type the 6-digit code from the email in Enter your code.

Toutes les étapes

If you are not signed in to Crisphive in this browser, type your email and click Send Verification, then type the 6-digit code from the email in Enter your code.
The Authorize Make page shows your business name, the mode (Rehearsal or Live) and who you are signed in as. In Rehearsal it says Make will only see Rehearsal (test) data. Use Switch or Connect Live instead if the business or mode is wrong. Click Approve.

Étape 1 sur 2Back in Make, Connection shows Crisphive sandbox and a new Event field appears. Open it and choose job_request.confirmed.

Toutes les étapes

Back in Make, Connection shows Crisphive sandbox and a new Event field appears. Open it and choose job_request.confirmed.
Click Save in the Create a webhook box. The module shows the webhook name and a Webhook URL. Click Save on the module.

Create the scenario

On the dashboard, click Create scenario (top right). The editor opens on an empty canvas with a large +. If a Build with Maia panel opens on the left, close it with ×.

Add Watch events

Click the big +, type Crisphive, and click Watch events (badge Instant).

Create a webhook

In the module, under Webhook, click Create a webhook. In the Create a webhook box, type a Webhook name, for example Crisphive job confirmed.

Create the connection inside the webhook box

Next to Connection, click Create a connection. Type a Connection name that says which environment it is, for example Crisphive sandbox (Make suggests “<your account name>’s Crisphive connection”). Leave the Advanced settings switch off: it only reveals Additional scopes, and an empty value gives the connection the same access as your Crisphive role. Click Save. A Crisphive window opens — allow pop-ups for make.com if nothing appears.

Authorize Make

In the Crisphive window, sign in if asked. The Authorize Make page shows your business name, the mode (Rehearsal or Live) and who you are signed in as. In Rehearsal it says Make will only see Rehearsal (test) data — not your real jobs, customers or team. Use Switch or Connect Live instead if that is the wrong business or mode. Click Approve.

Choose the event

Back in Make, Connection shows Crisphive sandbox and a new field, Event, appears. Open it and choose job_request.confirmed. The list is read live from Crisphive and shows 14 events by their codes, for example job_request.created, job_request.confirmed, job_request.completed, customer.created.

Save

Click Save in the Create a webhook box. The module now shows the webhook name and a Webhook URL (https://hook.<zone>.make.com/…). Click Save on the module.

Name the scenario

Make renames the scenario to Integration Crisphive. Click the name at the top left, type for example Crisphive: email the office when a job is confirmed, and press Enter.

Step 3 — Load a real event (Run once)

Make needs one real event before it can offer the job’s fields for mapping.

Start listening

Click Save in the bottom toolbar, then Run once. The log reads The request was accepted. Waiting for data.

Confirm a job in Crisphive

Confirm a job (in Rehearsal if you are testing). A job booked with Book and confirm fires straight away.

Open the bubble

Within a few seconds the Watch events module shows a 1 bubble. Click it: Bundle 1 has Event type job_request.confirmed, an Object with id, status and short_code, an Event ID and Created at.

Step 4 — Read the full job (Get a job)

Étape 1 sur 2Click the small + on the right of Watch events, type Crisphive and click Get a job. Connection already shows Crisphive sandbox.

Toutes les étapes

Click the small + on the right of Watch events, type Crisphive and click Get a job. Connection already shows Crisphive sandbox.
Click Job ID. In the mapping panel, under Object, click id. The field shows 1. object: id. Click Save.

Add Get a job

Click the small + on the right of the Watch events module, type Crisphive, and click Get a job.

Connection

Crisphive sandbox is already selected.

Job ID

Click the field. The mapping panel opens on the side. Under Object, click id. The field shows 1. object: id.

Save

Click Save.

Step 5 — Send the email (Gmail)

Add Send an email

Click the + on the right of Get a job, type Gmail, and click Send an email.

Connect Gmail

Next to Connection, click Create a connection, then Sign in with Google. Choose the Google account that will send the email.

On Google’s permission screen, tick every box (or Select all) before you click Continue. If the box that lets Make send email on your behalf is left unticked, the connection is still created, but the email step fails later with [403] Request had insufficient authentication scopes. See Troubleshooting.

Fill the fields. To insert a value, click the field and click it in the mapping panel (fields of Crisphive 2 - Get a job), or paste it in the {{…}} form shown below.

Field	What to put
To → Recipient email address 1	Your office email address.
Subject	`Job confirmed:` then Short code.
Body type	Leave Raw HTML.
Content	The block below.

Copy all of this and paste it into Content in one go; Make turns each {{…}} into a value:

Customer: {{2.customer.name}}<br>Phone: {{2.customer.phone}}<br>When: {{formatDate(2.schedule.scheduled_at; "dddd, MMMM D, YYYY h:mm A"; 2.schedule.business_timezone)}}<br>Technician: {{2.assignment.technician.full_name}}<br>Address: {{2.address.line}}, {{2.address.city}}<br>Job type: {{2.job_type_name}}<br>Job: {{2.short_code}}

Paste it, do not type it. Typed character by character, Make turns formatDate( into a function but leaves the arguments as plain text, and the email shows the formula instead of a time.

formatDate(…; 2.schedule.business_timezone) turns the start time into your business’s local time. Crisphive sends times in UTC: 2026-10-14T14:00:00Z becomes Wednesday, October 14, 2026 10:00 AM for a business in America/Toronto.
Technician shows with a white outline instead of orange: the field is not listed in the mapping panel yet, but it is filled when the scenario runs.

Étape 1 sur 2Fill Recipient email address 1 with your office address and Subject with Job confirmed: followed by Short code from Get a job.

Toutes les étapes

Fill Recipient email address 1 with your office address and Subject with Job confirmed: followed by Short code from Get a job.
Leave Body type on Raw HTML and paste the whole Content block in one go. Click Save, then Save in the bottom toolbar.

Click Save, then Save in the bottom toolbar.

Step 6 — Test, then turn it on

Run once

Click Run once and confirm another job in Crisphive. All three modules get a green tick and a 1 bubble. Click the Gmail bubble to see the Subject and Content that were sent, and check the inbox.

Turn it on

Turn on the switch next to Inactive (top right). It reads Active, next to Immediately as data arrives.

Check a live run

Confirm one more job. The scenario’s History tab shows a run with Instant and Success.

On the Crisphive side, Settings → Developer → Webhooks (crisphive.com/app/settings/developer/webhooks) lists an endpoint on hook.<zone>.make.com named Make: job_request.confirmed, status Active, with a secret that expires one year after you created it.

Templates

Ready-made automations you import instead of building. Each card says what the template does, what is inside and why it is safe before you take it.

Website form → confirmed job

De quoi s’agit-il: A Make scenario (blueprint) you import instead of building: a booking form on your website books and confirms the visit in Crisphive, then tells your website the result.
Pourquoi l’utiliser: It is the automation business owners ask for most, already built and tested end to end. You create its webhook, add your key and turn it on — no modules to wire up.
Ce qu’il contient: Webhook — the address your website form sends to
HTTP — the Crisphive booking request (book and confirm)
Router — splits on whether a technician could take the time
Two Webhook response modules — the answers your website gets back
Est-ce sûr ?: Yes. It is a plain JSON text file that only describes the five modules and their settings — no program code and no real key, only the placeholder chsk_test_PASTE_YOUR_KEY_HERE that you replace with your own.

Aperçu

To use it:

Import the blueprint

Create a new scenario. Click the ⋮ menu (top right), then Import blueprint → Choose JSON blueprint, pick the file you downloaded and click Import blueprint.

Create its webhook

Open the Webhook module, click Create a webhook, then Save. Copy the webhook address Make shows — your website form sends to it.

Add your Crisphive key

Open the HTTP module. In the Authorization header, replace chsk_test_PASTE_YOUR_KEY_HERE with your own Rehearsal key, keeping Bearer in front of it. If your business is not in Canada, change "country": "CA" in the request body.

Save and turn it on

Click Save. The schedule shows Immediately as data arrives; switch the toggle from Inactive to on.

Point your website form at it

Make your form POST to the webhook address (form-encoded or JSON) with these field names: full_name, phone (E.164, for example +16135550142), email, street_address, city, postal_code, preferred_date (YYYY-MM-DD), preferred_time (HH:MM, your business’s local time) and description.

Your website receives one of two JSON answers. When a technician can take that time:

{"booked": true, "reference": "REQ-CA-CM3JECHN", "message": "Your visit is booked. Your booking reference is REQ-CA-CM3JECHN."}

When nobody can take it (for example a day your team does not work), the job is still saved for your team to confirm:

{"booked": false, "reference": "REQ-CA-QNE44JAG", "message": "Thanks, we have your request (REQ-CA-QNE44JAG). Our team will call you to agree on a time."}

This scenario uses Make’s own HTTP module, not the Crisphive app, so it needs no app install. The key is stored in the scenario, so anyone who can edit the scenario can see it: use a restricted key with only customers_view, customers_manage, job_view, job_create and job_manage.

What the app can do

The Crisphive app for Make has five modules: Watch events (instant trigger), Get a job, Book and confirm a job, Search customers and Make an API call. This guide uses the first two. Book and confirm a job calls POST /v1/job-requests/book-and-confirm; the API reference describes every field it accepts.

Good to know

One event per webhook. The Watch events webhook listens to the one event you chose. For another event (for example job_request.completed), create a second scenario or webhook.
The customer’s email is in Get a job only if the customer has one. Customers created from a phone call often have only a phone number.
The webhook lasts one year. Crisphive gives the webhook a 365-day signing secret. The Owner and Administrators get an email 7 days before it ends.
Connections live under Credentials. The left menu → Credentials → Connections lists Crisphive sandbox and the Gmail connection, each with Reauthorize and Verify.
Removing access. The Owner can disconnect Make for everyone under Settings → Developer → MCP connections; the webhooks it created stop with it. Removing or suspending the member who connected Make also stops the connection.

Then set the connection to last a year. A new connection lasts 90 days. So that Make does not stop on that day, the Owner sets it to 365 days right after connecting. Settings → Developer → MCP connections (crisphive.com/app/settings/developer/mcp-servers) lists every app connected by signing in to Crisphive, not only AI apps, so Make appears there.

Open MCP connections

In the Crisphive dashboard go to Settings → Developer → MCP connections and find the Make row.

Set lifetime

Click Set lifetime, enter 365 in Lifetime (days) and click Save. The days count from when Make was first authorized, not from today.

Troubleshooting

You see	Do this
Gmail step: [403] Request had insufficient authentication scopes	Google’s permission boxes were not all ticked. Open Credentials → Connections → your Gmail connection → Reauthorize, tick every box, click Continue. Then click Run once again.
Invite page: No modules have been created in the app yet or they have a private status…	The app is not ready for your account. Email `support@crisphive.com`.
Watch events never gets a bundle	The job is not confirmed yet, or you chose a different Event. Run once listens for one event, then stops.
When shows the wrong hour	Use `2.schedule.business_timezone` as the third argument of `formatDate`, not a fixed time zone.
When shows `formatDate(` as text	The Content was typed instead of pasted. Clear the field and paste the whole block again.
Creating the trigger fails with a permission error	You are not the Owner. Ask the Owner, or have them grant the Developer module to your role in Settings → Permissions.
The Crisphive connection asks to be reauthorized (`OAUTH_GRANT_EXPIRED`)	The connection reached its lifetime or was disconnected in Crisphive. Open Credentials → Connections, click Reauthorize on the Crisphive connection, sign in and click Approve.

Automation platforms overview — what every automation integration shares
Zapier — book jobs from any Zap; instant job and customer triggers
n8n — the verified Crisphive node on n8n Cloud or self-hosted, plus n8n AI Agents
Webhooks reference — events, signatures and retries
Book and confirm a job — the API call behind every booking step

FAQ

How do I add Crisphive to my Make account?

Email support@crisphive.com and we’ll send you the invite link. Open it while signed in to Make, tick your organization and click Install.

Do I need a paid Make plan?

No. The Free plan is enough for this scenario. Each run uses 3 operations, one per module.

Do I need an API key to use Crisphive in Make?

No. Make connects by signing in to Crisphive and clicking Approve on the Authorize Make page.

Why do I need Get a job after Watch events?

Watch events carries only the job’s id, status and short_code. Get a job reads the full job — customer, schedule, address, technician — back from Crisphive.

Why does the email show the wrong time?

Crisphive sends times in UTC. Wrap the start time in formatDate with 2.schedule.business_timezone as the third argument, as in the Content block above.

Who can turn on Watch events?

The business Owner, or a member whose role the Owner gave the Developer module.

‹ PrécédentZapier

Suivant ›n8n

SUR CETTE PAGE

What you will have at the end Before you start Step 1 — Install the Crisphive app on Make Step 2 — Create the scenario and the trigger (Watch events)Step 3 — Load a real event (Run once)Step 4 — Read the full job (Get a job)Step 5 — Send the email (Gmail)Step 6 — Test, then turn it on Templates What the app can do Good to know Troubleshooting Related guides and reference FAQ