Integration
Connect Jira Service Management and Pipedrive
When New Request fires in Jira Service Management, your agent runs Add File to Deal in Pipedrive, or New Activity in Pipedrive to List customers in Jira Service Management. 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 Service Management and Pipedrive 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 Service Management and Pipedrive can do together
From Jira Service Management to Pipedrive
When New Request in Jira Service Management
then Add File to Deal in Pipedrive
From Pipedrive to Jira Service Management
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 Service Management and Pipedrive
Triggers and actions 9 triggers · 48 actions
- New Request
Triggers when a new customer request is raised in Jira Service Management.
- Updated Request
Triggers when a customer request in Jira Service Management is created or changed (status, fields or other details).
- Add comment
Adds a public or internal comment to a Jira Service Management customer request.
- Add organization
Adds an existing organization to a service desk so its members can raise requests there. Does nothing if the organization is already on the service desk.
- Add participants to request
Adds one or more users as participants on a Jira Service Management customer request and returns the request's participants.
- Create Request
Creates a customer request in a Jira Service Management service desk, using the chosen request type and its field values.
- Get request
Returns a customer request by its ID or key, including its summary, status, reporter and field values.
- List comments
Returns the comments on a Jira Service Management customer request, optionally filtered to public or internal comments.
- List customers
Returns the customers of a service desk, optionally filtered by name or email.
- List requests
Returns the customer requests visible to the connected user, optionally filtered by service desk, request type, status, ownership or a summary search.
- List request types
Returns the customer request types available in a Jira Service Management service desk, optionally filtered by group or search text.
- List service desk organizations
Returns the customer organizations associated with a service desk.
- List service desks
Returns all the service desks in your Jira Service Management site that you have access to, with each desk's id, project key and name.
- Deal Won
Triggers when a deal is marked as won in Pipedrive.
- New Activity
Triggers when a new activity is created.
- New Deal
Triggers when a new deal is created.
- New lead
Triggers when a new lead is added in Pipedrive.
- New Organization
Triggers when a new organization is added.
- New Person
Triggers when a new person (contact) is added.
- New Person (with Custom Fields and Labels)
Triggered when a new person (contact) is added. Includes custom fields and labels.
- Add File to Deal
Attaches a file to a deal, person, or organization by file URL reference.
- Add product
Creates a new product in your Pipedrive products catalog, with optional prices, tax, unit and custom field values.
- Create Activity
Creates a new activity (call, meeting, task, etc.).
- Create Deal
Adds a new deal to Pipedrive. Returns the created deal.
- Create Lead
Creates a new lead. Returns the created lead.
- Create Note
Adds a new note to a deal, person, or organization.
- Create Organization
Adds a new organization. Returns the created organization.
- Create Person
Adds a new person (contact). Returns the created person.
- Delete Activity
Marks an activity as deleted.
- Delete Deal
Marks a deal as deleted.
- Delete Organization
Marks an organization as deleted.
- Delete Person
Marks a person as deleted.
- Get Activity
Returns the details of one Pipedrive activity by its ID, including its subject, type, due date, linked records and participants.
- Get Deal
Returns the deal with the given ID.
- Get lead
Returns the details of a single Pipedrive lead by its ID, including its custom field values.
- Get Organization
Returns the organization with the given ID.
- Get Person
Returns the person with the given ID.
- Get product
Returns one Pipedrive product by its ID, including its prices and custom field values.
- Get related deals for person
Returns deals having the specified status that are related to the specified person.
- Get stage ID by stage name
Returns the stage id if the stage name exists.
- List activities
Returns the activities in the Pipedrive account, optionally narrowed by saved filter, owner, deal, lead, person, organization, done status or update time.
- List deals
Returns the deals in your Pipedrive account that are not archived, optionally filtered by owner, person, organization, pipeline, stage, status or update time.
- List organizations
Returns all organizations in the Pipedrive account, optionally narrowed by filter, owner, IDs or update time.
- List persons
Returns the persons in your Pipedrive account, optionally narrowed by filter, owner, organization, deal or update time.
- List pipelines
Returns all deal pipelines in the Pipedrive account, with their names and ids.
- List stages
Returns the stages in your Pipedrive account, optionally limited to one pipeline.
- Merge organizations
Merges two organization accounts. Info from the organization record to discard is merged into the organization record to keep.
- Merge persons
Merges two person accounts. Info from the person record to discard is merged into the person record to keep.
- Search Deals
Searches deals by term. Returns matching deals.
- Search Organizations
Searches organizations by term. Returns matching organizations.
- Search Persons
Searches persons by term (name, email, phone). Returns matching persons.
- Update Activity
Updates an existing activity by ID.
- Update Deal
Updates an existing deal by ID.
- Update lead
Updates an existing lead in Pipedrive. Only the values you fill in are changed.
- Update note
Updates an existing note in Pipedrive: its content, the deal, person, organization, lead, project or task it is attached to, its author, and its pinning.
- Update Organization
Updates an existing organization by ID.
- Update Person
Updates an existing person by ID.
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 Service Management
Jira Service Management to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Jira Service Management to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Jira Service Management to MailchimpMailchimp marketing automation and email platform.
Jira Service Management to StripeStripe is a payment processing platform for online businesses.
Jira Service Management to ShopifyShopify is a commerce platform for online stores and retail point-of-sale.
Jira Service Management to QuickBooks OnlineQuickBooks Online accounting — manage customers, invoices, bills, payments, vendors, expenses, and more via...
More into Pipedrive
HubSpot to PipedriveHubSpot is your all-in-one stop for all of your marketing software needs.
Gmail to PipedriveGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Notion to PipedriveA new tool that blends your everyday work apps into one. It's the all-in-one workspace for you and your team.
Airtable to PipedriveOrganize anything with Airtable, a modern database created for everyone.
Questions
Jira Service Management and Pipedrive, answered
What can start an automation from Jira Service Management?
Any of Jira Service Management's 2 triggers in the catalog, including New Request and Updated Request. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Pipedrive when something happens in Jira Service Management?
Any of Pipedrive's 37 actions, including Create Activity, Create Deal, Create Lead and Create Note. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Pipedrive to Jira Service Management?
Yes. When something happens in Pipedrive, your agent can act in Jira Service Management too. This page covers both directions: Pipedrive's triggers and Jira Service Management's actions are listed here as well.
Do I have to build a connector for Jira Service Management or Pipedrive?
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 Service Management and Pipedrive 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.