es
Esta guía aún no está disponible en tu idioma. Estás leyendo la versión en inglés.

Connect Zapier, Make and n8n

Book jobs in Crisphive and react to its events from the automation tool your team already uses — with no code, or very little.

Zapier and Make connect by signing in to Crisphive and act as the member who connected; n8n uses a secret API key. All three call the same public API, so what one can do, the others can too. Each guide lists every field to fill in; the facts below apply to all of them.

What every platform shares

  • One call books and confirms. POST /v1/job-requests/book-and-confirm creates the job, sizes it from the job type’s default duration (or the duration you send) and confirms it at scheduled_at — the business’s local wall clock with no timezone offset, for example 2026-10-06T10:00:00. Crisphive picks the technician. Every job type an automation may book needs a default duration (Settings → Job Types).
  • Send the customer and the address, not a customer ID. An existing customer is matched by phone or email and never duplicated, and the job uses the address you sent.
  • confirmed: false is not an error. The job is saved in the coordinator queue and refusal says why no technician could take that time. Do not book it again.
  • Retries never book twice when the request carries an Idempotency-Key built from the triggering record: the same request with the same key replays the first answer. Change anything in the request and it needs a new key.
  • Triggers are webhooks the platform subscribes when you turn a trigger on and removes when you turn it off, signed with Crisphive-Signature — see Webhooks. A business can have 25 active webhooks per environment.
  • Who may turn on a trigger. With Zapier and Make, the member who connected needs Developer access (by default only the Owner). With n8n, the API key needs developer_view and developer_manage_api_keys as well as the booking scopes, plus team_view for technician events.
  • Connections and keys expire. A Zapier or Make connection lasts 90 days by default: right after connecting, the Owner sets it to 365 days under Settings → Developer → MCP connections → Set lifetime (that page lists every app connected by signing in, not only AI apps). An n8n key lasts 30 days by default, up to 365.
curl -X POST "https://api.crisphive.com/v1/job-requests/book-and-confirm" \
  -H "Authorization: Bearer chsk_test_4eC8xQ9mZ2pL7Ka0rT" \
  -H "Idempotency-Key: form-submission-4815" \
  -H "Content-Type: application/json" \
  -d '{"customer":{"full_name":"Alex Martin","phone":"+16135550177","email":"alex.martin@example.com"},"address":{"line":"145 Laurier Avenue West","city":"Ottawa","state":"ON","postal_code":"K1P 5J3","country":"CA"},"scheduled_at":"2026-10-06T10:00:00"}'

More: Webhooks · Book and confirm a job · Voice agents · AI assistants