Plunk logo
Plunk

Emails in,
actions out.

Receive at your own domain, save the sender as a contact, and trigger a workflow from the reply.

Start for freeInbound docs
inboundyourdomain.comMX ok
  • Ana Ruizsupport@c_8f21Can you resend my invoice?now
  • Tom Bakkerbilling@c_7d04Updated our VAT number14m
  • Priya Nairhello@c_6b93Loved the changelog1h
POST /hooks/plunk3 delivered

What arrives, and what happens next

Receiving is the easy half. What Plunk does with the message afterwards is the point.

  • Every address, one MX record

    Point your domain at Plunk once and every address on it starts receiving. You do not create mailboxes one at a time.

    support@, billing@, hello@

  • Senders become contacts

    Anyone who writes in is created as a contact if they do not already exist, so a reply is the start of a record rather than a dead end in someone inbox.

  • Parsed onto your webhook

    Headers, body, and attachments arrive as JSON on your endpoint, in real time, ready to route into a help desk or a CRM.

    POST /hooks/plunk

  • Filtered before it reaches you

    Spam, virus, SPF, DKIM and DMARC checks run on every message first.

  • Triggers workflows

    An inbound message is an event like any other, so it can start a sequence, tag a contact, or send an auto-reply.

Setting it up

  1. Step 01

    Verify your domain

    Add your domain in Plunk and configure the DKIM and SPF records in your DNS settings.

  2. Step 02

    Add one MX record

    Copy the MX record from your dashboard into your DNS. That routes incoming mail to Plunk.

  3. Step 03

    Start receiving

    Mail to any address at your domain now arrives, saves the sender, and can trigger workflows or webhooks.

What teams use it for

  • Support inbox

    Mail to support@ creates a ticket in your help desk over a webhook and sends an acknowledgement back automatically, so nothing sits unanswered.

    Instant acknowledgement, automatic ticket, nothing missed

  • Lead capture

    Mail to info@ or sales@ adds the sender to your contacts and starts a nurture sequence timed from when they actually reached out.

    Zero-friction capture, auto-segmentation, instant follow-up

  • Two-way campaigns

    Let people reply to your campaigns. The reply lands on the same contact record and can tag them as engaged.

    Conversation history, engagement tracking

Frequently asked questions

Do I have to create each address I want to receive on?

No. One MX record covers the whole domain, so support@, billing@ and anything else all start working at once. You route them however you like on your own side.

What does Plunk send to my webhook?

A JSON payload with the sender, the recipient address, the subject, the parsed body and any attachments, plus the contact record the sender was matched to or created as.

Is inbound mail filtered for spam?

Yes. Spam, virus, SPF, DKIM and DMARC checks run on every message before it reaches your webhook.

Can a reply trigger an automation?

Yes. An inbound message is an event like any other, so it can start a workflow, tag the contact, or fire an auto-reply.

Start receiving at your domain.

Free plan: 1,000 emails a month. Paid: $0.001 an email.

Start for freeView pricing