Job Application Email Sender
Send a job post screenshot to Telegram and get a personalized email draft cached for review before sending with your resume attached.
freelancers and consultantsdevelopers and engineers
What it does
Send a job post screenshot to Telegram to instantly receive a personalized email draft tailored to the role and ready to send with your resume attached after you review it.
Step by step
- Configure Telegram Bot API credentials and set up a webhook or long-polling listener for incoming messages.
- Initialize Redis connection with a specific key pattern like 'draft:{user_id}' to store generated email drafts temporarily.
- Set up Gmail OAuth2 service account or user credentials to enable programmatic sending of emails with attachments.
- Implement Google Drive API integration to locate and download the resume file based on a predefined file ID or search query.
Where the LLM does the work
- Analyze the text extracted from the job post screenshot to identify key skills, role title, and company culture cues.
- Generate a personalized email draft that aligns the user's resume experience with the specific requirements found in the job description.
- Refine the tone of the generated email to ensure it sounds professional yet enthusiastic without sounding generic or robotic.
Watch out for
OCR accuracy on screenshots can be poor so add a step to validate extracted text quality before sending it to the LLM for analysis.
Resume files may exceed Gmail's 25MB limit so check file size early and compress or warn the user if the attachment is too large.
Tools that fit
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 Job Application Email Sender: Send a job post screenshot to Telegram and get a personalized email draft cached for review before sending with your resume attached. ## Specification - What it does: Send a job post screenshot to Telegram to instantly receive a personalized email draft tailored to the role and ready to send with your resume attached after you review it. - Trigger: Triggered by an event (Manual · on new job post screenshot) - Autonomy: You stay in control - Expected setup effort: a few focused days - Tools/services involved: - Telegram: User input and interaction interface - OpenAI: Analyzing job posts and drafting emails - Gmail: Sending personalized application emails with attachments - Google Drive: Storing and retrieving resume files - Redis: Caching AI-generated email drafts for user confirmation ## Known pitfalls, handle each one explicitly in your implementation 1. OCR accuracy on screenshots can be poor so add a step to validate extracted text quality before sending it to the LLM for analysis. 2. Resume files may exceed Gmail's 25MB limit so check file size early and compress or warn the user if the attachment is too large. ## Reference implementation https://n8n.io/workflows/13077 (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/automated-job-application-email-sender/ via usecasesforagents.com
Frequently asked questions
Can I use a different Messaging than Telegram?
Yes. Telegram is only the example messaging in this recipe. The same flow works with ClickSend API, Discord, Google Chat and LINE Messaging API. 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 freelancers and consultants juggling this across every client, not just one.
Developers can adapt this to their own repo or ticket queue with the same trigger and tools.