Retool Email to Webhook Integration

Why Connect Retool to Inbound Email

Retool 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 Retool can read, display, and act upon.

Connecting your inbound email to Retool 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 Retool
• 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

Retool supports Retool Workflows HTTP trigger or direct database resource insert, 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 Retool as a clean JSON object — no polling, no manual export, no middleware server to maintain.

Setting Up Retool with JsonHook

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

1. Step 1: In Retool Workflows, create a new workflow and add an HTTP webhook trigger as the starting block. Copy the generated webhook URL.
2. Step 2: In JsonHook, create an inbound email address and set the Retool Workflows webhook URL as the destination.
3. Step 3: In the Retool workflow, add a Query block connected to your database resource. Write an INSERT query that maps JsonHook fields to the appropriate columns.
4. Step 4: Add optional downstream blocks — send a Slack notification, update a Retool app state, or call an external API — to complete the automation.

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

JsonHook supports Retool Workflows HTTP trigger or direct database resource insert on the Retool side, so no additional configuration is needed in Retool beyond the steps above. If Retool requires header-based authentication for incoming webhooks, add the required headers in the JsonHook endpoint configuration under Advanced Settings.

Example Workflow: When a support email arrives, insert the parsed data into an internal Postgres database and refresh the support dashboard

This walkthrough demonstrates one concrete way to use JsonHook with Retool. The scenario: When a support email arrives, insert the parsed data into an internal Postgres database and refresh the support dashboard.

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

{
  "messageId": "",
  "from": {
    "name": "Jane Smith",
    "address": "[email protected]"
  },
  "to": [
    { "address": "[email protected]" }
  ],
  "subject": "When a support email arrives, insert the parsed data into an internal Postgres database and refresh the support dashboard",
  "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"
  }
}

Retool exposes the HTTP trigger payload as {{ trigger.data }} in query blocks. Map trigger.data.from.address to the sender column, trigger.data.subject to the subject column, and trigger.data.text to the body column in your SQL INSERT statement.

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

Payload Mapping for Retool

JsonHook delivers a consistent JSON schema for every parsed email. The table below shows which JsonHook fields map to the equivalent fields in Retool. Use this as a reference when configuring your Retool Retool Workflows HTTP trigger or direct database resource insert.

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

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