Crisphive

Works with Zapier

Early access
Zapier

A job gets confirmed in Crisphive — your Zap already knows.

Trigger a Zap on any job or customer event, or book jobs from any Zap. Signed webhooks fire the moment it happens; no polling.

Start freeGet the Crisphive app for Zapier (invite)

Three Zaps teams build first

job_request.confirmedEmail

Job confirmed → email the office

Technician, window and address land in the dispatcher’s inbox the moment the solver confirms.

job_request.completedSMS

Job completed → send the review request

When the technician closes the job, the customer gets your review link from the tool you already use.

customer.createdCRM

New customer → add to your CRM

A caller the agent has never seen becomes a CRM contact before the first visit.

Triggers, actions and searches

Triggers

  • New JobA job request is created from any channel.
    job_request.created
  • Job ConfirmedThe solver confirmed a technician and window.
    job_request.confirmed
  • Job AssignedA job moved to a named technician.
    job_request.assigned
  • Job CompletedThe technician closed the job.
    job_request.completed
  • Job RescheduledThe window or technician changed.
    job_request.rescheduled
  • Job ArchivedA job was removed from the active board.
    job_request.archived
  • Job Priority ChangedA coordinator raised or lowered priority.
    job_request.priority_changed
  • Customer CreatedA new customer record exists.
    customer.created
  • Customer UpdatedContact details or address changed.
    customer.updated
  • Customer DeletedA customer record was deleted.
    customer.deleted

Actions & searches

  • Find Customer by PhoneReturns the matching customer, or nothing.
    customer.find_by_phone
  • Book JobBook-and-confirm into a slot the solver can keep.
    job_request.book_and_confirm
  • Get JobFetch a job with its technician and window.
    job_request.get

Setup — Copy link to this sectionLink copied

Connect in five steps

Test with a Rehearsal job. Nothing reaches a real customer until you publish on a live key.

  1. 1

    Open the Crisphive app invite on Zapier (link below).

  2. 2

    Create a Zap, trigger “New Event → Job Confirmed”.

  3. 3

    Connect your Crisphive account (OAuth consent).

  4. 4

    Add your action — Email, Slack, Sheets, your CRM.

  5. 5

    Test with a Rehearsal job, publish.

Open the Crisphive app invite on Zapier →Full guide with screenshots on docs.crisphive.com →

  • Signed webhooks with replay and an event log.

  • Fires at the moment of the event — no polling.

  • Rehearsal first — nothing reaches a real customer.

Questions

Why is the app “early access”?
The Crisphive app is invite-only while it is under Zapier’s review. Use the invite link on this page; signed webhooks work today without it.
Which events can trigger a workflow?
Every job event — created, confirmed, assigned, completed, rescheduled, archived, priority changed — and customer created, updated and deleted.
Can a workflow book a job?
Yes. The Book Job action finds or creates the customer and books-and-confirms into a slot the solver can keep.
Does Crisphive do invoicing or inventory?
No — your workflow hands the event to the tool that does. Crisphive owns the schedule; QuickBooks, your CRM or your sheet own the rest.
Is Live mode different from Rehearsal?
Same triggers, same actions. Rehearsal fires on sample data with a chsk_test_ key; Live fires on your real board with your live key.

Your office knows before the tech leaves.

Start free

Predictable by design