Connect HailMate to thousands of apps

Two building blocks#

For both you need an API key: in HailMate open Settings → Integrations → API & Webhooks and press New key. Give each tool its own key, so revoking one never breaks another, and use a read-only key for anything that only reads.

Zapier#

Trigger: Webhooks by Zapier → Catch Hook#

1. Create a Zap. For the trigger choose Webhooks by Zapier, event Catch Hook, and copy the webhook URL Zapier shows you.
2. In HailMate, open Settings → Integrations → API & Webhooks, add a webhook, pick the event and any filters, and paste that URL. (Or subscribe it with POST /webhooks.)
3. Press Send test in HailMate, then Test trigger in Zapier. The record’s fields arrive at the top level of the delivery, ready to map.

Action: Webhooks by Zapier → Custom Request#

The simpler GET and POST actions work too — for POST, set Payload Type to json. Webhooks by Zapier is one of Zapier’s premium apps, so check that your Zapier plan includes it.

Make#

Trigger: Webhooks → Custom webhook#

1. Add a Webhooks module, choose Custom webhook, add a new webhook and copy its address.
2. Add that address as a webhook in HailMate, as for Zapier.
3. With the module waiting for data (Redetermine data structure), press Send test in HailMate. Make learns every field from the delivery.

Action: HTTP → Make a request#

• URL https://app.hailmate.ai/api/v1/… and the Method.
• Headers: Authorization = Bearer hm_live_….
• Body type Raw, Content type JSON (application/json), and the JSON in Request content.
• Turn on Parse response so later modules can map the answer’s fields, such as the new job’s id.

n8n#

Trigger: Webhook node#

1. Add a Webhook node with HTTP method POST.
2. Give HailMate the node’s Production URL — the Test URL only answers while the editor is listening — and activate the workflow.
3. To check signatures, turn on the node’s raw-body option and compare an HMAC-SHA256 of <t>.<raw body> (a Crypto node) with the v1 in X-HailMate-Signature. How signing works.

Action: HTTP Request node#

• Authentication: Generic credential type → Header Auth, with name Authorization and value Bearer hm_live_…. The key is then stored as a credential, not pasted into every node.
• Send Body on, Body Content Type JSON.
• For lists, the node’s Pagination option can follow next_cursor for you: send it back as the cursor query parameter until it comes back empty.

Tips that save an afternoon#

• Filter in HailMate, not in the tool. A webhook filter such as {"stage": "Claim Approved"} means the automation only runs when it should — a cleaner run history, and no runs spent on events you throw away.
• Map fields from a real delivery. Send test in Settings, or GET /webhooks/samples/job.created, shows every field before anything real has happened.
• Search before you create. GET /contacts/search matches a phone number however it was typed, so a form lead who is already a homeowner in HailMate is found rather than duplicated.
• Send an Idempotency-Key built from something stable in the trigger, such as the form submission id. When the tool retries a step, HailMate replays the first answer instead of making a second job.
• Send stages by label. "stage": "Inspection Scheduled" works as well as the key.
• Appointment times are wall-clock. due_date has no time zone; show it as it is. A formatter step that assumes UTC will shift it by hours.
• When a step fails, its error names the field that was wrong, and Settings → Integrations → API & Webhooks lists every request a key made, and every delivery, for you to look at.

Recipes#

Eight automations roofers ask for. Each works in Zapier, Make or n8n; placeholders like {{email}} stand for a field mapped from an earlier step.

• Website form → contact and job, without duplicates
• Slack message when a claim is approved
• A Google Sheets row for every signed estimate
• Payments into your accounting app
• Text the crew when a build day is booked
• An “interested” door becomes a lead
• Storm list ready → the mail house
• Tag a new lead with its hail history

{
  "name": "{{name}}",
  "email": "{{email}}",
  "phone": "{{phone}}",
  "address": "{{street}}",
  "city": "{{city}}",
  "state": "{{state}}",
  "postal_code": "{{zip}}"
}

{
  "name": "{{street}}",
  "address": "{{street}}",
  "city": "{{city}}",
  "state": "{{state}}",
  "postal_code": "{{zip}}",
  "homeowner_id": "{{contact_id}}",
  "lead_source": "Website",
  "notes": "{{message}}"
}

✅ {{name}} moved from {{previous_stage_label}} to {{stage_label}}
RCV {{rcv_amount}} · {{assigned_to_name}}
{{url}}

{
  "job_id": "{{id}}",
  "content": "Hail history: {{hail_day_count}} hail days since {{since}}. Largest {{largest_hail_in}} in, most recent {{last_hail_date}}."
}