Integration
Connect Request Tracker (RT) and Skyvern
When Ticket Created fires in Request Tracker (RT), your agent runs Create and Run a Task in Skyvern, or New or Updated Skyvern Workflow in Skyvern 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 Skyvern 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 Request Tracker (RT) and Skyvern can do together
From Request Tracker (RT) to Skyvern
When Ticket Created in Request Tracker (RT)
then Create and Run a Task in Skyvern
From Skyvern to 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 Skyvern
Triggers and actions 4 triggers · 34 actions
- Ticket Correspondence
Triggers when a ticket is replied to (that is, corresponded with).
- Ticket Created
Triggers when a new Request Tracker ticket is created.
- Ticket Status Changed
Triggers when a Request Tracker ticket changes status. Can watch for any status change or only for changes to a specific status.
- Add asset
Create an asset.
- Add user
Create a user.
- Comment on a Ticket
Add an internal comment to a ticket and send to any internal watchers.
- Create Ticket
Create a new ticket in Request Tracker.
- Find Attachment
Locate an attachment by ID.
- Find Ticket
Locate a ticket by ID.
- Find Tickets
Issue a query to find matching tickets.
- Find Transaction
Find a transaction by ID
- Get asset
Retrieves one asset by ID: name, description, status, catalog, owner, held by, contact, custom fields.
- Get queue
Get a queue by id or name.
- Get user
Get a user by id or name.
- List queues
List all queues visible to user.
- List ticket history
List transactions of a ticket.
- Reply to a Ticket
Reply to the requestor and any internal or external watchers of a ticket.
- Update ticket
General ticket update (Owner, Priority, Queue, custom fields).
- Update Ticket Due Date
Update the due date of a ticket.
- Update Ticket Status
Update the status of a ticket.
- Update Ticket Subject
Update the subject of a ticket.
- Update user
Update a user.
- New or Updated Skyvern Workflow
Triggers when a Skyvern workflow (agent) is created or a new version of it is saved.
- Add browser session
Creates a Skyvern browser session that persists across multiple task and workflow runs, and returns its session id and live-view link.
- Add credential
Creates a new stored credential (login, credit card or secret) in your Skyvern organization for use by tasks and agents.
- Add workflow
Creates a new Skyvern workflow (agent) from a JSON or YAML definition and returns the saved workflow.
- Cancel run
Cancels a running Skyvern task run or workflow run by its id.
- Create and Run a Task
Starts a Skyvern browser-automation task from a plain-language prompt and returns the new run, including its id, status and link in the Skyvern app.
- Create and Run Task V2
Starts a Skyvern 2.0 browser task from a natural-language prompt and returns the new run's id and status.
- Delete workflow
Deletes a Skyvern workflow (agent) by its ID.
- Get a Browser Session
Returns the details of a Skyvern browser session, including its status, browser address for connecting, downloaded files and recordings.
- Get a Task
Returns a Skyvern task run by its id, including its status, extracted output, downloaded files, recording and screenshots.
- Get a Task V2
Returns the status, output, recording and screenshots of a Skyvern task run.
- Get a Workflow
Returns a Skyvern workflow (agent) by its permanent id, including its blocks, parameters and settings.
- List credentials
Returns the credentials stored in your Skyvern organization, optionally filtered by vault, type or search text. Secrets are never included.
- List runs
Returns your organization's task and agent runs, newest first, optionally filtered by status, run type, agent, tags, failure category or a search term.
- List workflows
Returns the workflows (agents) in your Skyvern organization, optionally filtered by search text, folder, status or tags. Returns up to 100 workflows.
- Run a Workflow
Starts a run of one of your Skyvern workflows (agents) with the parameters you supply, and returns the new run's id, status and link.
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 Skyvern
HubSpot to SkyvernHubSpot is your all-in-one stop for all of your marketing software needs.
Google Sheets to SkyvernGoogle Sheets
Gmail to SkyvernGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to SkyvernGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Google Drive to SkyvernGoogle Drive is a cloud storage solution for uploading, sharing, and collaborating on files across devices...
Questions
Request Tracker (RT) and Skyvern, 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 Skyvern when something happens in Request Tracker (RT)?
Any of Skyvern's 15 actions, including Create and Run a Task, Create and Run Task V2, Add browser session and Add credential. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Skyvern to Request Tracker (RT)?
Yes. When something happens in Skyvern, your agent can act in Request Tracker (RT) too. This page covers both directions: Skyvern'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 Skyvern?
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.