--- title: "Connect Request Tracker (RT) to Support Board - APIANT.ai" description: "When \"Ticket Created\" fires in Request Tracker (RT), your agent runs \"Send Message\" in Support Board." canonical: "https://apiant.ai/connect/request-tracker-rt-to-support-board" --- # Connect Request Tracker (RT) to Support Board When **Ticket Created** fires in [Request Tracker (RT)](https://apiant.ai/connections/request-tracker-rt), your agent runs **Send Message** in [Support Board](https://apiant.ai/connections/support-board). Describe the whole flow and it is built, tested on every scenario and kept running. Request Tracker (RT) **3** triggers Request Tracker (RT) **19** actions Support Board **36** actions What the catalog holds today. Ask for anything missing and your agent reads the API documentation and adds it. ## What do you want Request Tracker (RT) and Support Board to do together? Give your AI client this address. `https://mcp.apiant.ai` One 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.ai` Start Claude Code there, approve the server, and sign in in the browser page it opens. [Claude Code guide (opens in a new tab)](https://apiant.ai/docs/mcp/claude-code) ### 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)](https://apiant.ai/docs/mcp) ### 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)](https://apiant.ai/docs/mcp) ### Zed Open Settings, then AI, then MCP Servers, then Add Server, then Add Remote Server. [Setup guide (opens in a new tab)](https://apiant.ai/docs/mcp) ### 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)](https://apiant.ai/docs/mcp) ### 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)](https://apiant.ai/docs/mcp) Example flows ## What Request Tracker (RT) can start in Support Board - When **Ticket Created** in Request Tracker (RT) then **Send Message** in Support Board - When **Ticket Status Changed** in Request Tracker (RT) then **Update Conversation Status** in Support Board 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 Support Board ## Triggers and actions 3 triggers · 55 actions - Trigger **Ticket Correspondence** Triggers when a ticket is replied to (that is, corresponded with). - Trigger **Ticket Created** Triggers when a new Request Tracker ticket is created. - Trigger **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. - Action **Add asset** Create an asset. - Action **Add user** Create a user. - Action **Comment on a Ticket** Add an internal comment to a ticket and send to any internal watchers. - Action **Create Ticket** Create a new ticket in Request Tracker. - Action **Find Attachment** Locate an attachment by ID. - Action **Find Ticket** Locate a ticket by ID. - Action **Find Tickets** Issue a query to find matching tickets. - Action **Find Transaction** Find a transaction by ID - Action **Get asset** Retrieves one asset by ID: name, description, status, catalog, owner, held by, contact, custom fields. - Action **Get queue** Get a queue by id or name. - Action **Get user** Get a user by id or name. - Action **List queues** List all queues visible to user. - Action **List ticket history** List transactions of a ticket. - Action **Reply to a Ticket** Reply to the requestor and any internal or external watchers of a ticket. - Action **Update ticket** General ticket update (Owner, Priority, Queue, custom fields). - Action **Update Ticket Due Date** Update the due date of a ticket. - Action **Update Ticket Status** Update the status of a ticket. - Action **Update Ticket Subject** Update the subject of a ticket. - Action **Update user** Update a user. - Action **Add Conversation** Creates a new conversation. - Action **Add Note** Adds a new note to a conversation. - Action **Add User** Create a new user in Support Board. - Action **Delete Message** Deletes an existing message. - Action **Delete Note** Deletes a note from a conversation. - Action **Delete User** Deletes a user and all linked conversations and messages. - Action **Delete Users** Deletes multiple users and all linked conversations and messages. - Action **Direct Message** Sends a direct chat message. - Action **Get Agents in Conversation** Returns an array with all the agents with at least one message in the conversation. - Action **Get Conversation** Returns a conversation and the messages of the conversation. - Action **Get Conversations** Returns all the conversations. Each conversation includes the last message of the conversation. - Action **Get External Setting** Returns an external setting. External settings are saved on a dedicated database row. - Action **Get Last Agent in Conversation** Returns the last agent who answered a conversation. - Action **Get Last Message** Returns the last message in a conversation. - Action **Get Multi Setting** Returns a subsetting of another setting. - Action **Get New Conversations** Returns the conversations created after the given date/ID or with a message created after the given date/ID. Each conversation includes the last message of the conversation. - Action **Get New Messages** Returns the messages of a conversation created after the given date/ID. - Action **Get New User Conversations** Returns the user conversations created after the given date/ID or with a message created after the given date/ID. Each conversation includes the last message of the conversation. - Action **Get Notes** Returns the internal notes of a conversation. - Action **Get Setting** Returns a setting saved in the Settings area. - Action **Get Settings** Returns an array with all the settings. - Action **Get User** Returns one user's details (name, email, type, extra details) by user ID via api.php function=get-user; returns false when the user does not exist. - Action **Get User Conversations** Returns the conversations of a user. Each conversation includes the last message of the conversation. - Action **Google Translate** Translates multiple strings via Google Translate. - Action **Login** Logins a user or agent. A user can log in in two ways: via email and password, or via user ID and token. The last value of the response is the encrypted login data ready to be stored in the sb-login cookie. Use the function SBF.loginCookie(response[1]); to store it. Returns false if login is unsuccessful. - Action **Push Notification** Sends a Push notification to an agent, a group of agents, or all agents. Push notifications must be enabled in the settings area. - Action **Search Conversations** Returns the conversations matching the search. - Action **Search User Conversations** Returns the conversations of the given user ID that matches the search terms. - Action **Send Message** Adds a new message to an existing conversation. - Action **Telegram Send Message** Sends a message to Telegram. - Action **Update Conversation Agent** Assigns or update the agent assigned to a conversation. - Action **Update Conversation Department** Updates the department of a conversation. - Action **Update Conversation Status** Updates the status code of a conversation. - Action **Update Message** Updates an existing message. - Action **Update User** Updates the details of an existing user. - Action **WhatsApp Send Message** Sends a message to a WhatsApp number. ## Each app on its own - [ **Request Tracker (RT)** Request Tracker (RT) is an open-source, enterprise-grade ticketing system.](https://apiant.ai/connections/request-tracker-rt) - [ **Support Board** Support Board is a communication and chat platform powered by artificial intelligence-driven chatbots.](https://apiant.ai/connections/support-board) Reviews ## What our customers say ## More from Request Tracker (RT) - [ **Request Tracker (RT) to Salesforce** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/request-tracker-rt-to-salesforce) - [ **Request Tracker (RT) to Slack** Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...](https://apiant.ai/connect/request-tracker-rt-to-slack) - [ **Request Tracker (RT) to Stripe** Stripe is a payment processing platform for online businesses.](https://apiant.ai/connect/request-tracker-rt-to-stripe) - [ **Request Tracker (RT) to Shopify** Shopify is a commerce platform for online stores and retail point-of-sale.](https://apiant.ai/connect/request-tracker-rt-to-shopify) - [ **Request Tracker (RT) to Trello** Trello is a visual collaboration tool that organizes projects into boards, lists, and cards.](https://apiant.ai/connect/request-tracker-rt-to-trello) - [ **Request Tracker (RT) to Zoom** Zoom unifies cloud video conferencing, simple online meetings, group messaging, and a software-based...](https://apiant.ai/connect/request-tracker-rt-to-zoom) ## More into Support Board - [ **HubSpot to Support Board** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/hubspot-to-support-board) - [ **Salesforce to Support Board** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/salesforce-to-support-board) - [ **Slack to Support Board** Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...](https://apiant.ai/connect/slack-to-support-board) - [ **Google Sheets to Support Board** Google Sheets](https://apiant.ai/connect/google-sheets-to-support-board) - [ **Gmail to Support Board** Gmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...](https://apiant.ai/connect/gmail-to-support-board) - [ **Google Calendar to Support Board** Google Calendar is a time management tool providing scheduling features, event reminders, and integration...](https://apiant.ai/connect/google-calendar-to-support-board) Questions ## Request Tracker (RT) and Support Board, 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 Support Board when something happens in Request Tracker (RT)? Any of Support Board's 36 actions, including Send Message, Update Conversation Agent, Update Conversation Department and Update Conversation Status. Your agent maps the data both ways and tests every scenario before it ships. ### ### Can it also run from Support Board to Request Tracker (RT)? Support Board has no triggers in the catalog today, so automations start in Request Tracker (RT). If you need the other direction, ask: your agent reads Support Board's API documentation and adds it. ### ### Do I have to build a connector for Request Tracker (RT) or Support Board? 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 Support Board 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.