How to Build an 'Instant Inquiry Notification' System Using SES and Webhooks
Introduction
'I'm always late to notice website inquiries...'
'I get the emails, but I want to be notified immediately on Slack or LINE.'
'I want to set up a system that allows for real-time responses.'
For companies and developers facing these challenges, we recommend an 'instant notification' inquiry system using Amazon SES × Webhook.
In this article, we will explain the construction steps and best practices for linking email-based inquiries to Slack or other systems in real-time.
Why is the combination of 'Email' + 'Webhook' so powerful?
Most inquiry forms are completed via 'email sending'.
By using SES, you can also use receiving as a trigger
With Webhook integration, you can notify your preferred tools instantly
📬 Moving from 'just receiving' emails to 'notification + action'.
This will significantly change the speed and quality of your operations.
Common challenges and solutions
5 Steps to Building an 'Instant Notification' System
✅ 1. Configure custom domain reception in SES
Register your domain in SES and configure DNS records (TXT, MX).
Create a 'Receipt Rule Set'.
Select 'Lambda' or 'SNS (→Webhook)' as the reception trigger.
🔐 Reception configuration requires 'Verify domain' and 'MX record' registration.
✅ 2. Write the email parsing → Webhook sending process in Lambda
Example: Lambda (Node.js) to notify Slack of inquiry emails
jsCopy and edit
🧩 This can also be applied to LINE, Teams, Notion, etc., in addition to Slack.
✅ 3. Link Lambda to SES Receipt Rules
Specify Lambda in the SES 'Receipt Rule Set' screen
A configuration that relays via an SNS topic for Webhook notification is also possible
⚠️ For the first time, don't forget to set the 'SES Receipt Permission (Policy)' for Lambda.
✅ 4. Structure and Notify Inquiry Email Content
Use one of the following to parse the email body:
Parse mail.content within Lambda (Base64 to string conversion)
Processing is easier if you use plain text instead of HTML email
If the body is in JSON format, parsing, converting to an object, and formatting is smooth
📄 By automatically extracting and notifying form input values from emails, you get content notifications that allow for immediate response.
✅ 5. Combine with DB storage or CRM integration as needed
Save inquiry content to RDS / DynamoDB
Integrate with CRMs like Salesforce or HubSpot
Integration with Google Sheets or Notion via Zapier or IFTTT is also possible
🔁 It can be used not just for 'notifying and finishing', but also for centralized management of inquiry information.
Commonly used Tips
✅ SNS → Lambda → Webhook configuration increases versatility
✅ Enable confirmation of notification processing success/failure in CloudWatch Logs
✅ Optimize format for each notification destination (Markdown for Slack)
✅ Automated immediate response emails after form submission can also be handled by SES
Conclusion
AWS SES × Webhook integration is a mechanism that changes inquiry handling from 'passive' to 'active'. By notifying Slack or LINE immediately, it can also contribute to
improving lead acquisition rates and customer satisfaction.
It is a small mechanism, but it should become a major weapon for your team and business. Please consider implementing it!
Notice
At ZENSHIN, we provide development support for business automation, internal notification systems, and inquiry management using AWS.
If you have needs such as 'I want to introduce a Slack notification mechanism' or 'I want to streamline inquiry responses,' please feel free to contact us.
👉 If you are interested,
you can contact us via https://www.zenshin-inc.co.jp/#contact!
Company Overview
Trade Name: ZENSHIN Inc.
Address: 1-11-4 Jinnan, Shibuya-ku, Tokyo 150-0041
Representative: Motoki Hanzawa, Representative Director
Main Business:
Contract Development of Casual Games
Software / System Contract Development
Generative AI Contract Development
Quality Assurance Testing
SES / Staffing and Recruitment Services