Integration
Connect Request Tracker (RT) and Userflow
When Ticket Created fires in Request Tracker (RT), your agent runs Create/Update User in Userflow, or Checklist Completed in Userflow 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 Userflow 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 Userflow can do together
From Request Tracker (RT) to Userflow
When Ticket Created in Request Tracker (RT)
then Create/Update User in Userflow
From Userflow 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 Userflow
Triggers and actions 17 triggers · 24 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.
- Checklist Completed
Triggered when a user finishes every task in a Userflow checklist.
- Checklist Dismissed/Ended
Triggered when a Userflow checklist ends for a user — because they dismissed it, it was completed, or it stopped applying to them. The reason is in checklist_end_reason.
- Checklist Started
Triggered when a user starts a Userflow checklist. Why it started is in checklist_start_reason.
- Checklist Task Completed
Triggered when a user completes a single task inside a Userflow checklist.
- Event Tracked
Triggered when Userflow tracks an event for a user — either your own custom events or Userflow's own flow and checklist events. Name one event to watch, or leave it blank to fire for all of them.
- Flow Completed
Triggered when a user completes a Userflow flow by reaching its goal step.
- Flow Dismissed/Ended
Triggered when a Userflow flow ends for a user — because they dismissed it, finished it, or it stopped applying. The reason is in flow_end_reason.
- Flow Started
Triggered when a user starts a Userflow flow. Why it started is in flow_start_reason.
- Group Created/Updated
Triggered when a group (a company or account) is created or changed in Userflow.
- Launcher Activated
Triggered when a user clicks a Userflow launcher (a beacon, button or hotspot) to open it.
- Launcher Dismissed
Triggered when a user dismisses a Userflow launcher (a beacon, button or hotspot).
- Launcher Seen
Triggered when a Userflow launcher (a beacon, button or hotspot) is shown to a user.
- Question Answered
Triggered when a user answers a question in a Userflow flow — a survey, NPS or rating step. The answer arrives as text, a number, or a list depending on the question type.
- User Created/Updated
Triggered when a user is created or changed in Userflow.
- Create/Update Group
Creates a group (a company or account) in Userflow, or updates it if a group with that ID already exists. Only the attributes you send are changed.
- Create/Update User
Creates a user in Userflow, or updates them if a user with that ID already exists. Only the attributes you send are changed. Optionally adds the user to a group.
- Find Group
Finds groups (companies or accounts) in Userflow by name. Userflow's API cannot filter on the server, so this reads up to 300 groups and matches them here; leave the name blank to just list them.
- Find User
Finds users in Userflow by email or name. Userflow's API cannot filter on the server, so this reads up to 300 users and matches them here; leave both fields blank to just list them.
- Track Event
Tracks an event for a user in Userflow, so you can use it to start flows or checklists and to segment users.
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 Userflow
Agile CRM to UserflowAgile CRM is an all-in-one CRM with sales, marketing, and service automation.
Telegram to UserflowTelegram is a cloud-based instant messaging and voice over IP service developed by Telegram Messenger LLP.
HubSpot to UserflowHubSpot is your all-in-one stop for all of your marketing software needs.
Google Sheets to UserflowGoogle Sheets
Questions
Request Tracker (RT) and Userflow, 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 Userflow when something happens in Request Tracker (RT)?
Any of Userflow's 5 actions, including Create/Update Group, Create/Update User, Find Group and Find User. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Userflow to Request Tracker (RT)?
Yes. When something happens in Userflow, your agent can act in Request Tracker (RT) too. This page covers both directions: Userflow'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 Userflow?
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.