Notifications

How channels work

Notification channels belong to an inbox, not to your account. Each project's inbox has its own set of channels, and you can toggle each one on or off per inbox. When a message arrives from any source (the form endpoint or the project email address), every enabled channel fires. There is no routing logic to configure: one inbox, its channels, a ping per message.

Discord

Discord notifications use a standard Discord webhook. Included on the free plan.

1. In your Discord server, open Server Settings → Integrations → Webhooks → New Webhook.
2. Pick the channel the pings should land in, then copy the webhook URL.
3. Paste the URL into the inbox's notification settings and enable the channel. New messages now post to that Discord channel.

Slack

Slack notifications use an incoming webhook URL. Slack is part of the Pro plan.

1. Create a Slack app at api.slack.com/apps. A bare app used only for the webhook is enough.
2. Enable Incoming Webhooks for the app and add a new webhook to the channel of your choice.
3. Copy the webhook URL and paste it into the inbox's notification settings.

Email

The simplest channel: mailcontact sends a notification email to your own address when a message arrives. Included on the free plan. Note the direction: your project's @mailcontact.app address is where messages come in; the email channel is how notifications go out to you.

Webhook

For your own automation, the webhook channel sends a JSON POST to a URL you control on every new message. The payload shape and delivery behavior are documented in Webhooks. Part of the Pro plan.

What's on which plan

• Free: Discord and email notifications, up to 2 projects.
• Pro (priced at launch): Slack, webhooks, and WhatsApp notifications, plus more projects and addresses.

Details on both plans are on the pricing page. mailcontact is in beta, so if a channel you need is missing, tell us.