> ## Documentation Index > Fetch the complete documentation index at: https://docs.getcore.me/llms.txt > Use this file to discover all available pages before exploring further. # Email > Email your Meta Agent for asynchronous assistance ## Overview Send emails to **[brain@getcore.me](mailto:brain@getcore.me)** and get intelligent responses from CORE's Agent. Perfect for longer requests, asynchronous workflows, or when you're already in your email client. ## Getting Started Simply email **[brain@getcore.me](mailto:brain@getcore.me)** from your registered email address. Your agent will: 1. Process your request 2. Search your memory if needed 3. Take actions across your connected apps 4. Reply with results and context ## How It Works 1. **Compose or forward** an email to [brain@getcore.me](mailto:brain@getcore.me) from your registered account 2. **Add your instructions** in the email body (or just forward with a quick note) 3. **Include context** by forwarding email threads, attaching files, or referencing past conversations 4. **Get intelligent replies** with drafted responses, action confirmations, or requested information **Email Forwarding Workflow:** When you forward an email to [brain@getcore.me](mailto:brain@getcore.me), CORE preserves the entire thread context, making it perfect for: * Setting reminders to follow up * Extracting action items and creating tasks * Getting summaries of long threads * Drafting context-aware responses * Saving important discussions to memory ## Use Cases **Scenario**: Never forget to follow up on important emails ``` To: brain@getcore.me Subject: Fwd: Q1 Budget Approval [Forward the email thread] Remind me to follow up on this if I don't hear back by Friday. ``` CORE saves the email context to memory and will remind you at the right time, with full context of the original thread. **Scenario**: Write emails that need information from other tools ``` To: brain@getcore.me Subject: Draft response to client I need to respond to Sarah's email about the API migration timeline. Please draft a response that includes: - Current status from Linear project "API Migration" - Completed PRs from GitHub in the last week - Any blockers mentioned in #engineering Slack channel ``` CORE gathers information from your connected apps and drafts a complete, context-aware email response. **Scenario**: Turn email discussions into trackable tasks ``` To: brain@getcore.me Subject: Fwd: Meeting notes - Product roadmap [Forward the email with meeting notes] Extract all action items from this email and: - Create Linear issues for each task - Assign them to the people mentioned - Add them to the "Q1 Roadmap" project - Reply with a summary of created tasks ``` CORE processes the email, creates tasks across your tools, and confirms what was done. **Scenario**: Catch up on lengthy discussions quickly ``` To: brain@getcore.me Subject: Fwd: Re: Re: Re: Design system discussion (24 messages) [Forward the long email thread] Summarize this thread for me: - What's the current decision? - Who's responsible for what? - What are the next steps? ``` Perfect for when you're cc'd on a long thread and need the TL;DR without reading 50+ messages. **Scenario**: Pull context from past conversations to answer emails ``` To: brain@getcore.me Subject: Need context on authentication work John is asking about the authentication system we built last quarter. Find all the details: - Original design decisions from Slack/memory - Related GitHub PRs - Documentation in Notion Then draft a reply explaining the current architecture and why we chose it. ``` CORE searches your memory and connected tools, then drafts an informed response. **Scenario**: Get help organizing your inbox ``` To: brain@getcore.me Subject: Triage my action items [Forward 5-10 emails that need responses] Which of these emails need urgent attention and why? For each: - Priority level - Why it matters - Suggested response or action ``` CORE analyzes each email with context from your memory and suggests how to prioritize. **Scenario**: Convert emails into delegated work without leaving your inbox ``` To: brain@getcore.me Subject: Fwd: Bug report from customer [Forward customer email about bug] Create a high-priority Linear bug issue with: - Title: "Customer report: [extract from email]" - Description: [full customer report] - Assign to: engineering on-call - Send a Slack message to #bugs channel - Draft a reply to customer saying we're investigating ``` CORE handles the entire workflow and gives you a draft customer response to review. **Scenario**: Get detailed reports for email responses ``` To: brain@getcore.me Subject: Weekly update for investors Create a weekly update email covering: - What shipped (GitHub releases + Linear completed issues) - Team velocity (last 3 sprints from Linear) - Customer feedback highlights (from support emails) - Next week's priorities (from Linear current sprint) Make it investor-friendly and concise. ``` CORE compiles data from multiple sources and drafts a polished update email. ## Example Emails **Forward to Set Reminder:** ``` To: brain@getcore.me Subject: Fwd: Partnership proposal from Acme Corp [Forwarded email thread] Set a reminder to follow up on this next Tuesday if they haven't responded. Also save this to memory under "partnership opportunities." ``` **Draft Response with Context:** ``` To: brain@getcore.me Subject: Help draft reply to CEO The CEO just asked about our API rate limiting strategy. Draft a response that includes: - Current limits and why we chose them - Any recent discussions about changing them (check Slack #engineering) - Related GitHub issues or PRs ``` **Extract Action Items from Thread:** ``` To: brain@getcore.me Subject: Fwd: Kickoff meeting notes [Forwarded meeting notes email] Extract all action items, create Linear issues for each, and send a summary to #project-alpha Slack channel. ``` **Get Context for Email Reply:** ``` To: brain@getcore.me Subject: Need pricing discussion context Michael is asking about enterprise pricing. Find our previous discussions about pricing tiers and draft a response explaining our current structure. ``` ## Response Time * **Simple queries**: Usually within 1-2 minutes * **Complex requests**: May take 5-10 minutes for thorough analysis * **Batch operations**: Depends on number of actions (you'll get progress updates) ## Tips for Email Workflows * **Forward liberally**: Forward any email thread to CORE for context, reminders, or drafting replies * **Use subject lines**: Put key instructions in the subject for quick processing * **Set follow-up reminders**: Never forget to circle back - just forward and ask for a reminder * **Draft before sending**: Ask CORE to draft responses that need context from other tools * **Batch forward**: Send multiple emails at once and ask for prioritization or summaries * **Include deadlines**: "Remind me Friday" or "Follow up in 3 days" works naturally * **Reference people naturally**: Use @mentions or names, CORE will map them to your contacts ## Need Help? Join our [Discord community](https://discord.gg/dVTC3BmgEq) for support in **#core-support**