Integration
Connect Request Tracker (RT) and Webmecanik Pipeline
When Ticket Created fires in Request Tracker (RT), your agent runs Update contact in Webmecanik Pipeline, or New Company in Webmecanik Pipeline to Create Ticket in Request Tracker (RT). 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 Request Tracker (RT) and Webmecanik Pipeline 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 Request Tracker (RT) and Webmecanik Pipeline can do together
From Request Tracker (RT) to Webmecanik Pipeline
When Ticket Created in Request Tracker (RT)
then Update contact in Webmecanik Pipeline
When Ticket Status Changed in Request Tracker (RT)
then Update or Create Contact in Webmecanik Pipeline
From Webmecanik Pipeline to Request Tracker (RT)
When New Company in Webmecanik Pipeline
then Create Ticket in Request Tracker (RT)
When New Contact in Webmecanik Pipeline
then Update ticket in Request Tracker (RT)
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 Request Tracker (RT) and Webmecanik Pipeline
Triggers and actions 9 triggers · 40 actions
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.
Trigger
New CompanyTriggers when a new company is added in Webmecanik Pipeline.
Trigger
New ContactTriggers when a new contact is added in Webmecanik Pipeline.
Trigger
New OpportunityTriggers when a new opportunity is created in Webmecanik Pipeline.
Trigger
Updated CompanyTriggers when a company is updated in Webmecanik Pipeline.
Trigger
Updated ContactTriggers when a contact is created or updated in Webmecanik Pipeline.
Trigger
Updated OpportunityTriggers when an opportunity is created or updated in Webmecanik Pipeline.
Action
Create ActivityCreates an activity (call, email, appointment, note or custom) on a contact or opportunity in Webmecanik Pipeline.
Action
Delete activityDeletes an activity from Webmecanik Pipeline.
Action
Delete companyDeletes a company from Webmecanik Pipeline.
Action
Delete contactDeletes a contact from Webmecanik Pipeline.
Action
Delete opportunityDeletes an opportunity from Webmecanik Pipeline.
Action
Get companyReturns one company by its slug, including its tags and custom fields.
Action
Get contactReturns one contact by its slug, including tags, companies, addresses and custom fields.
Action
Get opportunityReturns one opportunity by its slug, including its pipeline, status, tags and custom fields.
Action
List companiesReturns all companies in your Webmecanik Pipeline account, including their custom fields.
Action
List contactsReturns the contacts in your Webmecanik Pipeline account, optionally filtered by email, first name, last name or phone number.
Action
List opportunitiesReturns the opportunities in your Webmecanik Pipeline account, optionally only those of one pipeline.
Action
List pipelinesReturns all sales pipelines visible to the connected Webmecanik Pipeline user.
Action
List statusesReturns the statuses (pipeline stages) in Webmecanik Pipeline, optionally limited to one pipeline.
Action
List usersReturns all users in the Webmecanik Pipeline organization, with their name, email and role.
Action
Update activityUpdates an existing activity (call, email, note, appointment) attached to a contact or opportunity.
Action
Update companyUpdates an existing company in Webmecanik Pipeline, changing only the fields you fill in.
Action
Update contactUpdates an existing contact in Webmecanik Pipeline, including its custom field values, and returns the updated contact.
Action
Update opportunityUpdates an existing opportunity in Webmecanik Pipeline, changing only the values you supply.
Action
Update or Create CompanyCreates a company, or updates the existing one when a duplicate is found.
Action
Update or Create ContactCreates a contact, or updates the existing contact with the same email address.
Action
Update or Create OpportunityUpdates an existing opportunity when a slug is given, otherwise creates a new opportunity, and returns the resulting record.
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 Request Tracker (RT)
Request Tracker (RT) to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Request Tracker (RT) to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Request Tracker (RT) to StripeStripe is a payment processing platform for online businesses.
Request Tracker (RT) to ShopifyShopify is a commerce platform for online stores and retail point-of-sale.
Request Tracker (RT) to TrelloTrello is a visual collaboration tool that organizes projects into boards, lists, and cards.
Request Tracker (RT) to ZoomZoom unifies cloud video conferencing, simple online meetings, group messaging, and a software-based...
More into Webmecanik Pipeline
HubSpot to Webmecanik PipelineHubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to Webmecanik PipelineSalesforce is a leading enterprise customer relationship management (CRM) platform.
Slack to Webmecanik PipelineSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Google Sheets to Webmecanik PipelineGoogle Sheets
Gmail to Webmecanik PipelineGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to Webmecanik PipelineGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
Request Tracker (RT) and Webmecanik Pipeline, answered
What can start an automation from Request Tracker (RT)?
Any of Request Tracker (RT)'s 3 triggers in the catalog, including Ticket Created, Ticket Status Changed and Ticket Correspondence. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Webmecanik Pipeline when something happens in Request Tracker (RT)?
Any of Webmecanik Pipeline's 21 actions, including Create Activity, Update activity, Update company and Update contact. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Webmecanik Pipeline to Request Tracker (RT)?
Yes. When something happens in Webmecanik Pipeline, your agent can act in Request Tracker (RT) too. This page covers both directions: Webmecanik Pipeline's triggers and Request Tracker (RT)'s actions are listed here as well.
Do I have to build a connector for Request Tracker (RT) or Webmecanik Pipeline?
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 Request Tracker (RT) and Webmecanik Pipeline 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.