Connect webhooks to Make

Use Make to add a row to Google Sheets when an enquiry is created in Arbour. The webhook supplies the enquiry ID; an API request fetches its details. Set up the Arbour side in Settings → Integrations.

Before you start

You need permission to Manage outbound webhooks and Manage API keys, a Make account, and a Google account that can edit your spreadsheet. Create an API key named for this scenario and save it securely.

Create a spreadsheet with these headings in row 1, in this order: Enquiry ID, Name, Stage, Event date, Created at. Use a separate test sheet and fictional enquiry details while building.

Connect Arbour

1. 01

   Create a Make scenario. Add Webhooks → Custom webhook, then add a webhook named Arbour enquiries. Leave API key authentication unset: Arbour cannot send Make's required x-make-apikey header. Save and copy the generated HTTPS URL.

2. 02

   In Arbour, press Add endpoint. Name it Make enquiries, paste the URL and subscribe only to pipeline_item.created. Press Create endpoint and save the signing secret separately from the API key.

3. 03

   Keep Make's default webhook acknowledgement. Do not add a response module that waits for the spreadsheet action: Arbour needs a 2xx within ten seconds.

Make's webhook module documentation covers the receiver settings. The default response acknowledges receipt before the later modules finish.

Test receipt

1. 01

   In Make, choose Run once. In Arbour, open the endpoint and press Send test ping. Check that Make receives it. A ping has empty data, contains no enquiry ID and creates no Arbour delivery-log entry.

2. 02

   Open the Make webhook settings and choose Detect new values. Create a new enquiry in Arbour using fictional details. Let Make detect that real event, then run the scenario once more with another test enquiry if needed to retain a run for mapping.

3. 03

   Inspect the webhook output. Confirm the outer type is pipeline_item.created, data.type is enquiry, and data.pipelineItemId is present. Do not map fields from the ping sample.

These fictional JSON examples show the two payloads. Their placeholder IDs cannot fetch a record.

Ping

{
  "version": 1,
  "type": "ping",
  "occurredAt": "2026-09-06T00:00:00.000Z",
  "organizationId": "org_example",
  "subject": null,
  "data": {}
}

New enquiry

{
  "version": 1,
  "type": "pipeline_item.created",
  "occurredAt": "2026-09-06T00:00:00.000Z",
  "organizationId": "org_example",
  "subject": { "type": "pipeline_item", "id": "pli_example" },
  "data": {
    "pipelineItemId": "pli_example",
    "type": "enquiry",
    "stageId": "stg_example",
    "formId": null,
    "formSubmissionId": null,
    "formSource": null
  }
}

Build the automation

The route is Custom webhook → HTTP request → Search Rows → Add a Row, with a filter before the HTTP request and another before adding a row.

Fetch the enquiry

1. 01

   Add HTTP → Make a request, using the current HTTP app with keychain credentials. Set a filter on the connection leading into it. Require both conditions with AND: webhook type equals pipeline_item.created, and webhook data.type equals enquiry. This stops pings and newly created bookings before the API request.

2. 02

   Set the method to GET. Enter https://api.usearbour.com/v1/pipeline-items/ in the URL and append the webhook's mapped data.pipelineItemId value. Keep the host fixed; do not map a URL from the incoming request.

3. 03

   Choose API key authentication and create a keychain. Give it a recognisable name, set its key to Bearer followed by your complete arb_... key, place it in the header and set the parameter name to Authorization. Do not add X-Arbour-Org: the API key already identifies your organisation. Leave the request body empty.

4. 04

   Enable Parse response and stop on failed HTTP requests. Disable redirects. Save the module, then replay your captured enquiry using the dropdown beside Run once. Inspect the parsed response so its fields become available to map.

See Make's HTTP module and API key keychain settings. The API returns the enquiry's current state, which may have changed since the event. Its response contains id, displayName, stage.name, startDate and createdAt.

Check for an existing row

1. 01

   Add Google Sheets → Search Rows and connect your Google account. Select the test spreadsheet and sheet, with row 1 as headings. Filter Enquiry ID using text equality against id from the HTTP response. Set the result limit to 1.

2. 02

   Add Google Sheets → Add a Row. On the connection before it, require the search module's Total number of bundles to equal 0, using numeric equality. An existing match stops here and leaves the sheet unchanged.

3. 03

   Select the same spreadsheet and sheet. Map the fields below from the HTTP response, not the search output. Use raw values for input so names are stored as text rather than interpreted as spreadsheet formulas.

Make documents Google Sheets connections and the search-count filter pattern. Test the empty-sheet case first: it must reach Add a Row with a search count of zero.

For Event date, use Make's ifempty function with the mapped startDate value first and "" second. Keep both date columns as ISO text for this recipe. See Make's mapping functions and spreadsheet date guidance if you want date arithmetic later.

Turn it on

1. 01

   Replay the captured enquiry and confirm one row appears. Replay it again after that run finishes. The existing Enquiry ID must stop the second row. Replay the ping too: it must stop before the HTTP request.

2. 02

   Save the scenario. Set its schedule to Immediately as data arrives and activate it. Keep the same webhook URL in Arbour; Make does not require a separate production URL.

3. 03

   Create a fresh test enquiry in Arbour. Check the Arbour delivery, the completed Make run and all five spreadsheet columns. Test one enquiry without an event date and confirm the cell stays blank. Create a test booking and confirm it is filtered out.

Make's schedule settings, scenario history and run replay explain where to inspect and replay runs. A replay uses the current scenario and reruns its actions, so retain the Enquiry ID check.

The check reduces duplicates from sequential retries. Concurrent runs can both find no row and add one. Make processes instant webhooks in parallel by default; Process data in order serialises this scenario, but other writers can still race. The sheet is not an exactly-once destination. See Make's webhook processing guidance and Arbour's delivery guidance.

Troubleshoot

Arbour delivery means Make accepted the request. It does not mean the API lookup or spreadsheet write succeeded. Arbour does not automatically retry a request Make has already acknowledged. Recover failed later steps in Make and check the sheet before replaying.

Advanced security

The webhook's advanced settings offer Get request headers and JSON pass-through. These expose headers and the original JSON text for a custom verifier. Changing to pass-through changes what later modules receive, so parsing and mapping must happen after verification. These options alone do not check a signature.

Use the Arbour signing reference: HMAC-SHA256 over the timestamp, a full stop and the exact raw body, using the complete whsec_... secret. Compare the v1=<hex> signature safely, check timestamp freshness and deduplicate delivery IDs durably. Confirm byte preservation with a known valid request; parsing and rebuilding JSON is not equivalent. Test altered bodies and stale timestamps too.

If unverified requests must be rejected before Make accepts them, place a verifying HTTPS receiver in front. It verifies and durably queues the event, acknowledges Arbour within ten seconds, then forwards accepted events to the private Make URL. A later Make filter cannot undo an acknowledgement. Building that receiver is separate from this visual guide.