WordPress Email to Webhook Integration

Why Connect WordPress to Inbound Email

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

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

WordPress supports WordPress REST API or custom plugin endpoint, 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 WordPress as a clean JSON object — no polling, no manual export, no middleware server to maintain.

Setting Up WordPress with JsonHook

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

1. Step 1: Install a WordPress plugin that provides a webhook receiver endpoint, or create a custom REST API route in your theme's functions.php using register_rest_route().
2. Step 2: The endpoint should accept a POST request, verify an optional shared secret, parse the JSON body, and create a post or custom post type entry.
3. Step 3: In JsonHook, create an inbound address and set the WordPress endpoint URL as the destination. Add an X-Secret header matching your plugin configuration.
4. Step 4: Test by sending an email and confirming a new draft or published post appears in the WordPress admin.

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

JsonHook supports WordPress REST API or custom plugin endpoint on the WordPress side, so no additional configuration is needed in WordPress beyond the steps above. If WordPress requires header-based authentication for incoming webhooks, add the required headers in the JsonHook endpoint configuration under Advanced Settings.

Example Workflow: When a contributor submits an article pitch by email, create a draft WordPress post for editorial review

This walkthrough demonstrates one concrete way to use JsonHook with WordPress. The scenario: When a contributor submits an article pitch by email, create a draft WordPress post for editorial review.

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

{
  "messageId": "",
  "from": {
    "name": "Jane Smith",
    "address": "[email protected]"
  },
  "to": [
    { "address": "[email protected]" }
  ],
  "subject": "When a contributor submits an article pitch by email, create a draft WordPress post for editorial review",
  "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"
  }
}

WordPress REST API post creation: subject → title, text → content (or excerpt for a summary), from.address → meta.submitted_by (custom meta field), date → date, set status to draft for editorial review. Use the /wp-json/wp/v2/posts endpoint with Application Password authentication.

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

Payload Mapping for WordPress

JsonHook delivers a consistent JSON schema for every parsed email. The table below shows which JsonHook fields map to the equivalent fields in WordPress. Use this as a reference when configuring your WordPress WordPress REST API or custom plugin endpoint.

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

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