Integration
Connect Request Tracker (RT) and Wodify Core
When Ticket Created fires in Request Tracker (RT), your agent runs Add Tag to Lead in Wodify Core, or New/Updated Client in Wodify Core 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 Wodify Core 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) and Wodify Core can do together
From Request Tracker (RT) to Wodify Core
When Ticket Created in Request Tracker (RT)
then Add Tag to Lead in Wodify Core
From Wodify Core 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 Wodify Core
Triggers and actions 5 triggers · 37 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.
- 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.
- New/Updated Client
Triggers when a client is added or an existing client is updated in Wodify.
- Tag Changed on Client
Triggers when a client's tags change (a tag is added to or removed from a client).
- Add class reservation
Reserves a spot in a class for a client, optionally as a recurring reservation.
- Add membership
Creates a new membership for a client from a membership template. Values you leave blank are filled in from the template.
- Add Tag to Client
Adds one or more tags to a Wodify client and returns the client's current tags.
- Add Tag to Lead
Adds one or more tags to a Wodify lead and returns the lead's current tags.
- Add/Update Lead
Creates a new lead in Wodify, or updates an existing lead when a Lead ID is supplied.
- Convert lead to client
Converts a Lead into a Client. Any details you leave blank keep the Lead's existing values.
- Delete client
Deletes an inactive Wodify client by its ID.
- Delete lead
Deletes a lead record from Wodify by its ID.
- Find leads by criteria
Searches your Wodify leads with a search query and returns the matching leads.
- Get Client
Returns a Wodify client record by its id, including contact details, status, tags, memberships flags and custom field answers.
- Get Lead
Returns a single Wodify lead record by its lead ID.
- Get membership
Returns a single membership record by its membership ID.
- List clients
Returns the clients in your Wodify account.
- List employees
Returns the employees (staff and coaches) in your Wodify account.
- List invoices
Returns the invoices in your Wodify gym, with amounts, status, due and paid dates, and the client or lead each one belongs to.
- List leads
Returns the leads in your Wodify account, up to 100 at a time.
- List memberships
Returns the memberships in your Wodify account, up to 100 at a time.
- Remove Tag From Client
Removes one or more tags from a Wodify client and returns the client's remaining tags.
- Remove Tag From Lead
Removes the given tags from a Wodify lead and returns the lead's remaining tags.
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 Wodify Core
HubSpot to Wodify CoreHubSpot is your all-in-one stop for all of your marketing software needs.
Google Sheets to Wodify CoreGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Gmail to Wodify CoreGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to Wodify CoreGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
Request Tracker (RT) and Wodify Core, 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 Wodify Core when something happens in Request Tracker (RT)?
Any of Wodify Core's 19 actions, including Add class reservation, Add membership, Add Tag to Client and Add Tag to Lead. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Wodify Core to Request Tracker (RT)?
Yes. When something happens in Wodify Core, your agent can act in Request Tracker (RT) too. This page covers both directions: Wodify Core'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 Wodify Core?
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 Wodify Core 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.