Firebase Email to Webhook Integration

Why Connect Firebase to Inbound Email

Firebase stores structured data, but a surprising amount of business data still arrives via email — form submissions, order confirmations, sensor reports, and CSV attachments. JsonHook acts as the extraction layer, parsing incoming emails and pushing the relevant fields into Firebase as new rows or updated records without any manual intervention.

Connecting your inbound email to Firebase through JsonHook unlocks a range of high-value automation scenarios:

• Insert a new row for every inbound form-submission email
• Update existing records when a status-change email is received
• Store complete email metadata alongside extracted field values
• Aggregate daily report emails into a time-series table automatically
• Sync external order data from email confirmations into your database schema

Firebase supports Firebase Cloud Function (HTTP trigger), which makes it a natural target for JsonHook's outbound POST requests. Every email that hits your JsonHook address is parsed within milliseconds and delivered to Firebase as a clean JSON object — no polling, no manual export, no middleware server to maintain.

Setting Up Firebase with JsonHook

The following steps walk you through connecting JsonHook to Firebase. The entire setup typically takes under ten minutes.

1. Step 1: Create a Firebase Cloud Function with an HTTP trigger. The function accepts a POST request from JsonHook, validates an optional shared secret in the headers, and writes the parsed payload to Cloud Firestore.
2. Step 2: Deploy the function and copy its HTTPS endpoint URL from the Firebase console.
3. Step 3: In JsonHook, create an inbound address and set the Cloud Function URL as the destination. Optionally add a custom header (X-JsonHook-Secret: your-secret) for request validation.
4. Step 4: In Firestore, verify that new documents appear in the inbound_emails collection after sending a test email.

Once the connection is active, every email sent to your JsonHook address will be automatically parsed and forwarded to Firebase. You can test the integration by sending a plain-text email to your JsonHook address and verifying that the payload appears in Firebase within a few seconds.

JsonHook supports Firebase Cloud Function (HTTP trigger) on the Firebase side, so no additional configuration is needed in Firebase beyond the steps above. If Firebase requires header-based authentication for incoming webhooks, add the required headers in the JsonHook endpoint configuration under Advanced Settings.

Example Workflow: When a notification email arrives, write the parsed data to Firestore and trigger a Firebase Cloud Messaging push notification

This walkthrough demonstrates one concrete way to use JsonHook with Firebase. The scenario: When a notification email arrives, write the parsed data to Firestore and trigger a Firebase Cloud Messaging push notification.

When an email matching this scenario arrives, JsonHook parses the raw SMTP message and constructs the following JSON payload before POSTing it to your Firebase endpoint:

{
  "messageId": "",
  "from": {
    "name": "Jane Smith",
    "address": "[email protected]"
  },
  "to": [
    { "address": "[email protected]" }
  ],
  "subject": "When a notification email arrives, write the parsed data to Firestore and trigger a Firebase Cloud Messaging push notification",
  "text": "Hi, I need help with my account. Please contact me at your earliest convenience.",
  "html": "
Hi, I need help with my account...
",
  "date": "2026-03-15T10:32:00.000Z",
  "attachments": [],
  "headers": {
    "x-priority": "1"
  }
}

Firestore document fields: messageId → document ID (for deduplication), from.address → fromAddress, from.name → fromName, subject → subject, text → bodyText, html → bodyHtml, date → receivedAt (Firestore Timestamp), full payload → raw map field.

Once Firebase receives this payload, it can execute any downstream action — whether that is posting a notification, creating a record, updating a field, or triggering an entire multi-step workflow. The key advantage is that the data arrives as structured JSON, so Firebase never needs to parse raw email text or deal with MIME encoding.

Payload Mapping for Firebase

JsonHook delivers a consistent JSON schema for every parsed email. The table below shows which JsonHook fields map to the equivalent fields in Firebase. Use this as a reference when configuring your Firebase Firebase Cloud Function (HTTP trigger).

Not every field will be present in every email. Always check for null or missing values before mapping to required fields in Firebase. For text-only emails, html will be empty; for HTML-only emails, text may be empty or auto-generated from the HTML. The attachments array will be an empty array when no files are attached.

Best Practices for Firebase Email Integration

Following these best practices will make your Firebase email integration more reliable, easier to debug, and simpler to scale as your email volume grows.

• Use dedicated addresses per workflow. Create a separate JsonHook inbound address for each distinct Firebase workflow you want to trigger. This makes routing explicit and avoids a single endpoint becoming a bottleneck for all email types.
• Validate the payload before acting. In Firebase, add a conditional check at the start of your workflow to confirm that required fields like from.address and subject are present and non-empty before executing downstream actions.
• Test with real emails first. Use JsonHook's delivery log to inspect the raw JSON payload before wiring up Firebase. Confirm that all the fields you plan to map are actually populated by your email source.
• Handle errors gracefully. Configure Firebase to catch webhook delivery failures and send an alert. JsonHook will retry failed deliveries, but your Firebase endpoint should return a 2xx status promptly to acknowledge receipt.
• Keep secrets out of email content. Avoid routing emails that contain passwords, API keys, or PII through workflows unless you have appropriate data-handling controls configured in Firebase. Use JsonHook's HTTPS delivery to protect data in transit.