Skip to content

Outbound Webhooks Setup

When a customer accepts a quote in AirShop, you can automatically send that information to other tools you use — like QuickBooks, Xero, FreshBooks, or any app that can receive webhooks. No coding required if you use Zapier or Make.

What You'll Need

  • An AirShop account
  • A webhook URL from Zapier, Make, or another tool (we'll show you how to get one)
  • About 5 minutes

Step 1: Get Your Webhook URL

You need a URL that can "catch" the quote data when it's sent. The easiest way is to use Zapier or Make — both have free tiers and don't require any coding.

Option A: Zapier

  1. Go to zapier.com and sign in (or create a free account).
  2. Click Create Zap.
  3. For the trigger, search for Webhooks by Zapier and select Catch Hook.
  4. Copy the webhook URL Zapier gives you (it looks like https://hooks.zapier.com/hooks/catch/...).
  5. Keep this Zap open — you'll add what happens next (e.g., create a QuickBooks invoice) after we connect AirShop.

Option B: Make (formerly Integromat)

  1. Go to make.com and sign in (or create a free account).
  2. Create a new scenario.
  3. Add a Webhooks module → Custom webhook.
  4. Copy the webhook URL Make gives you.
  5. Keep this scenario open — you'll add the next step (e.g., create a QuickBooks invoice) after we connect AirShop.

New to automation?

Both Zapier and Make offer free tiers to get started. Sign up, create your webhook, and you can always add more steps later.

Step 2: Configure in AirShop

Log in to AirShop and go to Settings → Integrations → Outbound Webhooks. The page walks you through four steps:

Step 1 — Start your Zap or Make scenario

Paste your webhook URL into the Webhook URL field. This is the URL you copied from Zapier (Catch Hook) or Make (Custom webhook).

Step 2 — Enable and send a test

  1. Turn on Enable webhook.
  2. Click SEND TEST so Zapier or Make receives a sample payload. This lets you map fields in the next steps of your Zap or scenario.
  3. Finish building your Zap or Make scenario — add actions to create invoices, update spreadsheets, or whatever you need.

Step 3 — Name the button

The button on accepted quotes can show custom text. Enter a label that matches your integration (e.g. CREATE QUICKBOOKS INVOICE, CREATE XERO INVOICE, PUSH TO MAKE). Use the suggestions or type your own.

Step 4 — Choose when to send

  • Manual — You review the quote first, then click the button to send it to your integration.
  • Automatic — The webhook fires immediately when a customer accepts; no manual step needed.

Advanced options

Signing secret — Only needed if you build a custom endpoint that verifies request signatures. Zapier and Make don't use this; you can skip it. If you need it, expand Advanced options and use Generate or Copy.

Save

When you change any setting, Discard and Save buttons appear. Click Save to apply your changes.

Step 3: Use It

  • Manual mode: Open a quote that's marked as Won (Accepted), then click the button (e.g. CREATE QUICKBOOKS INVOICE) to send the event.
  • Auto mode: Nothing to do — when a quote is marked as Accepted, AirShop sends the data automatically.

Delivery Log

AirShop logs each delivery (success or failure) for debugging. If a send fails, check the webhook URL and that Zapier or Make is listening.

Troubleshooting

Nothing is showing up in Zapier/Make

  • Check that the webhook URL is correct and that you pasted the full URL (no spaces or missing characters).
  • In Zapier: Make sure you've triggered the Zap at least once (e.g., "Test trigger") so it's listening.
  • In Make: Make sure the scenario is turned on.

I want to verify that requests really come from AirShop

See the Technical section below for how to verify the signature.

Technical

This section is for developers or advanced users who need more control.

Overview

  • Per-organization — One webhook URL per organization.
  • Quote acceptance events — Fired when a quote is marked as accepted (Won).
  • Button label — Customizable text on the manual-send button (e.g. CREATE QUICKBOOKS INVOICE). Default: PUSH TO INTEGRATIONS.
  • Trigger modes — Manual: send only when you click the button. Auto: send automatically when a quote transitions to Accepted.
  • Secure — Requests are signed with HMAC-SHA256 in the X-Airshop-Signature header.

Signature Verification

Each request includes an X-Airshop-Signature header containing an HMAC-SHA256 signature of the raw request body, using your secret as the key. You can verify authenticity in Zapier/Make by adding a step that computes the expected signature and compares it to the header.

Custom Server

If you're not using Zapier or Make, expose a POST endpoint that accepts JSON. The request body will contain the quote acceptance payload. Use the X-Airshop-Signature header to verify the request before processing.

Delivery Log

All deliveries (success or failure) are logged for debugging.