Mursa + Gmail
You receive 120 emails a day. Maybe 10 of them contain something you need to do. Finding those 10 means reading or scanning all 120. That is 28% of your workday spent on email, according to McKinsey research.
The action items in your email are not the emails themselves. They are buried inside the emails — a sentence in paragraph three that says 'can you send the report by Friday.' Email-to-task automation extracts the needle from the haystack.
How it works
Connect Gmail via OAuth
One-time setup in Mursa Settings. Standard Google OAuth flow. You grant read access to incoming emails.
Gmail push notification triggers processing
When a new email arrives, Gmail sends a push notification to Mursa via Google Pub/Sub. The email is processed immediately.
Pre-filter removes noise
Before AI processing, a filter checks against 30+ noreply patterns, 50+ automation domains, and 25+ subject line patterns. Over 80% of emails are filtered out as non-actionable.
AI extracts the action item
For emails that pass the filter, AI (Google Gemini) reads the content and extracts: task title, category (client reply, action required, review, follow-up, scheduling, payment), priority, and due date.
Task appears in your inbox
A new task appears in Mursa with the action item, priority, due date, and a direct link to the original email in Gmail.
What syncs
- Incoming email content (processed in real time, not stored)
- Extracted task title and description
- Category (client-reply, action-required, review-approval, follow-up, scheduling, payment, reply-needed)
- Auto-detected priority and due date
- Link to original email in Gmail
✕What does not sync
- Full email body (processed in real time, discarded after extraction)
- Email attachments
- Sent emails or drafts
- Contact lists or Gmail settings
- Calendar events (separate integration)
- Task completion back to email (no auto-reply)
Email content is processed in real time by AI and discarded immediately. Only the extracted task summary and a link to the original email are stored in your Mursa account. We never store the full email body, attachments, or any email metadata beyond what is needed for the task. All processing happens server-side with encrypted connections.
This feature is currently in testing while we go through Google's verification process. It works, but you may see a consent warning during setup until approval is complete.