One-time code verification across every channel

The scenario accepts requests from any channel, sends a one-time code by email via ruSender, verifies it and links all of a person's channels into a single profile in Microsoft SQL.

  • One profile per person instead of a list per channel
  • Codes stored and checked in Microsoft SQL, with expiry
  • Resend the code if the email didn't arrive
  • Already-verified channels skip straight through
Webhook
Set it upScriptera

How it works

To connect Microsoft SQL and ruSender, you don't need a developer: a ready-made scenario links them in minutes.

  1. Starts when: Webhook
  2. Then: Universal normalization
  3. Then: Check if the channel already exists
  4. Check: If
  5. If yes: Execute a SQL query3
  6. Then: Channel already verified
  7. If no: Execute a SQL query
  8. Then: Search onboarding_session
  9. Check: If1
  10. If yes: Extract email
  11. Check: If4
  12. If yes: If2- extracted_email
  13. If yes: Execute a SQL query5
  14. Then: Generate OTP
  15. Then: Save OTP
  16. Then: Send email
  17. Then: waiting_for_otp
  18. Check: If2
  19. If no: response_message1 - verification code sent
  20. If no: Greeting 1 - send your email
  21. If no: IF_step- waiting_otp
  22. If yes: IF_resend_otp
  23. If no: Execute a SQL query1
  24. Check: IF_code_exists?
  25. If yes: valid OTP
  26. Then: Execute a SQL query2
  27. Then: Get verified session email
  28. Check: If email en session
  29. If yes: Upsert user by email
  30. Then: Upsert user_channel
  31. Then: Verification completed response
  32. If no: Missing email response
  33. If no: code does not exist

You can launch this Microsoft SQL + ruSender integration in Scriptera: describe the task in plain words — the scenario is built, launched and monitored for you.

Similar scenarios