A channel, not a mailbox
Contact messages land in #support or #leads instead of someone's personal inbox. Anyone in the channel can pick one up, and the project inbox keeps the full history.
notifications
Get your website's messages in Slack.
Point a plain HTML form at your mailcontact endpoint, paste a Slack incoming-webhook URL, and every submission pings your channel. No backend, no automation platform in the middle, no email-parsing hack.
It's not just forms. Every project also gets a real inbound email address (yourproject@mailcontact.app), and messages sent there fire the same Slack notification. One inbox per project, one channel that always knows.
how it works
From submit to Slack ping in three steps.
01
Create an inbox
One inbox per project. Name it and you immediately get a form endpoint and a project email address. No DNS, no mail server.
02
Add a form or email source
Paste the HTML form on your site, or share yourproject@mailcontact.app. Both sources feed the same project inbox.
03
Add a Slack channel
Create an incoming webhook on api.slack.com, paste the webhook URL into your channel settings in mailcontact, and every new message pings the channel.
the form
A contact form that pings Slack, in one paste.
Point any HTML form at your project's endpoint. It accepts posts from any origin, so it works on static sites, site builders, and frameworks alike. Prefer to keep visitors on the page? Submit the same fields with fetch; a configurable redirect for native posts is coming with the launch.
your-site/contact.html
<form action="https://mailcontact.app/api/forms/your-form-id" method="POST">
<input type="text" name="name" placeholder="Your name" />
<input type="email" name="email" placeholder="you@email.com" required />
<textarea name="message" placeholder="How can we help?" required></textarea>
<button type="submit">Send</button>
</form>why slack
Triage where the team already is.
No forwarding, no CC chains
Stop forwarding "did you see this?" emails around. Everyone in the channel sees new messages the moment they arrive, with zero routing rules to maintain.
Forms and inbound email, same ping
Whether a visitor used your contact form or emailed yourproject@mailcontact.app, the same Slack channel fires. One setup covers both sources.
faq
Slack + mailcontact, answered
How do I create a Slack incoming webhook?
On api.slack.com, create a Slack app (or use the Incoming Webhooks integration), enable Incoming Webhooks, and add one to the channel you want to notify. Copy the webhook URL Slack gives you and paste it into your project's channel settings in mailcontact. That's the whole setup.
Can I notify more than one channel?
Yes. A project can have several notification channels, so you can ping Slack and keep an email notification as a backup. Slack, webhooks, and WhatsApp channels are part of the Pro plan (priced at launch); Discord and email notifications are on the free plan.
Does the Slack notification include the full message?
Slack is the ping; the inbox is the record. The notification tells the channel a new message arrived, and the full message (sender, subject, body) lives in your project inbox alongside everything else the project has received.
Do messages sent to my project's email address ping Slack too?
Yes. Form submissions and emails to yourproject@mailcontact.app land in the same inbox, and every new message triggers your notification channels, Slack included. One setup covers both sources.
related
Keep exploring
Every message from your site, pinged to Slack.
Forms and a real email address, one inbox per project, notifications where your team lives. Launching soon. Be the first to know.