Integration
Connect Request Tracker (RT) to Attentive
When Ticket Created fires in Request Tracker (RT), your agent runs Custom Events in Attentive. 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 Attentive 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 Attentive
When Ticket Created in Request Tracker (RT)
then Custom Events in Attentive
When Ticket Status Changed in Request Tracker (RT)
then Subscribe User in Attentive
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 Attentive
Triggers and actions 3 triggers · 32 actions
Trigger
Ticket CorrespondenceTriggers when a ticket is replied to (that is, corresponded with).
Trigger
Ticket CreatedTriggers when a new Request Tracker ticket is created.
Trigger
Ticket Status ChangedTriggers when a Request Tracker ticket changes status. Can watch for any status change or only for changes to a specific status.
Action
Add assetCreate an asset.
Action
Add userCreate a user.
Action
Comment on a TicketAdd an internal comment to a ticket and send to any internal watchers.
Action
Create TicketCreate a new ticket in Request Tracker.
Action
Find AttachmentLocate an attachment by ID.
Action
Find TicketLocate a ticket by ID.
Action
Find TicketsIssue a query to find matching tickets.
Action
Find TransactionFind a transaction by ID
Action
Get assetRetrieves one asset by ID: name, description, status, catalog, owner, held by, contact, custom fields.
Action
Get queueGet a queue by id or name.
Action
Get userGet a user by id or name.
Action
List queuesList all queues visible to user.
Action
List ticket historyList transactions of a ticket.
Action
Reply to a TicketReply to the requestor and any internal or external watchers of a ticket.
Action
Update ticketGeneral ticket update (Owner, Priority, Queue, custom fields).
Action
Update Ticket Due DateUpdate the due date of a ticket.
Action
Update Ticket StatusUpdate the status of a ticket.
Action
Update Ticket SubjectUpdate the subject of a ticket.
Action
Update userUpdate a user.
Action
Add to CartRecords that a shopper added a product to their cart in Attentive, so cart-abandonment journeys can fire.
Action
Custom AttributesSets custom attributes (such as age, birthday or favorite team) on an Attentive user identified by phone, email, or external identifier.
Action
Custom EventsSends a custom event (such as "Order Shipped") for a user to Attentive, which can trigger Journeys.
Action
Delete RequestCreates a privacy (CCPA) deletion request that deletes a subscriber within thirty days, identified by email, phone or client user id.
Action
Get Custom Attributes for a UserReturns all custom attributes (name and value) stored on an Attentive user, looked up by phone number or email.
Action
Get Subscription Eligibility for a UserReturns the subscription types and channels (SMS or email) a subscriber is eligible to receive messages on, looked up by phone number or email.
Action
IdentityAssociates a client user identifier or custom identifiers with an Attentive subscriber identified by phone, email, Shopify ID or Klaviyo ID.
Action
Lookup Product Catalog IngestionReturns the status, validation errors and product counts of a product catalog upload.
Action
Product ViewRecords that a shopper viewed one or more products in Attentive, so product-view journeys can fire.
Action
PurchaseRecords a purchase (order) event for a shopper in Attentive so it can trigger purchase-based journeys.
Action
Subscribe UserOpts a person in to Attentive text or email subscriptions by phone or email, using a sign-up unit or a locale and subscription type.
Action
Unsubscribe Subscriptions for a UserUnsubscribes a user (by phone or email) from specific Attentive subscription types and channels, or from all subscriptions when none are given.
Action
View Recent Catalog UploadsReturns your recent product catalog uploads with their ingestion status, product counts and validation errors, newest first.
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 Attentive
HubSpot to AttentiveHubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to AttentiveSalesforce is a leading enterprise customer relationship management (CRM) platform.
Slack to AttentiveSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Google Sheets to AttentiveGoogle Sheets
Gmail to AttentiveGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to AttentiveGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
Request Tracker (RT) and Attentive, 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 Attentive when something happens in Request Tracker (RT)?
Any of Attentive's 13 actions, including Add to Cart, Custom Attributes, Custom Events and Get Custom Attributes for a User. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Attentive to Request Tracker (RT)?
Attentive has no triggers in the catalog today, so automations start in Request Tracker (RT). If you need the other direction, ask: your agent reads Attentive's API documentation and adds it.
Do I have to build a connector for Request Tracker (RT) or Attentive?
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 Attentive 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.