Integration
Connect TimeRex to Knock
When Event Created fires in TimeRex, your agent runs Add user in Knock. 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 TimeRex and Knock 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 TimeRex can start in Knock
When Event Created in TimeRex
then Add user in Knock
When Event Created in TimeRex
then Get user in Knock
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 TimeRex and Knock
Triggers and actions 1 trigger · 18 actions
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.
Action
Add objectCreates an object in a Knock collection, or updates it if an object with that ID already exists, setting its name, locale, time zone, custom properties, channel data and preferences.
Action
Add userCreate a user in Knock, or update an existing one with the same user id (only the supplied properties change).
Action
Delete objectPermanently removes an object from the specified collection. This cannot be undone.
Action
Delete userPermanently delete a Knock user and all associated data.
Action
Get objectRetrieves a specific object by its ID from a collection, including all of its custom properties.
Action
Get userRetrieve a single Knock user by id.
Action
List objectsLists the objects in a Knock collection, optionally with their preferences.
Action
List usersList all users in the Knock account, paginated.
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 TimeRex
TimeRex to TrelloTrello is a visual collaboration tool that organizes projects into boards, lists, and cards.
TimeRex to ZoomZoom unifies cloud video conferencing, simple online meetings, group messaging, and a software-based...
TimeRex to TwilioCloud communications platform for sending SMS/MMS messages, making and managing voice calls, and looking up...
TimeRex to TypeformBuild and publish online forms, surveys, and quizzes with Typeform.
TimeRex to WebflowWebflow is a professional website builder and CMS for designing, building, and launching responsive...
TimeRex to WixThe Wix website builder gives businesses of any size the tools to create, manage and grow a fully integrated...
More into Knock
EquipDash to KnockEquipDash is a AI-powered equipment rental and tour booking software built for outdoor recreation operators.
HubSpot to KnockHubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to KnockSalesforce is a leading enterprise customer relationship management (CRM) platform.
Slack to KnockSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Google Sheets to KnockGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Gmail to KnockGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Questions
TimeRex and Knock, answered
What can start an automation from TimeRex?
Any of TimeRex's 1 trigger in the catalog, including Event Created . Describe the moment in plain language and your agent picks the right one.
What can your agent do in Knock when something happens in TimeRex?
Any of Knock's 8 actions, including Add object, Add user, Get object and Get user. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Knock to TimeRex?
Knock has no triggers in the catalog today, so automations start in TimeRex. If you need the other direction, ask: your agent reads Knock's API documentation and adds it.
Do I have to build a connector for TimeRex or Knock?
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 TimeRex and Knock 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.