Integration
Connect Jira Software Cloud to Avoma
When Issue Status Changed fires in Jira Software Cloud, your agent runs Update call in Avoma. Describe the whole flow and it is built, tested on every scenario and kept running.
What the catalog holds today. Ask for anything missing and your agent reads the API documentation and adds it.
Build solutions, not workarounds.
What do you want Jira Software Cloud and Avoma to do together?
Ask the assistant
Connect your AI client
Give your AI client this address.
https://mcp.apiant.aiOne connection does both: ask your client to act in an app once, or have it build an automation that keeps running. Any client that takes a remote MCP server. Nothing to install. Create your free account, then sign in once in your browser.
Set it up in your client
Claude Code
Run this in the directory you want to work in.
claude mcp add --transport http -s project apiant-ai https://mcp.apiant.aiStart Claude Code there, approve the server, and sign in in the browser page it opens.
Claude Code guide (opens in a new tab)Claude, web and desktop
Open Customize, then Connectors, then Add custom connector, and paste the address. On Team and Enterprise an owner adds it first.
Setup guide (opens in a new tab)Cursor
Add the address to your MCP configuration as a server URL. Cursor signs you in in your browser.
Setup guide (opens in a new tab)Zed
Open Settings, then AI, then MCP Servers, then Add Server, then Add Remote Server.
Setup guide (opens in a new tab)Codex and the ChatGPT desktop app
Open Settings, then MCP servers, then Add server, and choose Streamable HTTP. From the terminal, Codex takes the address with its own add command and then signs you in.
Setup guide (opens in a new tab)Any other MCP client
Paste the address where the client asks for a remote MCP server URL, and name the server apiant-ai where it lets you. APIANT's skills reach the client over the same connection.
Setup guide (opens in a new tab)Example flows
What Jira Software Cloud can start in Avoma
When Issue Status Changed in Jira Software Cloud
then Update call in Avoma
Starting points drawn from the triggers and actions in the catalog today. Describe the flow you need, at any depth, and your agent builds it and tests every scenario before it ships.
Everything your agent can do with Jira Software Cloud and Avoma
Triggers and actions 4 triggers · 29 actions
- Issue Status Changed
Triggered when an issue's status changes
- New Issue
Triggered when a new issue is created in Jira.
- New Issue (Via JQL)
Triggered when a new issue matching your JQL query is created.
- Updated Issue
Triggered when an issue is created or updated.
- Add Attachment to Issue
Uploads a file (fetched from a URL) and attaches it to a Jira issue.
- Add Comment to Issue
Adds a new comment to an issue.
- Add or Edit Form on Issue
Adds a form from a template to a Jira issue, or edits a form already on the issue, and optionally saves answers to it. Returns the resulting form.
- Add Watcher to Issue
Adds a user as a watcher of a Jira issue.
- Add Work Log to Issue
Logs time spent on a Jira issue as a new work log entry. Time tracking must be enabled on the Jira site.
- Create Issue
Creates a new issue.
- Delete Form
Deletes a form from a Jira issue.
- Find Issue
Returns the issues in a project whose summary matches the specified text, newest first.
- Find Issue by Key
Finds a Jira issue by its key (for example PROJ-123) or ID and returns its details, including custom field values.
- Find Issues by Filter
Returns the issues matched by a saved Jira filter.
- Find Issues (Via JQL)
Returns the Jira issues that match a JQL query.
- Find Project
Returns up to 50 Jira projects whose key or name contains the search text.
- Find User
Returns active Jira users whose display name or email address matches the search text, or whose account ID or user property matches.
- Get Attachment Content
Downloads the file content of a Jira issue attachment.
- Link Issues
Links two Jira issues with a link type such as Blocks, Duplicate or Relates, optionally adding a comment to the outward issue.
- List Issue Forms
Returns the forms attached to a Jira issue.
- Update Issue
Updates an existing issue.
- Get call
Returns a single Avoma call by its external ID, including its CRM links, recording URL, processing state and linked meeting.
- Get meeting
Returns a single Avoma meeting by its UUID, including its attendees, schedule, state, and recording and transcription details.
- Get meeting insights
Returns the AI notes, keyword occurrences, popular keywords and speakers for a completed Avoma meeting.
- Get recording
Returns the signed audio and video download links for the recording of an Avoma meeting. If the video is still being processed, returns a message instead of the links.
- Get transcription
Returns the transcript of a meeting's recording, including the speakers, the timed transcript text and a link to the VTT file.
- List calls
Returns the calls in your Avoma organization that started within a date range, optionally narrowed to inbound or outbound calls.
- List meetings
Returns the meetings in your Avoma organization that started within a date range, optionally filtered by attendee, CRM record, recording length or meeting type.
- List notes
Returns the AI-generated notes for meetings in a date range, optionally narrowed to one meeting or custom category.
- List scorecard evaluations
Returns completed scorecard evaluations for meetings, optionally narrowed by date range, scorecard template, meeting or evaluated user.
- List users
Returns the users in your Avoma organization, including each user's name, email, role, teams and status.
- Update call
Updates an existing call's details in Avoma, such as its subject, participant names, meeting purpose and outcome, or linked CRM records, and returns the updated call.
- Upload Audio Call
Creates a call in Avoma from a publicly reachable audio recording. Avoma downloads the recording and processes it into a transcript and notes, or uses a transcript you supply.
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.
Each app on its own
Reviews
What our customers say
More from Jira Software Cloud
Jira Software Cloud to SendGridSendGrid by Twilio — email delivery and marketing platform.
Jira Software Cloud to ChainlinkChainlink is a decentralized oracle network that feeds off-chain data to smart contracts.
Jira Software Cloud to HackMDHackMD is a realtime collaboration markdown editor to help developers and teams to manage their...
Jira Software Cloud to OpenRouterOpenRouter is a unified interface to AI models.
Jira Software Cloud to PM2.5 Open Data PortalThe PM2.5 Open Data Portal, run by the LASS community, publishes readings from a large network of low-cost...
Jira Software Cloud to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
More into Avoma
HubSpot to AvomaHubSpot is your all-in-one stop for all of your marketing software needs.
Slack to AvomaSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Google Sheets to AvomaGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Gmail to AvomaGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to AvomaGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
Jira Software Cloud and Avoma, answered
What can start an automation from Jira Software Cloud?
Any of Jira Software Cloud's 4 triggers in the catalog, including Issue Status Changed, New Issue, New Issue (Via JQL) and Updated Issue. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Avoma when something happens in Jira Software Cloud?
Any of Avoma's 12 actions, including Update call, Upload Audio Call, Get call and Get meeting. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Avoma to Jira Software Cloud?
Avoma has no triggers in the catalog today, so automations start in Jira Software Cloud. If you need the other direction, ask: your agent reads Avoma's API documentation and adds it.
Do I have to build a connector for Jira Software Cloud or Avoma?
No. Both are in the catalog with their triggers and actions. You describe the automation; your agent builds it, tests every scenario and keeps it running.
Can my AI client use Jira Software Cloud and Avoma without building an automation?
Yes. With your AI client connected to APIANT, ask it to do something in either app once and it runs that action on the spot. Ask for an automation and your agent builds it, tests every scenario and keeps it running. One connection covers both.
What happens when something fails?
Your agent works that out for you. It plans the failure paths along with the happy path, then tests every scenario before it ships.
Is there a free plan?
Yes. Every plan includes the agent, including free, and building from your own AI client spends no assistant credits.