Integration
Connect CalendarLink and Ubidots
When New Upcoming Event fires in CalendarLink, your agent runs Add event in Ubidots, or Device Is Updated in Ubidots to List Contacts in CalendarLink. 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 CalendarLink and Ubidots 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 CalendarLink and Ubidots can do together
From CalendarLink to Ubidots
When New Upcoming Event in CalendarLink
then Add event in Ubidots
When New Upcoming Event in CalendarLink
then Add device in Ubidots
From Ubidots to CalendarLink
When Device Is Updated in Ubidots
then List Contacts in CalendarLink
When Variable Updated in Ubidots
then Create New Event in CalendarLink
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 Ubidots
Triggers and actions 4 triggers · 23 actions
Trigger
New Upcoming EventTriggered when a new upcoming event is added to your CalendarLink organisation.
Action
Create New EventCreates 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.
Action
Find EventSearches 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.
Action
List ContactsReturns a page of the contacts in your CalendarLink organisation, 15 per page, along with how many pages there are.
Action
List Event CollectionsReturns every event collection in your CalendarLink organisation, with each collection's ID, name, description, public link and event count.
Action
List Event RegistrationsReturns a page of the people who signed up for one CalendarLink event, 15 per page. The event must have RSVP turned on.
Action
List Past EventsReturns a page of your CalendarLink events that have already finished, 15 per page, newest first.
Action
List Upcoming EventsReturns a page of your CalendarLink events that have not happened yet, 15 per page.
Action
Update Event CollectionChanges 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.
Trigger
Device Is UpdatedTriggers when a device is created or any of its fields (name, description, tags, properties, organization, status) changes.
Trigger
Event Is TriggeredTriggers when a chosen Ubidots event fires, returning the new log entry for that event.
Trigger
Variable UpdatedTriggers when a variable is created or its settings (name, description, unit, tags, properties) change.
Action
Add deviceCreates a new device in your Ubidots account.
Action
Add eventCreates a new Ubidots event (alert rule) with its triggers, actions and active schedule.
Action
Add variableCreates a new variable on a Ubidots device.
Action
Create DotSends a single Dot (a value with optional timestamp and context) to a variable on a device. The device and variable are created automatically if they do not exist.
Action
Create Multiple Dots on Same DeviceSends values to one or more variables of a Ubidots device in a single call, creating the device and variables if they do not exist.
Action
Delete devicePermanently deletes a device and its variables from your Ubidots account.
Action
Delete variablePermanently deletes a variable and its data from Ubidots.
Action
Get data seriesReturns time-series values for one or more variables over a time range, each with its device and variable details.
Action
Get deviceReturns a single Ubidots device, looked up by its ID or label.
Action
Get device last valuesReturns the most recent value of every variable on a Ubidots device.
Action
Get variableReturns a single Ubidots variable, including its device, unit, tags, properties and last value.
Action
List devicesReturns the devices in your Ubidots account, with their labels, names, tags and activity details.
Action
List variablesReturns the variables in the Ubidots account, each with its device, label, name, type, unit and last value.
Action
Update deviceUpdates the specified fields of an existing Ubidots device, such as its name, label, description, tags, properties or organization, and returns the updated device.
Action
Update variableUpdates the specified fields of an existing Ubidots variable, such as its name, label, unit, tags or description. Returns the updated variable.
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 Ubidots
HubSpot to UbidotsHubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to UbidotsSalesforce is a leading enterprise customer relationship management (CRM) platform.
Slack to UbidotsSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Google Sheets to UbidotsGoogle Sheets
Gmail to UbidotsGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to UbidotsGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
CalendarLink and Ubidots, 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 Ubidots when something happens in CalendarLink?
Any of Ubidots's 15 actions, including Create Dot, Create Multiple Dots on Same Device, Update device and Update variable. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Ubidots to CalendarLink?
Yes. When something happens in Ubidots, your agent can act in CalendarLink too. This page covers both directions: Ubidots's triggers and CalendarLink's actions are listed here as well.
Do I have to build a connector for CalendarLink or Ubidots?
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 CalendarLink and Ubidots 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.