Integration
Connect Coworks and Jira Software Cloud
When Contact Updated fires in Coworks, your agent runs Add Attachment to Issue in Jira Software Cloud, or Issue Status Changed in Jira Software Cloud to List CRM contacts and leads in Coworks. 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 Coworks and Jira Software Cloud 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 Coworks and Jira Software Cloud can do together
From Coworks to Jira Software Cloud
When Contact Updated in Coworks
then Add Attachment to Issue in Jira Software Cloud
From Jira Software Cloud to Coworks
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 Coworks and Jira Software Cloud
Triggers and actions 14 triggers · 24 actions
- Contact Updated
Triggers when a contact in your Coworks CRM is created or changed.
- CRM Entry Updated
Triggers when a CRM contact or lead is added or changed in Coworks.
- Lead Updated
Triggers when a lead in Coworks is created or changed, including changes to its status, custom fields, or any other returned detail.
- Member Deactivate
Triggered when a member is deactivated and is no longer an active member.
- Member Updated
Triggers when a member is added or any of a member's details change.
- New Checkin
Triggered when a new check-in is recorded for a member, visitor or passport holder in your Coworks community.
- New Contact
Triggered when a new contact is created in your Coworks CRM.
- New CRM Entry
Triggered when a new CRM entry, either a contact or a lead, is created.
- New Lead
Triggers when a new lead is created in the Coworks CRM.
- New Member
Triggered when a new member is created in your Coworks community.
- Get room occupancy
Returns the rooms at a campus with their occupancy, optionally limited to one room type.
- List active memberships
Returns the community's paid memberships, optionally limited to one status. Free subscriptions are not included.
- List checkins
Returns check-ins for your Coworks community, optionally filtered by campus, check-in type, date range or person name.
- List CRM contacts and leads
Returns the contacts and leads in your Coworks CRM, optionally filtered by campus, type, lead status, source and date.
- List members
Returns the members of your Coworks community, optionally narrowed to specific teams or a campus, and optionally including inactive members.
- List rooms
Returns the rooms at a campus, optionally narrowed to one room type.
- List teams
Returns the teams in your Coworks community, optionally narrowed by team, campus, or join date.
- 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.
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 Coworks
Coworks to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
Coworks to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Coworks to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Coworks to Google SheetsGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Coworks to GmailGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Coworks to Google CalendarGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
More into Jira Software Cloud
Erpnext to Jira Software CloudOpen-source ERP system for accounting, inventory, manufacturing, sales, projects, and CRM.
Google Drive to Jira Software CloudGoogle Drive is a cloud storage solution for uploading, sharing, and collaborating on files across devices...
Questions
Coworks and Jira Software Cloud, answered
What can start an automation from Coworks?
Any of Coworks's 10 triggers in the catalog, including Contact Updated, CRM Entry Updated, Lead Updated and Member Updated. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Jira Software Cloud when something happens in Coworks?
Any of Jira Software Cloud's 17 actions, including Create Issue, Update Issue, Add Attachment to Issue and Add Comment to Issue. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Jira Software Cloud to Coworks?
Yes. When something happens in Jira Software Cloud, your agent can act in Coworks too. This page covers both directions: Jira Software Cloud's triggers and Coworks's actions are listed here as well.
Do I have to build a connector for Coworks or Jira Software Cloud?
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 Coworks and Jira Software Cloud 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.