Bubble Email to Webhook Integration

Why Connect Bubble to Inbound Email

Bubble empowers builders to create applications without writing code. Email is a natural input channel for many no-code apps — contact forms, appointment requests, and customer feedback all arrive via email. JsonHook makes it trivial to receive those emails as structured JSON data that Bubble can read, display, and act upon.

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

• Populate a data table with records parsed from incoming emails
• Trigger page logic or workflows when a specific email address receives a message
• Display inbound email data in a custom dashboard built on Bubble
• Connect contact form submissions delivered by email to your app's user table
• Build an email-driven approval flow without writing a single line of code

Bubble supports Bubble API Workflow (Backend workflow with webhook 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 Bubble as a clean JSON object — no polling, no manual export, no middleware server to maintain.

Setting Up Bubble with JsonHook

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

1. Step 1: In your Bubble app, go to Settings → API and enable the Bubble API. Create a new API Workflow under the Backend Workflows section, choose POST as the method, and note the generated endpoint URL.
2. Step 2: Define the parameters your workflow will accept: from_address (text), subject (text), body (text), received_at (date).
3. Step 3: In JsonHook, configure the inbound address and paste the Bubble API Workflow URL as the destination. Use JsonHook's field mapping to POST the correct parameter names.
4. Step 4: In the Bubble workflow, add an action to create a new Thing (database record) using the incoming parameter values.

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

JsonHook supports Bubble API Workflow (Backend workflow with webhook trigger) on the Bubble side, so no additional configuration is needed in Bubble beyond the steps above. If Bubble requires header-based authentication for incoming webhooks, add the required headers in the JsonHook endpoint configuration under Advanced Settings.

Example Workflow: When a user submits an email form, create a new Bubble database record and trigger an in-app notification

This walkthrough demonstrates one concrete way to use JsonHook with Bubble. The scenario: When a user submits an email form, create a new Bubble database record and trigger an in-app 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 Bubble endpoint:

{
  "messageId": "",
  "from": {
    "name": "Jane Smith",
    "address": "[email protected]"
  },
  "to": [
    { "address": "[email protected]" }
  ],
  "subject": "When a user submits an email form, create a new Bubble database record and trigger an in-app 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"
  }
}

Bubble API Workflow parameters: from.address → from_address parameter, subject → subject parameter, text → body parameter, date → received_at parameter. In the workflow, map each parameter to the corresponding field of your Bubble data type.

Once Bubble 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 Bubble never needs to parse raw email text or deal with MIME encoding.

Payload Mapping for Bubble

JsonHook delivers a consistent JSON schema for every parsed email. The table below shows which JsonHook fields map to the equivalent fields in Bubble. Use this as a reference when configuring your Bubble Bubble API Workflow (Backend workflow with webhook trigger).

Not every field will be present in every email. Always check for null or missing values before mapping to required fields in Bubble. 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 Bubble Email Integration

Following these best practices will make your Bubble 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 Bubble 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 Bubble, 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 Bubble. Confirm that all the fields you plan to map are actually populated by your email source.
• Handle errors gracefully. Configure Bubble to catch webhook delivery failures and send an alert. JsonHook will retry failed deliveries, but your Bubble 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 Bubble. Use JsonHook's HTTPS delivery to protect data in transit.