Integration
Connect Clientify and Request Tracker (RT)
When New Contact fires in Clientify, your agent runs Create Ticket in Request Tracker (RT), or Ticket Created in Request Tracker (RT) to Add task in Clientify. 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 Clientify and Request Tracker (RT) 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 Clientify and Request Tracker (RT) can do together
From Clientify to Request Tracker (RT)
When New Contact in Clientify
then Create Ticket in Request Tracker (RT)
From Request Tracker (RT) to Clientify
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 Clientify and Request Tracker (RT)
Triggers and actions 6 triggers · 34 actions
- New Contact
Triggers when a new contact is created in Clientify.
- New Deal
Triggers when a new deal is created in Clientify.
- New Task
Triggers when a new task is created in Clientify.
- Add company
Creates a company in Clientify with its contact details, address, tags and custom field values.
- Add task
Creates a task in Clientify, optionally assigned to a user and linked to contacts, companies and deals.
- Create Abandoned Cart
Creates an abandoned shopping cart for a Clientify contact, with the cart's items, shop and currency.
- Create Contact
Creates a contact in Clientify. If a contact with the same email or phone already exists it is updated instead, unless forced insert is turned on.
- Create Deal
Creates a deal in Clientify, optionally linked to a contact and company and placed in a pipeline stage.
- Create Order
Creates an order in Clientify for a contact, with its line items.
- Delete contact
Deletes a contact from Clientify.
- Find Contact
Finds contacts by name, surname or email, optionally narrowed by phone, source, type or dates, and returns the matches.
- Get company
Returns the full details of a Clientify company by its id, including contact info, tags, custom fields and employees.
- Get contact
Returns a Clientify contact's full details, including emails, phones, addresses, tags and custom fields.
- Get deal
Returns a Clientify deal by its id, including amount, stage, pipeline, involved contacts and companies, tasks and custom fields.
- List contacts
Returns the contacts in your Clientify account, optionally filtered by name/email, phone, source, type, or created/modified dates.
- Update company
Updates an existing company in Clientify and returns the updated record.
- Update contact
Updates an existing Clientify contact's name, title, company, status and notes. Fields left blank keep their current values.
- Update deal
Updates an existing Clientify deal, changing only the fields you fill in.
- 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.
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 Clientify
Clientify to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
Clientify to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Clientify to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Clientify to Google SheetsGoogle Sheets
Clientify to GmailGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Clientify to Google CalendarGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
More into Request Tracker (RT)
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
Clientify and Request Tracker (RT), answered
What can start an automation from Clientify?
Any of Clientify's 3 triggers in the catalog, including New Contact, New Deal and New Task. 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 Clientify?
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 Clientify?
Yes. When something happens in Request Tracker (RT), your agent can act in Clientify too. This page covers both directions: Request Tracker (RT)'s triggers and Clientify's actions are listed here as well.
Do I have to build a connector for Clientify 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.
Can my AI client use Clientify and Request Tracker (RT) 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.