Integration
Connect MySQL and TimeRex
When New or Updated Row fires in MySQL, your agent runs Get Event in TimeRex, or Event Created in TimeRex to Add Row in MySQL. 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 MySQL and TimeRex 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 MySQL and TimeRex can do together
From MySQL to TimeRex
When New or Updated Row in MySQL
then Get Event in TimeRex
When New Row in MySQL
then List Calendar Events in TimeRex
From TimeRex to MySQL
When Event Created in TimeRex
then Add Row in MySQL
When Event Created in TimeRex
then Update Row in MySQL
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 MySQL and TimeRex
Triggers and actions 5 triggers · 16 actions
Trigger
New or Updated RowTriggers when a new row is added or modified.
Trigger
New or Updated Row (Custom Query)Fires for each new or changed row returned by a SELECT statement you write against the connected MySQL database.
Trigger
New RowTriggers when you add a new row.
Trigger
New TableFires when a new table appears in the connected MySQL database.
Action
Add RowAdds a new row.
Action
Delete RowDelete the rows in a table whose chosen column equals a value.
Action
Find RowFinds a row in a table via a lookup column.
Action
Find Rows via Custom QueryRun an author-written SELECT against the connected MySQL database and return every row it produced. Mirrors PostgreSQL 715ae2ac, SQL Server 8e0bbb5d and Oracle 2c308e4d; MySQL placeholder style is ?.
Action
Find Row via Custom QueryRuns a SELECT statement you write against the connected MySQL database and returns the first row it matches.
Action
Update RowUpdates an existing row.
Trigger
Event CreatedTriggers when a new event is booked on a TimeRex calendar.
Action
Cancel EventCancels a booked TimeRex event, with an optional reason.
Action
Create One-Time URLCreates a single-use booking URL for a TimeRex calendar.
Action
Get CalendarReturns one TimeRex booking calendar by its ID.
Action
Get EventReturns one booked TimeRex event by its ID, with guest and meeting details.
Action
Get One-Time URLReturns a TimeRex one-time booking URL and the event booked through it, if any.
Action
Get Primary TeamReturns the TimeRex team the API key belongs to.
Action
Get TeamReturns one TimeRex team by its ID.
Action
List Calendar EventsReturns the events booked on a TimeRex calendar, optionally within a time range.
Action
List CalendarsReturns the booking calendars of a TimeRex team.
Action
List TeamsReturns the TimeRex teams available to the API key.
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 MySQL
MySQL to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
MySQL to MailchimpMailchimp marketing automation and email platform.
MySQL to QuickBooks OnlineQuickBooks Online accounting — manage customers, invoices, bills, payments, vendors, expenses, and more via...
MySQL to ActiveCampaignActiveCampaign is a marketing automation, email marketing, and CRM platform.
MySQL to TrelloTrello is a visual collaboration tool that organizes projects into boards, lists, and cards.
MySQL to SendGridSendGrid by Twilio — email delivery and marketing platform.
More into TimeRex
HubSpot to TimeRexHubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to TimeRexSalesforce is a leading enterprise customer relationship management (CRM) platform.
Slack to TimeRexSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Google Sheets to TimeRexGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Gmail to TimeRexGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to TimeRexGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
MySQL and TimeRex, answered
What can start an automation from MySQL?
Any of MySQL's 4 triggers in the catalog, including New or Updated Row, New or Updated Row (Custom Query), New Row and New Table. Describe the moment in plain language and your agent picks the right one.
What can your agent do in TimeRex when something happens in MySQL?
Any of TimeRex's 10 actions, including Create One-Time URL, Get Calendar, Get Event and Get One-Time URL. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from TimeRex to MySQL?
Yes. When something happens in TimeRex, your agent can act in MySQL too. This page covers both directions: TimeRex's triggers and MySQL's actions are listed here as well.
Do I have to build a connector for MySQL or TimeRex?
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 MySQL and TimeRex 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.