Integration
Connect Request Tracker (RT) and Stora
When Ticket Created fires in Request Tracker (RT), your agent runs Create Contact in Stora, or Completed Task in Stora 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 Stora 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 Stora can do together
From Request Tracker (RT) to Stora
When Ticket Created in Request Tracker (RT)
then Create Contact in Stora
From Stora 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 Stora
Triggers and actions 13 triggers · 36 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.
- Completed Task
Triggers when a task is completed.
- Finalized Order
Triggers when an order is finalized (ready for payment).
- New Contact
Fires when a contact is created in Stora.
- New Note
Triggers when a new note is created.
- New Order
Triggers when a new order is created.
- New Task
Triggers when a new task is created.
- Reopened Task
Triggers when a completed task is reopened.
- Updated Contact
Triggers when a contact is updated.
- Updated Note
Triggers when a note is updated.
- Updated Task
Triggers when a task is updated.
- Complete Task
Marks a Stora task as complete.
- Create Contact
Creates a new contact.
- Create Note
Create a note attached to a contact, unit, subscription or task in Stora.
- Create Task
Creates a new task.
- Create Timeline Event
Creates a new timeline event.
- Delete Contact
deletes a contact by id (scope public.contact:write). Only lead contacts without invoices can be deleted; others return 409.
- Find Contact
Returns the contacts that match the given email, name/phone search or filters. The first match is also returned on its own.
- Find Order
Finds orders matching the given contact, site, status, source, billing period or date criteria and returns the matches plus the first match.
- Find Site
Find self-storage sites by name, optionally narrowed by creation or update date.
- Find Staff Member
Finds Stora staff members by name or email.
- Find Task
Find tasks in Stora by related record, assignee, status or date range.
- Find Unit
Finds a unit by ID, reference ID, unit type, or site.
- Find Unit Type
Finds unit types whose name contains the text you give, optionally narrowed to a site and a created/updated date range.
- Reopen Task
Mark a completed Stora task as open again.
- Update Contact
Update an existing Stora contact. Only the fields you fill in are changed.
- Update Note
Update an existing note in Stora: change its text, move it to a different contact, unit, subscription or task, or replace its metadata. Fields left blank are not changed.
- Update Task
Update an existing Stora task's title, description, due date, site, assignee, related record or metadata. Fields left blank are not 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 Stora
HubSpot to StoraHubSpot is your all-in-one stop for all of your marketing software needs.
Google Sheets to StoraGoogle Sheets
Gmail to StoraGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to StoraGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
Request Tracker (RT) and Stora, 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 Stora when something happens in Request Tracker (RT)?
Any of Stora's 17 actions, including Create Contact, Create Note, Create Task and Create Timeline Event. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Stora to Request Tracker (RT)?
Yes. When something happens in Stora, your agent can act in Request Tracker (RT) too. This page covers both directions: Stora'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 Stora?
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.