Integration
Connect Request Tracker (RT) to Commonsku
When Ticket Created fires in Request Tracker (RT), your agent runs Add client contact in Commonsku. 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 Commonsku 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) can start in Commonsku
When Ticket Created in Request Tracker (RT)
then Add client contact in Commonsku
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 Commonsku
Triggers and actions 3 triggers · 40 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.
- 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.
- Add client
Creates a new client in commonsku.
- Add client address
Creates a new address in a client's address book and returns the created address.
- Add client contact
Creates a contact for a commonsku client and returns the new contact.
- Add project
Creates a new project for an existing client in commonsku.
- Add tag
Creates a tag in your commonsku company, or returns the existing tag if one with the same label already exists.
- Delete client
Deletes a client from commonsku by ID, along with all of its contacts and addresses, and returns the deleted client.
- Find products by keyword
Returns the products whose name, supplier code or tag match a keyword, optionally narrowed by supplier, division, tag, owner or net price.
- Get client
Returns the details of a single Commonsku client, including its terms, industry, status and tags. An error occurs if the client is not found.
- Get invoice
Returns a single invoice, including its customer, billing and shipping details, line items and totals. An error occurs if the invoice is not found.
- Get product
Returns the full details of a single product by its ID, including its colors, sizes, imprints, images, SKUs, costs and prices. An error occurs if the product is not found.
- Get project
Returns the details of a single commonsku project by its ID.
- List client contacts
Returns the contacts associated with a commonsku client, including names, email, department and phone numbers.
- List clients
Returns the clients in your commonsku account, optionally filtered by customer number, client name, credit hold status or last-updated date.
- List invoices
Returns invoices in your commonsku account, optionally filtered by status, customer, numbers or dates.
- List products
Returns products in your commonsku account, optionally filtered by keyword, supplier, division, tag or price, or by a special mode such as popular or recently used products.
- List projects
Returns the projects in your commonsku account, optionally filtered by client, dates or project number.
- List purchase orders
Returns the purchase orders in your commonsku account, optionally filtered by status, client, order numbers, dates or tracking number.
- List sales orders
Returns the sales orders in your commonsku account, optionally filtered by status, client, numbers and date ranges.
- List tags
Returns the tags defined in your commonsku company, optionally limited to one record, one record type, or a label search.
- Update client
Updates an existing commonsku client's name, payment terms, industry, rep, website, status, credit hold and tags.
- Update contact
Updates an existing client contact's name, email or department in commonsku.
- Update product
Updates an existing product in commonsku. Only the fields you fill in are changed.
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 Commonsku
HubSpot to CommonskuHubSpot is your all-in-one stop for all of your marketing software needs.
Google Sheets to CommonskuGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Gmail to CommonskuGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to CommonskuGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
Request Tracker (RT) and Commonsku, 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 Commonsku when something happens in Request Tracker (RT)?
Any of Commonsku's 22 actions, including Update client, Update contact, Update product and Add client. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Commonsku to Request Tracker (RT)?
Commonsku has no triggers in the catalog today, so automations start in Request Tracker (RT). If you need the other direction, ask: your agent reads Commonsku's API documentation and adds it.
Do I have to build a connector for Request Tracker (RT) or Commonsku?
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 Commonsku 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.