Integration
Connect Jira Software Cloud and ProWorkflow Classic
When Issue Status Changed fires in Jira Software Cloud, your agent runs Add Contact in ProWorkflow Classic, or New Company in ProWorkflow Classic to Add Attachment to Issue in Jira Software Cloud. 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 ProWorkflow Classic 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)Grok
Open grok.com/connectors, choose New Connector, then Custom, and paste the address. Grok signs you in in your browser.
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 and ProWorkflow Classic can do together
From Jira Software Cloud to ProWorkflow Classic
When Issue Status Changed in Jira Software Cloud
then Add Contact in ProWorkflow Classic
When New Issue in Jira Software Cloud
then Update Contact in ProWorkflow Classic
From ProWorkflow Classic to Jira Software Cloud
When New Company in ProWorkflow Classic
then Add Attachment to Issue in Jira Software Cloud
When New Contact in ProWorkflow Classic
then Add Comment to Issue in Jira Software Cloud
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 ProWorkflow Classic
Triggers and actions 9 triggers · 27 actions
Trigger
Issue Status ChangedTriggered when an issue's status changes
Trigger
New IssueTriggered when a new issue is created in Jira.
Trigger
New Issue (Via JQL)Triggered when a new issue matching your JQL query is created.
Trigger
Updated IssueTriggered when an issue is created or updated.
Action
Add Attachment to IssueUploads a file (fetched from a URL) and attaches it to a Jira issue.
Action
Add Comment to IssueAdds a new comment to an issue.
Action
Add or Edit Form on IssueAdds 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.
Action
Add Watcher to IssueAdds a user as a watcher of a Jira issue.
Action
Add Work Log to IssueLogs time spent on a Jira issue as a new work log entry. Time tracking must be enabled on the Jira site.
Action
Create IssueCreates a new issue.
Action
Delete FormDeletes a form from a Jira issue.
Action
Find IssueReturns the issues in a project whose summary matches the specified text, newest first.
Action
Find Issue by KeyFinds a Jira issue by its key (for example PROJ-123) or ID and returns its details, including custom field values.
Action
Find Issues by FilterReturns the issues matched by a saved Jira filter.
Action
Find Issues (Via JQL)Returns the Jira issues that match a JQL query.
Action
Find ProjectReturns up to 50 Jira projects whose key or name contains the search text.
Action
Find UserReturns active Jira users whose display name or email address matches the search text, or whose account ID or user property matches.
Action
Get Attachment ContentDownloads the file content of a Jira issue attachment.
Action
Link IssuesLinks two Jira issues with a link type such as Blocks, Duplicate or Relates, optionally adding a comment to the outward issue.
Action
List Issue FormsReturns the forms attached to a Jira issue.
Action
Update IssueUpdates an existing issue.
Trigger
New CompanyTriggers when a new company is added in ProWorkflow.
Trigger
New ContactTriggers when a new contact is added in ProWorkflow.
Trigger
New ProjectTriggers when a new project is added in ProWorkflow.
Trigger
New TaskTriggers when a new task is added to a ProWorkflow project.
Trigger
New TimeTriggers when a new time record is logged in ProWorkflow.
Action
Add CompanyCreates a company (client, contractor, staff or other) in ProWorkflow.
Action
Add ContactCreates a contact in ProWorkflow.
Action
Add TimeLogs a time record against a ProWorkflow task.
Action
Delete ContactDeletes a contact from ProWorkflow.
Action
Find ContactReturns a ProWorkflow contact by its ID.
Action
Find TaskReturns a ProWorkflow task by its ID.
Action
Make Task ActiveSets a ProWorkflow task's status to active.
Action
Update ContactUpdates an existing contact in ProWorkflow.
Action
Update Contact LocationUpdates the address (street, city, state, postal code and country) of an existing ProWorkflow contact.
Action
Update ProjectUpdates an existing project in ProWorkflow.
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 ProWorkflow Classic
HubSpot to ProWorkflow ClassicHubSpot is your all-in-one stop for all of your marketing software needs.
Google Sheets to ProWorkflow ClassicGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Gmail to ProWorkflow ClassicGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to ProWorkflow ClassicGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Google Drive to ProWorkflow ClassicGoogle Drive is a cloud storage solution for uploading, sharing, and collaborating on files across devices...
Mailchimp to ProWorkflow ClassicMailchimp marketing automation and email platform.
Questions
Jira Software Cloud and ProWorkflow Classic, 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 ProWorkflow Classic when something happens in Jira Software Cloud?
Any of ProWorkflow Classic's 10 actions, including Update Contact, Update Contact Location, Update Project and Add Company. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from ProWorkflow Classic to Jira Software Cloud?
Yes. When something happens in ProWorkflow Classic, your agent can act in Jira Software Cloud too. This page covers both directions: ProWorkflow Classic's triggers and Jira Software Cloud's actions are listed here as well.
Do I have to build a connector for Jira Software Cloud or ProWorkflow Classic?
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 ProWorkflow Classic 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.