AI email management

A workflow explanation by Jayson Bautista · Original robot guide: Dennice

1 / 24
Read the complete transcript
  1. The question: Let’s follow ai email management through the source diagram.
  2. The challenge: A diagram shows the connections, but not every configuration or runtime result.
  3. Our route: Therefore, we’ll trace the visible steps and finish with the evidence limits.
  4. Receive & classify: A Gmail Trigger feeds an AI Agent Classifier connected to Groq.
  5. Receive & classify: Parsed output reaches label lookup and label-existence checks.
  6. Receive & classify: The diagram includes creating a label and adding a label to a message.
  7. Route & draft: A sender lookup checks whether the sender is a VIP.
  8. Route & draft: VIP and high-priority branches contain AI draft generation.
  9. Route & draft: Draft details are logged in Google Sheets and notifications go to Telegram.
  10. Review & send: Telegram Callback Query starts a separate reply-review path.
  11. Review & send: The path retrieves draft details before the Gmail send-message node.
  12. Review & send: Status updates and a Telegram confirmation follow the send step.
  13. Follow up & report: A reminder branch reads unanswered emails and checks for overdue items.
  14. Follow up & report: Other branches show daily summaries, weekly reports and dashboard metrics.
  15. Follow up & report: A spam-checking branch and an unsubscribe-analysis branch are also visible.
  16. What is evidenced: The screenshots document node names, integrations and connections.
  17. What is evidenced: Prompts, credentials, exact routing rules and execution logs are not supplied.
  18. What is evidenced: Sending accuracy, response times and time savings have not been measured here.
  19. Recap: start: A Gmail Trigger feeds an AI Agent Classifier connected to Groq.
  20. Recap: process: A sender lookup checks whether the sender is a VIP.
  21. Recap: route: Telegram Callback Query starts a separate reply-review path.
  22. Recap: output: A reminder branch reads unanswered emails and checks for overdue items.
  23. Evidence boundary: The supplied screenshots show architecture. They do not verify production outcomes.
  24. Takeaway: Follow the connections, inspect the source, and validate configuration before operational use.

Source: local automation1 screenshots. This film explains visible node connections; prompts, credentials and execution results are not supplied. Robot and props are explanatory illustrations. Back to the case study.