Integration
Connect CalendarLink to Knock
When something happens in CalendarLink, your agent does the next thing in Knock. Describe it 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 CalendarLink and Knock to do together?
Ask the assistant
Connect your AI client
Give your AI client this address.
https://mcp.apiant.aiAny 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 CalendarLink can start in Knock
When New Upcoming Event in CalendarLink
then Add object 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 CalendarLink and Knock
Triggers and actions 1 trigger · 16 actions
- New Upcoming Event
Triggered when a new upcoming event is added to your CalendarLink organisation.
- Create New Event
Creates an event in a CalendarLink collection and returns its add-to-calendar link. Times use the format 2026-09-01 09:00:00. Optionally turns on RSVP with a deadline, attendee limit and notification settings.
- Find Event
Searches your CalendarLink events for one whose title contains the text you give, and returns the first match with its add-to-calendar link, times and RSVP counts.
- List Contacts
Returns a page of the contacts in your CalendarLink organisation, 15 per page, along with how many pages there are.
- List Event Collections
Returns every event collection in your CalendarLink organisation, with each collection's ID, name, description, public link and event count.
- List Event Registrations
Returns a page of the people who signed up for one CalendarLink event, 15 per page. The event must have RSVP turned on.
- List Past Events
Returns a page of your CalendarLink events that have already finished, 15 per page, newest first.
- List Upcoming Events
Returns a page of your CalendarLink events that have not happened yet, 15 per page.
- Update Event Collection
Changes the settings of one CalendarLink event collection — its name, description, appearance, what visitors can add and whether sign-up is required. Only the fields you fill in are changed; the rest keep their current values.
- Add object
Creates 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.
- Add user
Create a user in Knock, or update an existing one with the same user id (only the supplied properties change).
- Delete object
Permanently removes an object from the specified collection. This cannot be undone.
- Delete user
Permanently delete a Knock user and all associated data.
- Get object
Retrieves a specific object by its ID from a collection, including all of its custom properties.
- Get user
Retrieve a single Knock user by id.
- List objects
Lists the objects in a Knock collection, optionally with their preferences.
- List users
List 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 CalendarLink
CalendarLink to StripeStripe is a payment processing platform for online businesses.
CalendarLink to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
CalendarLink to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
CalendarLink to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
CalendarLink to Google SheetsGoogle Sheets
CalendarLink to GmailGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
More into Knock
EquipDash to KnockEquipDash is a AI-powered equipment rental and tour booking software built for outdoor recreation operators.
Questions
CalendarLink and Knock, answered
What can start an automation from CalendarLink?
Any of CalendarLink's 1 trigger in the catalog, including New Upcoming Event. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Knock when something happens in CalendarLink?
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 CalendarLink?
Knock has no triggers in the catalog today, so automations start in CalendarLink. 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 CalendarLink 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.
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.