Webhook Events to Airtable Database for Healthcare & Allied Health

# Webhook Events to Airtable Database - Healthcare & Allied Health

## Purpose
Set up as a central event log when you need to track and analyse data from applications that support webhook notifications.

## When to Use
Capture incoming webhook events from any application into an Airtable database for logging, analysis, and triggering downstream automations.

## Instructions
1. Review the template below and familiarise yourself with the structure
2. Replace all [bracketed placeholders] with your healthcare & allied health business details
3. Customise the tone and formatting to match your brand
4. Save in your preferred tool (Airtable or Zapier)

---

## Webhook Events to Airtable Database

### Overview
Capture incoming webhook payloads from any application into a structured Airtable database, creating a central event log that you can filter, analyse, and use to trigger downstream automations.

### Prerequisites
- Airtable account (Free plan works, Pro recommended for higher record limits)
- Zapier account (Professional plan for Webhooks by Zapier)
- The source application must support outgoing webhooks or webhook notifications
- Basic understanding of JSON data structure

### Setup Steps

**Step 1: Create your Airtable base**
Create a new Airtable base called "Event Log" with the following table structure:

**Table: "Events"**

| Field Name | Field Type | Notes |
|-----------|-----------|-------|
| Event ID | Auto-number | Unique identifier |
| Timestamp | Date/Time | When the event was received |
| Source App | Single Select | e.g., Stripe, Shopify, Custom App |
| Event Type | Single Line Text | e.g., "payment.completed", "order.created" |
| Status | Single Select | New, Processing, Completed, Error |
| Payload Summary | Long Text | Human-readable summary |
| Raw Payload | Long Text | Full JSON payload for debugging |
| Related Record ID | Single Line Text | ID from the source system |
| Processed | Checkbox | Whether downstream actions ran |
| Notes | Long Text | Manual notes or error messages |

**Step 2: Create a Zapier webhook endpoint**
Log in to Zapier and click "Create Zap". Name it "Webhook to Airtable Event Log".

**Step 3: Configure the Webhooks by Zapier trigger**
- App: Webhooks by Zapier
- Trigger event: "Catch Hook"
- Zapier will generate a unique webhook URL (e.g., https://hooks.zapier.com/hooks/catch/xxxxx/)
- Copy this URL - you will need it in Step 5

**Step 4: Test the webhook**
Before connecting your source application, test with a sample payload:
- Use a tool like Postman, curl, or your browser
- Send a POST request to the Zapier webhook URL with a test JSON body:

```
curl -X POST https://hooks.zapier.com/hooks/catch/xxxxx/ \
  -H "Content-Type: application/json" \
  -d '{"event": "test.event", "data": {"id": "123", "name": "Test"}}'
```

- Verify Zapier receives and parses the payload correctly

**Step 5: Configure your source application**
In the application sending webhooks:
- Navigate to Settings > Webhooks (or API > Webhooks)
- Add a new webhook endpoint
- URL: Paste the Zapier webhook URL from Step 3
- Events: Select which events to send (start with a small set and expand)
- Secret/Signing key: Note this if provided (for payload verification)

Common source configurations:
- **Stripe:** Dashboard > Developers > Webhooks > Add endpoint
- **Shopify:** Settings > Notifications > Webhooks > Create webhook
- **GitHub:** Repository > Settings > Webhooks > Add webhook

**Step 6: Add a Formatter step for the payload**
- App: Formatter by Zapier
- Action: "Utilities - Line Itemizer" or "Text - Concatenate"
- Create a human-readable summary from key payload fields
- Example: "[Event Type] for [Customer Name] - Amount: $[Amount]"

**Step 7: Configure the Airtable action**
- App: Airtable
- Action event: "Create Record"
- Base: "Event Log"
- Table: "Events"

**Step 8: Map fields**

| Webhook Data | Airtable Field | Notes |
|-------------|---------------|-------|
| (current timestamp) | Timestamp | Use Zapier's built-in timestamp |
| (static value) | Source App | Set based on which webhook this Zap handles |
| event / type field | Event Type | The event name from the payload |
| "New" | Status | Default for all incoming events |
| Formatted summary | Payload Summary | Human-readable version |
| Full JSON body | Raw Payload | Complete payload for reference |
| id / reference field | Related Record ID | The record ID from the source system |
| false | Processed | Unchecked until downstream actions complete |

**Step 9: Add downstream actions (optional)**
Based on the event type, trigger additional actions:
- Payment received: Update your CRM deal status
- Order created: Notify your fulfilment team via Slack
- Error event: Page your on-call team via PagerDuty or SMS

**Step 10: Test the full flow**
1. Trigger a real event in your source application (e.g., create a test order)
2. Wait 1-2 minutes for the webhook to fire and Zapier to process it
3. Open Airtable and verify the new record appears with correct data
4. Check the Payload Summary is readable and the Raw Payload is complete
5. If downstream actions are configured, verify they triggered correctly

### Error Handling
- **Malformed payloads:** If the webhook sends data Zapier cannot parse, the Zap will error. Use Zapier's "Catch Raw Hook" variant if you need to handle non-JSON payloads.
- **Duplicate events:** Some applications send the same event multiple times. Use the Related Record ID to check for duplicates before creating a new Airtable record.
- **Webhook verification:** If your source app uses HMAC signing for webhook verification, note that Zapier does not verify signatures. For production security, consider using a middleware service.
- **Rate limits:** Airtable's free plan allows 5 API calls per second. For high-volume webhooks, use Zapier's built-in throttling or upgrade your Airtable plan.

### Maintenance
- Review the Event Log weekly for any "Error" status records
- Archive processed records monthly to keep the Airtable base performant (move to an "Archive" table)
- Rotate or update the webhook URL if you suspect it has been compromised
- Update field mappings when the source application changes its webhook payload structure
- Monitor Airtable record count against your plan limits

---

**Complexity:** advanced | **Setup time:** 25 minutes | **Tools:** Airtable, Zapier

Note: This template has been tailored for healthcare & allied health businesses in Australia. Adjust terminology and compliance references to match your specific context.