Make Email to Webhook Integration

Why Connect Make to Inbound Email

Automation platforms like Make are designed to connect apps and trigger actions automatically. Email remains one of the most universal communication channels, yet most automation tools have no built-in way to receive email as a trigger. JsonHook solves this by turning any inbound email into a structured JSON event that Make can act on immediately.

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

• Trigger a multi-step automation every time a support email arrives
• Route emails from different senders to different automation branches
• Parse order confirmation emails and sync data to a spreadsheet automatically
• Send a follow-up SMS or email whenever a specific keyword appears in the subject line
• Create calendar events from email-based meeting requests without any manual input

Make supports Custom Webhook module, 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 Make as a clean JSON object — no polling, no manual export, no middleware server to maintain.

Setting Up Make with JsonHook

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

1. Step 1: Open Make and create a new Scenario. Add a "Webhooks" module as the first step and select "Custom webhook". Give it a name and click "Save" to generate the webhook URL.
2. Step 2: Copy the Make webhook URL. In JsonHook, create or edit an inbound address and paste this URL as the target endpoint. Enable the connection.
3. Step 3: Send a test email to your JsonHook address. In Make, click "Run once" and then "OK" to capture the incoming request. Make will display the full JSON payload for field mapping.
4. Step 4: Add downstream modules to your Scenario — for example, a Google Sheets module to append a row or an HTTP module to call another API. Map the JsonHook fields (subject, from.address, text) to the appropriate inputs.

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

JsonHook supports Custom Webhook module on the Make side, so no additional configuration is needed in Make beyond the steps above. If Make requires header-based authentication for incoming webhooks, add the required headers in the JsonHook endpoint configuration under Advanced Settings.

Example Workflow: When an order confirmation email arrives, append a row to a Google Sheet and send a Slack summary

This walkthrough demonstrates one concrete way to use JsonHook with Make. The scenario: When an order confirmation email arrives, append a row to a Google Sheet and send a Slack summary.

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

{
  "messageId": "",
  "from": {
    "name": "Jane Smith",
    "address": "[email protected]"
  },
  "to": [
    { "address": "[email protected]" }
  ],
  "subject": "When an order confirmation email arrives, append a row to a Google Sheet and send a Slack summary",
  "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"
  }
}

Make automatically parses the incoming JSON and presents each field as a pickable variable. Nested objects like from appear as from.address and from.name in the field selector. Arrays like attachments can be iterated using Make's Array Iterator module.

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

Payload Mapping for Make

JsonHook delivers a consistent JSON schema for every parsed email. The table below shows which JsonHook fields map to the equivalent fields in Make. Use this as a reference when configuring your Make Custom Webhook module.

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

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