Integration
Connect Ubidots to Instatus
When Device Is Updated fires in Ubidots, your agent runs Add component in Instatus. 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 Ubidots and Instatus 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 Ubidots can start in Instatus
When Device Is Updated in Ubidots
then Add component in Instatus
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 Ubidots and Instatus
Triggers and actions 3 triggers · 29 actions
- Device Is Updated
Triggers when a device is created or any of its fields (name, description, tags, properties, organization, status) changes.
- Event Is Triggered
Triggers when a chosen Ubidots event fires, returning the new log entry for that event.
- Variable Updated
Triggers when a variable is created or its settings (name, description, unit, tags, properties) change.
- Add device
Creates a new device in your Ubidots account.
- Add event
Creates a new Ubidots event (alert rule) with its triggers, actions and active schedule.
- Add variable
Creates a new variable on a Ubidots device.
- Create Dot
Sends 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.
- Create Multiple Dots on Same Device
Sends values to one or more variables of a Ubidots device in a single call, creating the device and variables if they do not exist.
- Delete device
Permanently deletes a device and its variables from your Ubidots account.
- Delete variable
Permanently deletes a variable and its data from Ubidots.
- Get data series
Returns time-series values for one or more variables over a time range, each with its device and variable details.
- Get device
Returns a single Ubidots device, looked up by its ID or label.
- Get device last values
Returns the most recent value of every variable on a Ubidots device.
- Get variable
Returns a single Ubidots variable, including its device, unit, tags, properties and last value.
- List devices
Returns the devices in your Ubidots account, with their labels, names, tags and activity details.
- List variables
Returns the variables in the Ubidots account, each with its device, label, name, type, unit and last value.
- Update device
Updates the specified fields of an existing Ubidots device, such as its name, label, description, tags, properties or organization, and returns the updated device.
- Update variable
Updates the specified fields of an existing Ubidots variable, such as its name, label, unit, tags or description. Returns the updated variable.
- Add component
Creates a new component on an Instatus status page and returns the created component.
- Add incident update
Posts a new update to an existing incident on an Instatus status page, optionally changing the incident status and affected component statuses.
- Add maintenance
Schedules a new maintenance on an Instatus status page, with its affected components, timing and subscriber notification options.
- Add subscriber
Adds a subscriber (by email or phone) to a status page, subscribed to all components or to specific ones.
- Create Incident
Creates a new incident on an Instatus status page, optionally marking affected components and notifying subscribers.
- Delete incident
Deletes an incident from an Instatus status page.
- Get component
Returns one component on an Instatus status page, including its name, current status, description and group.
- Get incident
Returns a single incident on a status page, including its updates, affected components and the teammate who created it.
- Get maintenance
Returns one scheduled maintenance on a status page, including its updates and affected components.
- List components
Returns the components on an Instatus status page, with each component's name, status and group.
- List maintenances
Returns the scheduled, in-progress and completed maintenances on an Instatus status page.
- List status pages
Returns the status pages in your Instatus account, including each page's id, name, subdomain and current status.
- List subscribers
Returns the subscribers of an Instatus status page, optionally filtered by email/phone search or subscription status.
- Update component
Updates a component on an Instatus status page, such as its name, description, status, order or group.
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 Ubidots
Ubidots to ZoomZoom unifies cloud video conferencing, simple online meetings, group messaging, and a software-based...
Ubidots to WebflowWebflow is a professional website builder and CMS for designing, building, and launching responsive...
Ubidots to WixThe Wix website builder gives businesses of any size the tools to create, manage and grow a fully integrated...
Ubidots to LinkedInLinkedIn is a professional networking platform enabling job seekers, companies, and thought leaders to...
Ubidots to FacebookFacebook is a social media and advertising platform used by individuals and businesses to connect, share...
Ubidots to AnthropicAnthropic builds Claude, a family of large language models.
More into Instatus
HubSpot to InstatusHubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to InstatusSalesforce is a leading enterprise customer relationship management (CRM) platform.
Slack to InstatusSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Google Sheets to InstatusGoogle Sheets
Gmail to InstatusGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to InstatusGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
Ubidots and Instatus, answered
What can start an automation from Ubidots?
Any of Ubidots's 3 triggers in the catalog, including Device Is Updated, Variable Updated and Event Is Triggered. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Instatus when something happens in Ubidots?
Any of Instatus's 14 actions, including Create Incident, Update component, Add component and Add incident update. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Instatus to Ubidots?
Instatus has no triggers in the catalog today, so automations start in Ubidots. If you need the other direction, ask: your agent reads Instatus's API documentation and adds it.
Do I have to build a connector for Ubidots or Instatus?
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 Ubidots and Instatus 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.