Integration
Connect Request Tracker (RT) to Iterable
When Ticket Created fires in Request Tracker (RT), your agent runs Add email template in Iterable. 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 Iterable 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 Request Tracker (RT) can start in Iterable
When Ticket Created in Request Tracker (RT)
then Add email template in Iterable
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 Iterable
Triggers and actions 3 triggers · 39 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.
- Add email template
Creates an email template, or updates every email template that already has the same client template ID.
- Add list
Creates a new static list in Iterable and returns its id.
- Add user to list
Adds a user, identified by email or user ID, to a static Iterable list, optionally updating their profile data.
- Create a User
Creates a user profile in Iterable (or updates it if one already exists), identified by email or user ID, with any profile data you supply.
- Delete catalog item
Deletes an item from an Iterable catalog. Deletion is asynchronous, so the item may take a moment to disappear.
- Delete list
Deletes a list from your Iterable project.
- Delete user
Deletes an Iterable user by email address. Deletion is processed asynchronously.
- Get catalog item
Returns one item from an Iterable catalog, including all of its field values.
- Get email template
Returns an email template by its ID, including its HTML and plain-text content, subject, sender details and metadata.
- Get user
Returns an Iterable user profile, including all its data fields, looked up by email address.
- List lists
Returns all lists in the Iterable project, including their id, name and list type.
- Remove user from list
Removes a user, identified by email or user ID, from an Iterable static list.
- Send email
Sends an email from an Iterable triggered campaign to a single user, identified by email address or user ID.
- Send push notification
Sends a push notification from an existing push campaign to one Iterable user, now or at a scheduled time.
- Send SMS
Sends an SMS from an Iterable SMS campaign to one user, identified by email or user ID, optionally scheduled for later.
- Track a Purchase
Records a purchase for an Iterable user, with its line items and order total, and clears the user's shopping cart. Creates the user if they do not exist yet.
- Track Event
Records a custom event against an Iterable user profile, identified by email or user ID, with optional event data.
- Trigger campaign
Sends an existing triggered campaign to the members of one or more lists.
- Update a User's Shopping Cart Items
Replaces the shopping cart items stored on an Iterable user profile, creating the user if they do not exist yet.
- Update user subscriptions
Updates a user's list, channel and message type subscriptions in Iterable. Any subscription list you provide replaces the user's existing one.
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 Iterable
HubSpot to IterableHubSpot is your all-in-one stop for all of your marketing software needs.
Google Sheets to IterableGoogle Sheets
Gmail to IterableGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to IterableGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
Request Tracker (RT) and Iterable, 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 Iterable when something happens in Request Tracker (RT)?
Any of Iterable's 20 actions, including Create a User, Send email, Send push notification and Send SMS. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Iterable to Request Tracker (RT)?
Iterable has no triggers in the catalog today, so automations start in Request Tracker (RT). If you need the other direction, ask: your agent reads Iterable's API documentation and adds it.
Do I have to build a connector for Request Tracker (RT) or Iterable?
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 Iterable 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.