Integration
Connect Ubidots to SigningHub
When Device Is Updated fires in Ubidots, your agent runs Add Document in SigningHub. 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 SigningHub 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 SigningHub
When Device Is Updated in Ubidots
then Add Document in SigningHub
When Variable Updated in Ubidots
then Add User in SigningHub
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 SigningHub
Triggers and actions 3 triggers · 26 actions
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.
Action
Add Digital SignatureAdds a digital signature field to a document in a SigningHub package and assigns it to a recipient in the workflow.
Action
Add DocumentUploads a document file into an existing SigningHub document package.
Action
Add Electronic SignatureAdds an electronic signature field to a document in a package, assigned to a recipient in the workflow.
Action
Add Recipient to WorkflowAdds a signer or other recipient to a document package's workflow.
Action
Add UserRegisters a new user in your SigningHub enterprise account, optionally with a password, role and profile details.
Action
Create Integration URLGenerates an encrypted SigningHub link that opens a shared document package so a user can view and sign it from your application.
Action
Create PackageCreates a new document package in SigningHub to hold documents and recipients for a signing workflow.
Action
Download PackageDownloads a document package as a Base64-encoded file: a PDF for a single-document package, or a zip of all its documents.
Action
Get Document FieldsReturns the fields on a document in a SigningHub package: signature, initials, in-person, text, checkbox, radio, dropdown, listbox, QR code, attachment and comment fields.
Action
Get PackageReturns the details of a SigningHub document package: its name, owner, status and the documents it contains.
Action
Share Document for SigningShares a prepared document package with its signers and starts the signing workflow.
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 SigningHub
HubSpot to SigningHubHubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to SigningHubSalesforce is a leading enterprise customer relationship management (CRM) platform.
Slack to SigningHubSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Google Sheets to SigningHubGoogle Sheets
Gmail to SigningHubGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to SigningHubGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
Ubidots and SigningHub, 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 SigningHub when something happens in Ubidots?
Any of SigningHub's 11 actions, including Create Integration URL, Create Package, Add Digital Signature and Add Document. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from SigningHub to Ubidots?
SigningHub has no triggers in the catalog today, so automations start in Ubidots. If you need the other direction, ask: your agent reads SigningHub's API documentation and adds it.
Do I have to build a connector for Ubidots or SigningHub?
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 SigningHub 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.