Stripe Email to Webhook Integration

Why Connect Stripe to Inbound Email

E-commerce operations generate a constant stream of email notifications — orders, refunds, supplier messages, and customer inquiries. Stripe needs to respond to these events quickly. JsonHook captures those emails the moment they arrive, parses them into clean JSON, and forwards them to Stripe so your fulfillment and support workflows can fire automatically.

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

• Automatically fulfill orders when supplier confirmation emails arrive
• Trigger refund workflows when a customer sends a cancellation email
• Update inventory records when stock notification emails are received
• Notify your warehouse team the moment a rush order email arrives
• Log all customer support emails as tickets linked to their order history

Stripe supports Stripe API (Customers, Payment Links, Invoices endpoints), 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 Stripe as a clean JSON object — no polling, no manual export, no middleware server to maintain.

Setting Up Stripe with JsonHook

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

1. Step 1: Generate a Stripe secret API key from the Stripe Dashboard under Developers → API keys.
2. Step 2: In Make or n8n, create a workflow triggered by the JsonHook webhook URL. Add an HTTP Request action to call the relevant Stripe API endpoint.
3. Step 3: In JsonHook, create an inbound address (e.g., [email protected]) and set the automation webhook URL as the destination.
4. Step 4: Map from.address to the Stripe Customer email for lookup, and parse payment amounts or invoice references from the text field to populate the API call body.

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

JsonHook supports Stripe API (Customers, Payment Links, Invoices endpoints) on the Stripe side, so no additional configuration is needed in Stripe beyond the steps above. If Stripe requires header-based authentication for incoming webhooks, add the required headers in the JsonHook endpoint configuration under Advanced Settings.

Example Workflow: When a payment request email is received, look up the Stripe customer and send them a Payment Link

This walkthrough demonstrates one concrete way to use JsonHook with Stripe. The scenario: When a payment request email is received, look up the Stripe customer and send them a Payment Link.

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

{
  "messageId": "",
  "from": {
    "name": "Jane Smith",
    "address": "[email protected]"
  },
  "to": [
    { "address": "[email protected]" }
  ],
  "subject": "When a payment request email is received, look up the Stripe customer and send them a Payment Link",
  "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"
  }
}

Stripe Customer lookup: from.address → query /v1/customers?email=. Payment Link creation: extract amount from parsed text → unit_amount. Invoice: subject → description, date → due_date. Use structured email templates from your team so the parser can reliably extract numeric values.

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

Payload Mapping for Stripe

JsonHook delivers a consistent JSON schema for every parsed email. The table below shows which JsonHook fields map to the equivalent fields in Stripe. Use this as a reference when configuring your Stripe Stripe API (Customers, Payment Links, Invoices endpoints).

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

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