Trello Email to Webhook Integration

Why Connect Trello to Inbound Email

Project work is often coordinated across email and tools like Trello. Client feedback, bug reports, and approval requests arrive by email, but your team tracks work in Trello. JsonHook bridges this gap by converting inbound emails into structured data that Trello can use to create tasks, update records, and notify team members automatically.

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

• Convert client feedback emails into actionable tasks automatically
• Create bug reports in your backlog from automated error-notification emails
• Assign tasks to team members based on the recipient or subject of an email
• Update task status when an approval email is received from a stakeholder
• Attach incoming email content to the relevant project record for full context

Trello supports Trello REST API (Cards 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 Trello as a clean JSON object — no polling, no manual export, no middleware server to maintain.

Setting Up Trello with JsonHook

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

1. Step 1: Generate a Trello API Key at trello.com/app-key and generate a token with write access to your boards.
2. Step 2: In Zapier or Make, create a workflow triggered by the JsonHook webhook URL. Add a Trello action to create a card in the specified list.
3. Step 3: In JsonHook, create an inbound address and set the automation webhook URL as the destination.
4. Step 4: Map subject to the Trello card name, text to the card description, and set the idList to the target Trello list ID.

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

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

Example Workflow: When a client emails a feature request, create a Trello card in the Backlog list

This walkthrough demonstrates one concrete way to use JsonHook with Trello. The scenario: When a client emails a feature request, create a Trello card in the Backlog list.

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

{
  "messageId": "",
  "from": {
    "name": "Jane Smith",
    "address": "[email protected]"
  },
  "to": [
    { "address": "[email protected]" }
  ],
  "subject": "When a client emails a feature request, create a Trello card in the Backlog list",
  "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"
  }
}

Trello Card creation: subject → name, text → desc, from.address → add as a comment (via POST /1/cards/{id}/actions/comments) for context. Set due if the email contains a date reference. Use idLabels to color-code by category.

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

Payload Mapping for Trello

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

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

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