Integration
Connect Request Tracker (RT) to Tomba
When Ticket Created fires in Request Tracker (RT), your agent runs Create Lead in Tomba. 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 Tomba 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) can start in Tomba
When Ticket Created in Request Tracker (RT)
then Create Lead in Tomba
When Ticket Status Changed in Request Tracker (RT)
then Domain Status in Tomba
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 Tomba
Triggers and actions 3 triggers · 37 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.
Action
Author FinderFinds the most likely email address of an article's author from the article's URL.
Action
Check technologiesDetect the technologies (CMS, analytics, frameworks, hosting and more) used by a website domain.
Action
Count EmailReturns the number of email addresses Tomba has found for a domain, with breakdowns by type, department and seniority.
Action
Create LeadCreate a new lead . If the email already exists, fails with 422 status code.
Action
Detect email formatDetect the email address pattern used by a company domain.
Action
Domain SearchFinds the email addresses Tomba knows for a company, looked up by website domain or company name, along with details about the organization.
Action
Domain StatusChecks whether a domain is a webmail provider or a disposable email domain.
Action
Email EnrichmentLooks up the person and company details Tomba has for an email address, such as name, job title, company, location and social profiles.
Action
Email VerifierVerify the deliverability of an email address.
Action
Enrich companyLook up company details (name, industry, location, social profiles, size, technologies) from a website domain.
Action
Find EmailFinds the most likely professional email address for a person from their name and a company domain or company name.
Action
Get employee locationsGet the breakdown of a company's employees by country, based on its domain name.
Action
Get LeadFetches a saved lead by ID, including its contact details, company, list, score, notes and custom attributes. An error occurs if the lead is not found.
Action
LinkedIn FinderEnter a LinkedIn profile URL to find the associated email address.
Action
Phone FinderFinds phone numbers for a contact from an email address, a company domain, or a LinkedIn profile URL.
Action
Phone ValidatorValidate a phone number and get its carrier, line type, country and formatted versions.
Action
Reveal companiesSearch Tomba's company database with a natural-language description or structured filters and return the matching companies.
Action
Similar DomainsFinds up to 25 companies and websites similar to a given domain.
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 Tomba
HubSpot to TombaHubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to TombaSalesforce is a leading enterprise customer relationship management (CRM) platform.
Slack to TombaSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Google Sheets to TombaGoogle Sheets
Gmail to TombaGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to TombaGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
Request Tracker (RT) and Tomba, 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 Tomba when something happens in Request Tracker (RT)?
Any of Tomba's 18 actions, including Create Lead, Author Finder, Check technologies and Count Email. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Tomba to Request Tracker (RT)?
Tomba has no triggers in the catalog today, so automations start in Request Tracker (RT). If you need the other direction, ask: your agent reads Tomba's API documentation and adds it.
Do I have to build a connector for Request Tracker (RT) or Tomba?
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.