Multi-Factor Authentication via Voice and Email
On form submission, it calls the user with a spoken code via ClickSend, then emails a second code via SMTP for two-step verification.
developers and engineersops and IT teams
What it does
Get verified instantly when you submit a form by receiving a spoken code on your phone followed immediately by a second code in your email. This two-step process ensures your account stays secure while letting you complete your submission quickly.
Step by step
- Configure the HTTP request node to POST to the ClickSend voice endpoint with the recipient number and generated code.
- Set up the SMTP connection details including host, port, username, and password for the email service provider.
- Define the form trigger schema to capture the user's phone number and initial submission timestamp.
Where the LLM does the work
- Generate secure, random alphanumeric verification codes that meet specific length and complexity requirements.
- Draft clear, concise voice script text for the ClickSend API call to ensure natural speech synthesis.
- Compose a professional email template that includes instructions and the unique verification code.
Watch out for
ClickSend calls may fail if the phone number format is invalid so always validate E.164 formatting before sending.
SMTP servers often block automated emails from unknown IPs so configure SPF and DKIM records to improve deliverability.
Voice recognition errors can cause verification failures so implement a retry mechanism with a limited number of attempts.
Code expiration times must be strictly enforced in the validation logic so users cannot reuse old codes after the window closes.
Tools that fit
SMTP Service Sending email verification codes
Code LLM Formatting verification code for voice clarity
The agent brief
Everything your agent needs, including the gotchas. Copy it and go.
You are helping me build the following AI agent workflow. ## Goal Multi-Factor Authentication via Voice and Email: On form submission, it calls the user with a spoken code via ClickSend, then emails a second code via SMTP for two-step verification. ## Specification - What it does: Get verified instantly when you submit a form by receiving a spoken code on your phone followed immediately by a second code in your email. This two-step process ensures your account stays secure while letting you complete your submission quickly. - Trigger: Triggered by an event (Event · on form submission) - Autonomy: Fully hands-off - Expected setup effort: about an afternoon - Tools/services involved: - ClickSend API: Sending voice calls with verification codes - SMTP: Sending email verification codes - Code: Formatting verification code for voice clarity ## Known pitfalls, handle each one explicitly in your implementation 1. ClickSend calls may fail if the phone number format is invalid so always validate E.164 formatting before sending. 2. SMTP servers often block automated emails from unknown IPs so configure SPF and DKIM records to improve deliverability. 3. Voice recognition errors can cause verification failures so implement a retry mechanism with a limited number of attempts. 4. Code expiration times must be strictly enforced in the validation logic so users cannot reuse old codes after the window closes. ## Reference implementation https://n8n.io/workflows/3142 (workflow template) Fetch and inspect this before building. If it matches my stack, adapt it; if not, rebuild the pattern with my tools. ## Process requirements 1. Before building: ask me which of the listed tools I actually use and what my platform is (n8n / Make / code / other). Do not assume. 2. Adapt the pattern to my answers; do not force the reference stack. 3. Address every pitfall above; tell me how you handled each. 4. Provide a test plan I can run before letting this touch real data. 5. Ask before any step that sends messages, modifies data, or spends money. Source: https://usecasesforagents.com/use-case/multi-factor-authentication-via-voice-and-email/ via usecasesforagents.com
Frequently asked questions
Can I use a different Messaging than ClickSend API?
Yes. ClickSend API is only the example messaging in this recipe. The same flow works with Discord, Google Chat, LINE Messaging API and Matrix. Swap the messaging connection and keep the rest of the setup as written.
Want this running in your business?
This is what I do. I design and build AI agents like this one, and keep them running. If you want it set up for your team instead of doing it yourself, get in touch.
Who it's for
Built for developers who want the busywork around code automated, not the code itself.
Ops-IT teams triaging their own internal requests get the same pattern, different queue.