Imagine your team releases a feature in Jira that 20 potential customers have been waiting for. How many of those people will actually hear from Sales?
Or consider the Leads that haven't been contacted in weeks, the Deals approaching their closing dates, and the customer requests that need input from several departments. How much time does your team spend finding this information, updating records, and coordinating the next steps?
Most of these processes follow predictable rules. Yet someone still has to initiate them, move information between tools, and make sure nothing is forgotten.
Jira Automation already handles much of this work for development, project management, and service management. And when your CRM lives directly in Jira, the same automation engine can manage customer-related processes.
Mria CRM now works directly with Jira Automation, allowing teams to create, find, and update CRM records, link them to Jira work items, and automate customer-related processes using the familiar Jira Automation builder.
This opens up possibilities that go well beyond automatically changing a Deal stage.
Let's explore how Jira-native CRM automation can eliminate repetitive work, keep customer information up to date, and coordinate processes across Sales, Support, Product, and Engineering.
Why CRM Automation Works Differently When Your CRM Lives in Jira
Jira Automation already provides a powerful set of capabilities: event-based triggers, scheduled processes, incoming webhooks, conditions, branching, smart values, and actions.
The challenge with CRM automation is usually connecting those capabilities to customer information.
A traditional Jira CRM integration requires two systems to exchange data. Teams need to map records, manage authentication, handle synchronization, and maintain the integration as their workflows evolve.
Even after connecting the systems, they still need to establish relationships between customer records and the work associated with them.
A Jira-native CRM simplifies this architecture.
Mria CRM is a CRM for Jira built on Atlassian Forge. It provides dedicated records for Leads, Contacts, Companies, Deals, Products, and customer activities directly within the Atlassian environment.
These records can be linked to Jira work items, while native Jira custom fields expose relevant CRM information to JQL, filters, dashboards, and automation conditions.
For example, Jira can identify work items associated with Deals in Negotiation, find work linked to a specific Company, or filter delivery tasks by the closing dates of related Deals.
Now Jira Automation can also act on those CRM records.
Mria CRM introduces nine dedicated actions:
- Create Lead, Create Contact, and Create Deal to add CRM records automatically.
- Find Record and Search Records to retrieve individual records or lists that match specific conditions.
- Update Lead and Update Deal to change statuses, assignees, tags, and other supported properties.
- Link Item to connect CRM records with Jira work items, Confluence pages, boards, and other resources.
- Add Note to record information directly in the relevant CRM record.
These actions work alongside existing Jira Automation capabilities.
Mria CRM actions are available directly in the Jira Automation builder
A scheduled flow can search for inactive Leads, process every matching record, update its tags, and send a follow-up reminder. Or a Jira event can identify linked CRM records, evaluate their properties, and automatically create work for another team.
For these supported operations, there's no need to build a separate automation engine or maintain a custom integration between Jira and Mria CRM.
The same business logic applies whether someone changes a CRM record manually or through automation. Updates are recorded in the CRM timeline, permissions and validation rules are respected, and relevant notifications and pipeline calculations are updated.
Customer management can become part of the same automated workflows that already coordinate work across Jira.
Practical CRM Automation Use Cases in Jira
With Mria CRM actions now available directly in Jira Automation, the possibilities extend well beyond sales pipeline updates.
You can automate everyday CRM operations that don't involve Jira work items at all, as well as more complex processes connecting customer relationships with product development, service management, and project delivery.
The following six use cases demonstrate how Mria CRM and Jira Automation can work together to reduce manual tasks and coordinate customer-related processes.
1. Automatically Capture Leads from External Sources Directly in Jira
Let's start with a familiar problem.
A company receives new inquiries through website forms, demo requests, webinar registrations, and landing pages.
Each submission contains valuable information, but someone needs to transfer it into the CRM, check whether the person already exists, assign the Lead, and preserve the context of their request.
Jira Automation can handle that process automatically.
Example: A prospect submits a demo request.
The flow begins with an Incoming webhook that receives the form submission.
From there, Jira Automation:
- Searches Mria CRM for an existing Lead using the submitted email address.
- Creates a new Lead if no matching record exists, including the person's name, company, source, and tags.
- Adds the original request as a note to the CRM record.
- If the Lead already exists, records the new inquiry against the existing Lead.
- Optionally assigns the Lead and creates a Jira follow-up work item according to predefined rules.
Automation flow:
Form submission → Incoming webhook → Find Lead → Create Lead or add note → Assign and follow up
Lead Capture: Automatically create Leads in Jira and prevent duplicates
Consider someone who registers for a webinar in March, asks about pricing in April, and requests a demo in May.
Instead of creating three separate Leads, the automation can preserve those interactions under one record.
Sales receives the history of the prospect's interest without manually collecting information from different sources.
The same approach works with any form or application capable of sending the required HTTP request.
Since Jira Automation supports incoming webhooks and Mria CRM provides the necessary actions, you don't need an additional automation platform just to move submissions into your CRM. The sending application only needs a secure way to submit the data.
We've published a complete example of automatic Lead capture from website forms, including the webhook configuration, duplicate-checking logic, and CRM actions.
2. Automatically Identify Neglected Leads and Overdue Deals in Jira
Creating CRM records is only part of maintaining useful customer information.
Over time, Leads remain untouched, Deals accumulate outdated closing dates, and opportunities that need attention become difficult to distinguish from those progressing normally.
Someone eventually has to review the database, identify neglected records, and ask their owners for updates.
It's repetitive work that can be automated.
Example: A weekly CRM health check.
Every Monday morning, Jira Automation runs a scheduled flow that searches Mria CRM.
The first rule identifies Leads that:
- Are still in New status.
- Haven't been updated for more than 30 days.
For each matching Lead, the automation adds a Needs review tag and can create a follow-up task in Jira, assign it to the responsible sales representative, and link it to the Lead in Mria CRM.
A second rule finds open Deals with approaching or overdue closing dates.
It then sends the team a digest through email or Slack, including Deal names, amounts, closing dates, and links to the corresponding CRM records.
Automation flow:
Weekly schedule → Search CRM records → Check conditions → Update matching records → Send digest
CRM Clean-up: Identify neglected Leads and create follow-up tasks.
These workflows can become more sophisticated.
For example, Leads that remain untouched beyond a defined period can be flagged for reassignment. Deals approaching their closing dates can generate follow-up work items for their owners. Opportunities that have been overdue for a long time can be collected for a pipeline review.
You can also configure rules that automatically close Deals meeting specific conditions, although commercial decisions should generally include appropriate safeguards.
The important part is that CRM maintenance no longer depends entirely on someone remembering to review the database.
With Search Records and Jira's Advanced branching, one automation can process multiple CRM records, updating each according to its own conditions.
Because these flows use a Scheduled trigger, they don't need a Jira work item or a person to start them.
We've documented several examples in Scheduled Clean-up and Digests.
3. Turn Jira Product Releases into Automated Sales Follow-ups
This is one of my favorite examples because it connects product development directly to customer relationships.
Imagine a SaaS company where several potential customers have requested a particular feature.
Some are waiting for it before making a purchasing decision. Others previously decided the product wasn't suitable because that functionality was missing.
Sales records their interest in Mria CRM and links the relevant Leads to the feature request in Jira.
A few months later, the development team releases the feature.
Without automation, the development team needs to inform Sales about the release, and each sales representative has to check whether any of their Leads were waiting for the feature and arrange follow-ups.
With Jira Automation, the release itself can initiate that process.
Example: A requested feature becomes available.
When the Jira work item transitions to Released, the automation:
- Finds the Leads linked to that feature.
- Processes the matching records using Advanced branching.
- Adds a Feature available tag to each Lead.
- Records the release information in their CRM history.
- Creates Jira follow-up work items for their owners, including links to the Lead and released feature.
Automation flow:
Feature released → Find interested Leads → Update CRM records → Create Sales follow-ups
Jira Product Releases: Turn Jira releases into automated Sales follow-ups.
Imagine that 20 prospects were waiting for this functionality.
One Jira event can prepare 20 follow-up actions, each connected to the relevant customer record.
Sales can then reach out with a specific reason to restart the conversation.
Nobody needs to search old meeting notes, manually review lost opportunities, or maintain a separate spreadsheet of customers interested in future functionality.
This workflow combines existing Jira Automation capabilities with Mria CRM's native links, record search, branching, and update actions.
It also demonstrates an important advantage of having CRM and product development in the same environment.
Customer interest can be connected directly to the product backlog, and product releases can automatically generate relevant sales activity.
4. Automate Sales-to-Engineering Handoffs in Jira
In B2B software, consulting, and service companies, sales frequently depends on technical work.
A potential customer requests a custom integration. Sales needs to qualify the opportunity, but Engineering must first assess feasibility and estimate the effort.
This often creates a sequence of manual tasks.
Someone creates the Deal, prepares a technical request, copies customer requirements into Jira, assigns the work, and follows up with Engineering.
Jira Automation can coordinate much of this process.
Example: A new integration request needs technical assessment.
Suppose a prospect submits a structured request through Jira Service Management.
The automation can:
- Identify the requester and search for their Contact and Company in Mria CRM.
- Create missing customer records when appropriate.
- Check whether an open Deal already exists for the request.
- Create a new Deal in the relevant sales pipeline if needed, linking it to the appropriate Contact and Company.
- Create a technical assessment work item for Engineering.
- Link the work item to the Deal and assign it to the appropriate team.
- Notify the responsible sales representative.
Automation flow:
Customer request → Find customer records → Check opportunity → Create Deal if needed → Create technical assessment → Link and notify
The technical assessment arrives in Engineering's Jira backlog with the relevant request and customer context already connected.
Sales can follow its progress through the Jira work item linked to the Deal.
The process can continue when Engineering finishes the assessment.
Another Jira Automation flow can record the outcome in the Deal's timeline and notify its owner that the opportunity is ready for the next commercial step.
This creates a repeatable handoff between Sales and Engineering without requiring someone to coordinate each action manually.
It can be particularly useful for teams selling implementation projects, consulting services, custom development, or solutions that require technical validation before a proposal.
5. Use CRM Data to Automate Customer Escalations in Jira Service Management
For companies using Jira Service Management or Customer Service Management, customer information becomes especially valuable when it can influence how service requests are handled.
Support teams already use Jira Automation to manage SLAs, priorities, assignments, and escalations.
With Mria CRM, those rules can also consider the commercial context of a customer.
This makes Jira Service Management CRM integration useful for more than displaying customer details in a service request.
Mria CRM exposes linked CRM records through native Jira custom fields, whose properties can be queried using JQL.
For example, this condition identifies Jira work associated with Deals in Negotiation:
"Mria CRM Deals.Stage" = "Negotiation"
You can combine CRM conditions with ordinary Jira properties, including priority, status, and due dates.
This allows automation to consider both the operational urgency of an issue and its customer context.
Example: A critical customer issue threatens an active opportunity.
Imagine a customer whose support request has breached an SLA threshold.
At the same time, the customer has an active Deal in Negotiation, and the issue could affect the purchasing decision.
Without automation, the service team may continue working on the technical problem while the account manager remains unaware of the commercial risk.
Automation can:
- Trigger when the JSM request breaches a configured SLA threshold.
- Check whether the request is linked to a relevant CRM Deal.
- Evaluate the Deal's stage and other available CRM information.
- Create or update an escalation work item and notify the responsible team.
- Notify the Deal owner about the incident.
- Add the escalation details to the CRM record.
Automation flow:
SLA breached → Check CRM context → Evaluate conditions → Escalate → Notify Deal owner → Record incident
Support continues working in Jira Service Management, while Sales receives the information needed to manage the customer relationship.
The CRM maintains a history of the incident without requiring someone to copy it manually.
The same approach can support other processes.
For example, Jira Automation can:
- Raise the priority of work associated with Deals approaching their closing dates.
- Notify account managers when important customer work becomes blocked.
- Flag unresolved delivery tasks associated with late-stage opportunities.
- Route customer requests based on available CRM information.
These workflows demonstrate how customer data can influence operational decisions directly within Jira.
For teams looking to improve their Jira Service Management CRM integration, the key advantage is that automation can use customer and Deal information already linked to the service request, without requiring agents to open another system.
6. Automate Customer Project Onboarding in Jira
For consulting companies, software vendors, and implementation teams, moving from an approved commercial engagement to delivery involves considerable preparation.
Someone needs to create the project structure, prepare onboarding tasks, assign responsibilities, connect documentation, and make sure Engineering has the necessary customer information.
Many of these steps are nearly identical for every new customer.
That makes project onboarding another good candidate for automation.
Example: A new customer project receives approval.
Suppose the commercial approval process is tracked in Jira.
When the corresponding approval work item transitions to Approved, Jira Automation can:
- Find the Mria CRM Deal linked to the approval.
- Retrieve the relevant customer and owner information.
- Create a delivery Epic and initial work items in Jira.
- Assign kickoff, setup, and implementation tasks according to predefined rules.
- Link the newly created work items to the Deal in Mria CRM.
- Notify the delivery team and account manager.
- Record the handoff in the Deal's CRM history.
Automation flow:
Project approved → Find Deal → Create delivery work → Assign owners → Link CRM records → Notify teams
The delivery team receives the initial project structure with the customer context already connected.
The account manager can follow progress through the Jira work linked to the Deal, while Engineering has access to the information required to get started.
This workflow can also connect relevant Confluence documentation to the CRM record, helping keep project and customer information accessible from the same place.
For companies managing many customer projects, automating preparation creates a more consistent onboarding process and reduces the coordination required for every new engagement.
What Makes Jira Automation with Mria CRM Different?
The examples above rely on different triggers and business rules, but they share an important characteristic: CRM records and Jira work can participate in the same automated process.
For teams evaluating Atlassian CRM solution, several capabilities make this approach particularly useful.
One Automation Engine for Jira and CRM Workflows
Mria CRM adds dedicated actions to Atlassian's existing automation builder.
You don't need to develop a separate automation service or use custom API requests for the CRM operations supported by these actions.
You can create, find, update, and link CRM records while continuing to use familiar Jira Automation features such as conditions, branches, smart values, and the audit log.
The same workflow can combine CRM actions with work-item creation, notifications, scheduled triggers, and other Jira actions.
Instead of maintaining separate automation tools for project management and CRM, teams can build both types of workflows using Atlassian Automation.
CRM Data Available Through Jira Custom Fields and JQL
Mria CRM provides five read-only Jira custom fields representing linked Leads, Deals, Contacts, Companies, and Products.
These fields expose 65 CRM properties through JQL parameters, enabling teams to combine customer-related conditions with ordinary Jira queries.
For example:
"Mria CRM Deals.Stage" in ("Negotiation", "Proposal Sent") AND status != Done
This query identifies unfinished Jira work associated with Deals in the selected stages.
The same information can support Jira filters, dashboards, and automation conditions.
Because these are native Jira custom fields, they work with Jira's existing search and automation capabilities.
This makes customer information useful across the Atlassian environment, even in workflows that don't directly create or update CRM records.
Native Links Between Customers and Jira Work
A customer relationship often involves multiple activities across different teams.
A Deal may depend on a technical assessment. A Contact may have several JSM requests. A feature request may be linked to multiple interested Leads.
Mria CRM connects those records directly to Jira work items.
Automation can use the existing links to identify which customer or opportunity is associated with a particular event.
It can also establish new links when creating work items or CRM records.
This reduces the need to maintain separate mapping tables or synchronization logic just to establish which records belong together.
Consistent CRM Business Logic and Permissions
Mria CRM automation actions operate through the same business logic used by the application.
When an automation updates a CRM record, the change is recorded in its timeline.
Relevant notifications, linked Jira fields, and pipeline calculations are updated accordingly.
The same validation rules apply, and actions respect the permissions of the connected Mria CRM account.
This matters for processes that change customer information automatically. The CRM continues to provide a consistent record of what happened and who initiated the change.
Automations That Run Without Jira Work Items
Some of the most valuable CRM automations don't involve a Jira work item at all.
Lead capture can start from an Incoming webhook. CRM clean-up can run on a schedule. Other processes can begin with manual triggers or calls from external applications.
Search Records and Advanced branching allow these flows to find and process lists of CRM records independently of Jira project activity.
This extends Jira Automation into everyday CRM operations without introducing a separate workflow engine.
Getting Started with Mria CRM Automation in Jira
If you're already using Jira Automation, the setup will be familiar.
First, install Mria CRM from the Atlassian Marketplace. Then open Jira Automation and create a new flow.
When adding an action, search for Mria CRM under Other apps. The first Mria CRM action you configure will prompt you to connect your CRM account.
Once connected, you can combine the CRM actions with supported Jira Automation triggers, conditions, branches, and smart values.
A few recommendations will help you build reliable workflows:
- Check for existing records before creating new ones. Create actions don't automatically deduplicate records. Use Find Record or Search Records and add the appropriate conditions before creating a Lead, Contact, or Deal.
- Start with a narrow scope. Test scheduled and bulk workflows against a small set of records before enabling them for a larger database.
- Account for search and processing limits. Search Records returns up to 150 records per run, and bulk update and note actions have their own limits.
- Choose the connection owner carefully. CRM actions run with the permissions of the connected account, and the connection belongs to that user.
- Review the audit log. Jira Automation provides execution results and errors, helping you understand whether a flow completed successfully.
Also, remember that these flows currently start from supported Jira Automation triggers, including Jira events, schedules, manual triggers, and webhooks. Dedicated triggers based directly on events inside Mria CRM are not part of this release.
You can find the complete list of actions, available fields, and configuration instructions in our Mria CRM Jira Automation documentation.
The documentation also includes ready-to-follow examples for Lead capture, scheduled CRM maintenance, Jira Service Management workflows, and delivery-related automations.
Bringing Customer Management into Jira Automation
With Mria CRM, Jira Automation can handle more than project and service management tasks. It can capture Leads, maintain CRM data, trigger sales follow-ups, and coordinate customer-related work across teams.
For companies using Jira, this makes a Jira-native CRM particularly valuable. Customer records become part of everyday workflows, helping teams reduce manual work and keep everyone informed.
Ready to automate your CRM workflows in Jira? Explore Mria CRM on the Atlassian Marketplace and check out our Jira Automation documentation to get started.
