Integration
Connect Pipedrive and Request Tracker (RT)
When New Activity fires in Pipedrive, your agent runs Create Ticket in Request Tracker (RT), or Ticket Created in Request Tracker (RT) to Create Deal in Pipedrive. 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 Pipedrive and Request Tracker (RT) to do together?
Ask the assistant
Connect your AI client
Give your AI client this address.
https://mcp.apiant.aiAny 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 Pipedrive and Request Tracker (RT) can do together
From Pipedrive to Request Tracker (RT)
When New Activity in Pipedrive
then Create Ticket in Request Tracker (RT)
When New Deal in Pipedrive
then Update ticket in Request Tracker (RT)
From Request Tracker (RT) to Pipedrive
When Ticket Created in Request Tracker (RT)
then Create Deal in Pipedrive
When Ticket Status Changed in Request Tracker (RT)
then Create Lead in Pipedrive
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 Pipedrive and Request Tracker (RT)
Triggers and actions 8 triggers · 43 actions
Trigger
New ActivityTriggers when a new activity is created.
Trigger
New DealTriggers when a new deal is created.
Trigger
New OrganizationTriggers when a new organization is added.
Trigger
New PersonTriggers when a new person (contact) is added.
Trigger
New Person (with Custom Fields and Labels)Triggered when a new person (contact) is added. Includes custom fields and labels.
Action
Create ActivityCreates a new activity (call, meeting, task, etc.).
Action
Create DealAdds a new deal to Pipedrive. Returns the created deal.
Action
Create LeadCreates a new lead. Returns the created lead.
Action
Create NoteAdds a new note to a deal, person, or organization.
Action
Create OrganizationAdds a new organization. Returns the created organization.
Action
Create PersonAdds a new person (contact). Returns the created person.
Action
Delete ActivityMarks an activity as deleted.
Action
Delete DealMarks a deal as deleted.
Action
Delete OrganizationMarks an organization as deleted.
Action
Delete PersonMarks a person as deleted.
Action
Get DealReturns the deal with the given ID.
Action
Get OrganizationReturns the organization with the given ID.
Action
Get PersonReturns the person with the given ID.
Action
Get related deals for personReturns deals having the specified status that are related to the specified person.
Action
Get stage ID by stage nameReturns the stage id if the stage name exists.
Action
Merge organizationsMerges two organization accounts. Info from the organization record to discard is merged into the organization record to keep.
Action
Merge personsMerges two person accounts. Info from the person record to discard is merged into the person record to keep.
Action
Search DealsSearches deals by term. Returns matching deals.
Action
Search OrganizationsSearches organizations by term. Returns matching organizations.
Action
Search PersonsSearches persons by term (name, email, phone). Returns matching persons.
Action
Update ActivityUpdates an existing activity by ID.
Action
Update DealUpdates an existing deal by ID.
Action
Update OrganizationUpdates an existing organization by ID.
Action
Update PersonUpdates an existing person by ID.
Trigger
Ticket CorrespondenceTriggers when a ticket is replied to (that is, corresponded with).
Trigger
Ticket CreatedTriggers when a new Request Tracker ticket is created.
Trigger
Ticket Status ChangedTriggers when a Request Tracker ticket changes status. Can watch for any status change or only for changes to a specific status.
Action
Add assetCreate an asset.
Action
Add userCreate a user.
Action
Comment on a TicketAdd an internal comment to a ticket and send to any internal watchers.
Action
Create TicketCreate a new ticket in Request Tracker.
Action
Find AttachmentLocate an attachment by ID.
Action
Find TicketLocate a ticket by ID.
Action
Find TicketsIssue a query to find matching tickets.
Action
Find TransactionFind a transaction by ID
Action
Get assetRetrieves one asset by ID: name, description, status, catalog, owner, held by, contact, custom fields.
Action
Get queueGet a queue by id or name.
Action
Get userGet a user by id or name.
Action
List queuesList all queues visible to user.
Action
List ticket historyList transactions of a ticket.
Action
Reply to a TicketReply to the requestor and any internal or external watchers of a ticket.
Action
Update ticketGeneral ticket update (Owner, Priority, Queue, custom fields).
Action
Update Ticket Due DateUpdate the due date of a ticket.
Action
Update Ticket StatusUpdate the status of a ticket.
Action
Update Ticket SubjectUpdate the subject of a ticket.
Action
Update userUpdate a user.
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 Pipedrive
Pipedrive to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Pipedrive to Google SheetsGoogle Sheets
Pipedrive to Google CalendarGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Pipedrive to Google DriveGoogle Drive is a cloud storage solution for uploading, sharing, and collaborating on files across devices...
Pipedrive to MailchimpMailchimp marketing automation and email platform.
Pipedrive to ShopifyShopify is a commerce platform for online stores and retail point-of-sale.
More into Request Tracker (RT)
HubSpot to Request Tracker (RT)HubSpot is your all-in-one stop for all of your marketing software needs.
Google Sheets to Request Tracker (RT)Google Sheets
Gmail to Request Tracker (RT)Gmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to Request Tracker (RT)Google Calendar is a time management tool providing scheduling features, event reminders, and integration...
Google Drive to Request Tracker (RT)Google Drive is a cloud storage solution for uploading, sharing, and collaborating on files across devices...
Mailchimp to Request Tracker (RT)Mailchimp marketing automation and email platform.
Questions
Pipedrive and Request Tracker (RT), answered
What can start an automation from Pipedrive?
Any of Pipedrive's 5 triggers in the catalog, including New Activity, New Deal, New Organization and New Person. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Request Tracker (RT) when something happens in Pipedrive?
Any of Request Tracker (RT)'s 19 actions, including Create Ticket, Update ticket, Update Ticket Due Date and Update Ticket Status. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Request Tracker (RT) to Pipedrive?
Yes. When something happens in Request Tracker (RT), your agent can act in Pipedrive too. This page covers both directions: Request Tracker (RT)'s triggers and Pipedrive's actions are listed here as well.
Do I have to build a connector for Pipedrive or Request Tracker (RT)?
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.
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.