Gmail Is Now Part of Your Jira CRM Workflow: Introducing Mria CRM: Gmail Connector
Customer relationships do not live in project boards. They live in conversations: emails, follow-ups, replies, threads that go back months. For years, Jira teams have had to accept that this part of the customer relationship would always exist somewhere else.
Mria CRM was built to change that. It is a native CRM for Jira, built on Forge and carrying the Runs on Atlassian badge, which means every line of code and every piece of data live exclusively within Atlassian infrastructure. No external hosting, no data leaving the ecosystem. The only CRM on the Atlassian Marketplace that can make that claim. But until today, one fundamental piece was missing: emails. Every conversation with a customer still happened in Gmail, outside the CRM, disconnected from the record.
That gap is now closed. Mria CRM: Gmail Connector is now available on the Atlassian Marketplace, and Gmail is now a native part of the CRM workflow in Jira.
Building a Real Jira CRM on Forge: What We Have Proven So Far
Mria CRM was built on a simple belief: the tools your team uses to close deals and manage customers should live in the same place as the tools they use to do their work. Not integrated with Jira. Not connected to Jira. Native to Jira, built on Forge, running inside the Atlassian ecosystem from day one.
There has been a long-standing assumption in the Atlassian ecosystem that a real CRM cannot be built inside Jira. That Forge is too limited. That the platform is not designed for it. That teams needing a CRM should look elsewhere. We have been proving that assumption wrong, one release at a time.
Today Mria CRM gives Jira teams a purpose-built CRM with contacts, leads, deals, custom pipelines, probability-weighted forecasting, reports, Kanban views, and deep integration with Jira, JSM, Confluence, and Rovo AI. Not a customized task list. Not a contact database bolted onto Jira issues. A real CRM, built to live where your team already works.
This is what we believe has been missing from the Atlassian stack. A CRM that belongs there the same way Jira belongs there, the same way JSM belongs there, the same way Confluence belongs there. Built on modern Atlassian infrastructure, respecting the platform's standards, and built to stay.
The Role of Gmail Integration in a Full Jira CRM Workflow
For a team using Mria CRM inside Jira, the customer workflow looks complete on paper. Contacts, leads, deals, pipelines, linked Jira issues, reports. Everything tracked, everything in one place. But there is one part of the customer relationship that has always lived outside this workflow: emails.
What the workflow looks like without Gmail integration
A lead comes in. It gets created in Mria CRM, assigned, tagged, and tracked through a pipeline. The contact record is there. The deal is there. The linked Jira board is there.
Then a customer sends an email. That email goes to Gmail. The reply comes back to Gmail. A follow-up gets sent from Gmail. Three weeks of back-and-forth, and none of it is in the CRM.
What that costs in practice
Someone new joins the deal and has no context. A support ticket comes in from the same company and the agent has no idea there was an active sales conversation happening. Teams log manually when they remember. They do not remember consistently. Everyone knows the CRM record is incomplete, and they work around it.
Why email cannot be optional in a CRM workflow
Email is not a secondary channel. For most customer-facing teams, it is the primary one. Every meaningful conversation, commitment, and decision runs through it. A CRM that does not capture that is not a complete system. It is a structured view of part of the picture.
This is the gap Gmail integration closes. So we built Mria CRM: Gmail Connector.
Introducing Mria CRM: Gmail Connector
Mria CRM: Gmail Connector is a dedicated extension for Mria CRM, available as a separate app on the Atlassian Marketplace. It brings Gmail directly into the Mria CRM workflow: connect your Gmail account once, and every email you send or receive automatically syncs to the matching Contact or Lead record in Mria CRM.
The full conversation history lives on the record. Next to the deal. Next to the linked Jira issues. Next to the activity log. In one place, visible to everyone who should see it, without anyone having to do anything manually. The CRM record finally tells the whole story.
How It Works
The connector syncs every 5 minutes in both directions. Incoming emails from Gmail are matched to CRM records by email address and appear on the corresponding Contact or Lead automatically. Outgoing emails composed inside Mria CRM are delivered through Gmail and logged to the record instantly.
Matching works across records: if an email address appears on multiple contacts or leads, the email shows up on all of them. Emails sent from Mria CRM show a Pending status until the next sync cycle confirms delivery, which in practice takes up to 5 minutes.
Admins have full visibility into which Gmail accounts are connected across the site. Users can only manage accounts they personally own. The connector is CASA-certified and uses standard Google OAuth. Access can be revoked from Google Account settings at any time independently of Mria CRM.
Key Features
- Bidirectional sync every 5 minutes. Incoming and outgoing emails link to matching Contact and Lead records automatically, without any manual action.
- Compose and send from Mria CRM. Write and send emails directly from a Contact or Lead record. The email is delivered through Gmail and logged to the record instantly.
- Multiple Gmail accounts supported. Connect as many Gmail accounts as you need: personal, corporate, or shared inboxes. No limitations.
- Visibility controls. Choose who in Mria CRM can see your synced emails: Private (only you), Shared (specific teammates you select), or Public (your entire Mria CRM site). Private is the default.
- Incoming email filters. Control which emails from Gmail get synced into Mria CRM. Sync everything, exclude specific senders, or allowlist only the addresses that matter. Filters apply to future emails only and never remove messages already synced.
- Non-destructive pause and disconnect. Stop syncing at any time without losing emails already in Mria CRM. Disconnecting an account keeps all previously synced emails on their records.
Getting Started with Mria CRM: Gmail Connector
Mria CRM: Gmail Connector installs as a separate app alongside Mria CRM. Setup requires one admin step and takes a few minutes.
If you are already using Mria CRM, go straight to the Atlassian Marketplace and install Mria CRM: Gmail Connector. If you are new to Mria CRM, start by installing Mria CRM first, then follow the instructions below.
Installation
- Install Mria CRM: Gmail Connector from the Atlassian Marketplace
- As a site admin, go to Atlassian Administration, open Site settings, select Connected apps, choose Mria CRM, and enable App REST APIs. This is required for the connector to read and write CRM records during sync. Without it, the OAuth connection will succeed but no emails will sync
- Open Mria CRM: Gmail Connector from the Atlassian app switcher, go to the Accounts page, and click Connect Mria CRM. Complete the Atlassian OAuth consent
- Click Add Gmail Account, sign in with Google, and approve the requested Gmail scopes
Configuration
Once your Gmail account is added, click Edit next to it to configure two settings:
Visibility controls who in Mria CRM can see your synced emails. Private keeps them visible only to you. Shared lets you select specific teammates. Public makes them visible to everyone on your Mria CRM site. Private is the default and the safe starting point.
Incoming email filters control which emails get synced from Gmail into Mria CRM. No restrictions syncs everything. Excluded addresses lets you blocklist specific senders. Allowed addresses syncs only emails from addresses you specify. Changes apply to future emails only.
Using Gmail Integration in Mria CRM
Once connected, open any Contact or Lead record in Mria CRM and switch to the Emails tab. Every email exchanged with that contact appears there automatically, matched by email address. Incoming emails show a green arrow, outgoing a blue one. The full conversation history is paginated and always up to date within a 5-minute sync window.
To send an email, use the composer at the top of the Emails tab. Choose which connected Gmail account to send from, write your message, and hit Send. The email goes out through Gmail and is logged to the record instantly.
If the same email address appears on multiple records, the email shows up on all of them. Emails sent from Mria CRM show a Pending status until the next sync cycle confirms delivery.
For a full setup guide with screenshots, see the Mria CRM: Gmail Connector documentation.
Our Goal: CRM That Belongs in the Atlassian Stack by Default
Gmail integration is not the finish line. It is the piece that makes the CRM workflow complete enough to be taken seriously.
We are building a CRM that belongs in the Atlassian stack the same way Jira, JSM, and Confluence belong there. Not as a plugin. Not as a workaround. As a real, complete system for managing customer relationships, built on Forge, built for the ecosystem, built to stay. The kind of product that teams should not have to leave Atlassian to find.
Every release we ship closes another gap. Contacts, leads, deals, pipelines, reports, Jira integration, JSM integration, Confluence integration, Rovo AI, and now Gmail. Each one moves Mria CRM closer to what a CRM in the Atlassian stack should have been from the beginning.
Outlook integration is next on our roadmap. More is coming.
If you are using Mria CRM or evaluating it for your Jira team, we would love to hear from you in the comments. What does your current customer workflow in Jira look like? What is still missing? What would make it complete?
Try Mria CRM: Gmail Connector free on the Atlassian Marketplace
Was this helpful?
Thanks!
Anton Storozhuk _Mria Labs_
1 comment