Titan Email to Webhook

Why Route Titan Email Emails to a Webhook?

Titan Email is a professional email service bundled with many domain registrar and web hosting packages, targeting small businesses and entrepreneurs with custom-domain email. While Titan Email is a capable email platform, its native tooling for programmatic automation was not built for developers who need structured, reliable data delivery to backend systems.

The native approach — Titan Email IMAP access — introduces significant operational overhead. You need to manage credentials, poll or maintain persistent connections, and write custom parsing logic for every message field you care about. When your team is moving fast, that friction adds up to hours of maintenance per integration.

JsonHook eliminates that overhead by accepting inbound mail on your behalf and immediately firing a structured JSON payload to any HTTPS endpoint you specify. The email is parsed, attachments are base64-encoded, and headers are normalised — so your webhook handler can focus entirely on business logic rather than MIME parsing.

Below are the core benefits of routing your Titan Email messages through JsonHook instead of relying on the native alternative:

• Limitation avoided: Titan Email does not expose a public API for inbound email processing — there is no webhook, push notification, or programmatic event mechanism beyond IMAP.
• Limitation avoided: Titan's IMAP server is shared infrastructure that may apply rate limits on high-frequency polling, making it unreliable for real-time automation.
• Limitation avoided: Titan's forwarding configuration is only available at the account level — there is no per-address filter-based forwarding on the basic tiers.
• Zero-polling architecture: JsonHook pushes to your endpoint the moment mail arrives — no long-running background jobs needed.
• Automatic attachment handling: PDFs, images, and other file types are extracted, base64-encoded, and included in the JSON payload with their original MIME type.
• Retry with exponential back-off: If your endpoint is temporarily unavailable, JsonHook retries automatically — something the Titan Email IMAP access does not do natively.
• Webhook signatures for security: Every delivery includes an HMAC-SHA256 signature header so you can verify the payload originated from JsonHook.

Whether you are building a support-ticket ingestion pipeline, a lead-capture workflow, or an automated document processor, JsonHook gives you a consistent, typed interface to Titan Email messages without the fragility of raw SMTP or polling-based API integrations.

How to Forward Titan Email to JsonHook

Getting Titan Email emails delivered to your webhook takes about five minutes. The process has two parts: creating a JsonHook address via the API, and configuring Titan Email to forward a copy of each incoming message to that address.

1. Log in to your Titan Email admin panel (accessible from your hosting provider's control panel) or directly at cp.titan.email.
2. Navigate to Email Forwarding under your account or domain settings.
3. Click Add Forward, enter the source address (e.g. [email protected]), and set the destination to your JsonHook inbound address.
4. Save the rule. Titan activates forwarding immediately without a verification step.

Once forwarding is active, every email that arrives in your Titan Email inbox (or matches your filter) will be relayed to your JsonHook address, parsed, and delivered to your endpoint as a JSON payload within seconds.

You can create your JsonHook inbound address with a single curl command. Replace YOUR_API_KEY with the key from your dashboard and set webhookUrl to your endpoint:

curl -X POST https://jsonhook.com/api/addresses \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "label": "Titan Email inbound",
    "webhookUrl": "https://your-app.example.com/webhooks/email",
    "secret": "a-random-signing-secret"
  }'

The response includes your unique @in.jsonhook.com address. Copy that address and paste it into the forwarding field in your Titan Email settings. That is all the infrastructure you need to stand up.

Titan Email vs Titan Email IMAP access

When developers first explore email-to-webhook automation they typically discover Titan Email IMAP access — the official programmatic route provided by Titan. The table below shows how it compares to using JsonHook as an intermediary.

The native approach through Titan Email IMAP access requires you to set up OAuth credentials or API keys, maintain a long-running listener or polling job, write your own MIME parser, and implement your own retry queue. Any one of those steps can become a reliability bottleneck in production.

JsonHook handles all of that infrastructure on your behalf. You get a single HTTPS webhook call with a predictable JSON schema every time a Titan Email email arrives — no polling, no credential rotation, no MIME parsing, and no bespoke retry code to maintain.

JSON Payload Example

When a Titan Email email is forwarded to your JsonHook address and delivered to your endpoint, the request body looks like the following. All fields are consistently present; optional fields such as htmlBody and attachments are included when the source message contains them.

{
  "id": "msg_01j8xkr4p2vn3q7w",
  "receivedAt": "2026-03-15T14:32:07.412Z",
  "from": {
    "name": "Alice Smith",
    "address": "[email protected]"
  },
  "to": [
    {
      "name": "",
      "address": "[email protected]"
    }
  ],
  "subject": "Your Titan Email message subject here",
  "textBody": "Plain-text content of the email body.",
  "htmlBody": "<div>HTML version of the email body.</div>",
  "headers": {
    "message-id": "<[email protected]>",
    "x-mailer": "Titan",
    "mime-version": "1.0"
  },
  "attachments": [
    {
      "filename": "document.pdf",
      "contentType": "application/pdf",
      "size": 84234,
      "content": "JVBERi0xLjQK..."
    }
  ],
  "spf": "pass",
  "dkim": "pass"
}

The id field is a unique, stable identifier you can use for idempotent processing. The spf and dkim fields reflect the authentication results JsonHook observed when receiving the message, which you can use to enforce additional trust policies in your handler.

Attachment content is standard base64. Decode it with a single call in any language — Buffer.from(att.content, 'base64') in Node.js, base64.b64decode(att.content) in Python, and so on.

Node.js handler for Titan Email messages forwarded through JsonHook:

import express from 'express';
import crypto from 'crypto';

const app = express();
app.use(express.json());

app.post('/webhooks/titan', (req, res) => {
  const sig = req.headers['x-jsonhook-signature'] as string;
  const raw = JSON.stringify(req.body);
  const hash = crypto
    .createHmac('sha256', process.env.JSONHOOK_SECRET!)
    .update(raw).digest('hex');
  if (hash !== sig) return res.status(401).send('Bad signature');

  const email = req.body;
  // Small business lead routing
  if (email.subject?.toLowerCase().includes('inquiry')) {
    // notify owner via SMS or push notification
    console.log(`New inquiry from ${email.from.address}: ${email.subject}`);
  }
  res.sendStatus(200);
});

app.listen(3000);

Common Titan Email to Webhook Use Cases

Titan Email is the default email product bundled with many web hosting and domain registrar platforms, particularly in emerging markets. It provides a professional email address tied to a custom domain at low cost, making it common among small businesses and solo entrepreneurs who need automation without complex infrastructure.

• Small business inquiry capture: Businesses using Titan for their contact@ or hello@ inbox can forward every inquiry to a webhook that creates a lead in their CRM and sends an auto-acknowledgement — without hiring an IT team to set it up.
• Domain-registered business automation: Entrepreneurs who registered a domain with a hosting provider and received Titan Mail as part of the package can immediately add webhook automation to their email workflow without switching providers.
• Order confirmation relay: Small shops that manage orders manually via email can forward order confirmation messages to a webhook that updates a Google Sheet, Airtable base, or Notion database in real time.
• Support queue for solo operators: Solopreneurs using Titan Mail for customer support can route all inbound messages to a webhook that categorises by urgency and sends a push notification to their phone for high-priority inquiries.