Can HumDay connect to ClearBlade?

Yes. HumDay reads ClearBlade's own published API description and derives the operations from it, so there is no hand-built connector to wait for. 220 operations are documented.

Do I need to write code to automate ClearBlade?

No. You describe the outcome you want in plain words. HumDay agrees a contract with you, writes the program, and shows you a test run before anything touches your ClearBlade account.

What can HumDay do in ClearBlade?

126 of the 220 documented operations change something in ClearBlade, and 94 read from it. HumDay only ever uses the specific operations your approved contract needs.

Is my ClearBlade account safe?

Your credentials are stored encrypted and are never shown in chat, code, or logs. Every run is limited to the operations you explicitly approved, and anything that writes to ClearBlade is held behind that approval.

Automate ClearBlade

HumDay reads ClearBlade’s own published API description and derives 220 operations from it. Describe the outcome you want in plain words — you get a program that is written, proven on real data, and run for you.

Automate ClearBlade

What ClearBlade is

A friendly little API to help you interact with the ClearBlade platform.

API host: platform.clearblade.com

What HumDay can do in ClearBlade

126 documented operations change something in ClearBlade. The 64 most useful are listed here.

POSTUSERS - Register new user/api/v/1/user/reg
POSTUSERS - Authenticate anonymous user/api/v/1/user/anon
POSTUSERS - Authenticate user/api/v/1/user/auth
PUTUSERS - Update user info/api/v/1/user/info
PUTUSERS - Change user password/api/v/1/user/pass
POSTUSERS - Log out user/api/v/1/user/logout
PUTUSER - Users change roles and passwords for other users/api/v/4/user/manage
POSTUSERS - Check user auth/api/v/1/user/checkauth
POSTFILES - Creates a new file in a bucket/api/v/4/bucket_sets/{systemKey}/{deploymentName}/file/create
POSTDATA(id) - Create items/api/v/1/data/{collectionID}
POSTADAPTERS - Add or replace file content & configuration/api/v/4/{SystemKey}/adapters/{AdapterName}/files
POSTDATA - Create collection/api/v/3/collectionmanagement
DELETEAllows an user with adequate permissions to delete another user/api/v/1/user/info
POSTFILES - Copies a file to a new location within buckets/api/v/4/bucket_sets/{systemKey}/{deploymentName}/file/copy
POSTFILES - Moves a file to a new location within buckets./api/v/4/bucket_sets/{systemKey}/{deploymentName}/file/move
POSTDATA(name) - Create items/api/v/1/collection/{systemKey}/{collectionName}
DELETEDATA(id) - Delete items/api/v/1/data/{collectionID}
PUTDATA(id) - Update items/api/v/1/data/{collectionID}
DELETEMESSAGING - Delete history/api/v/1/message/{systemKey}
DELETEDEVICES - Delete devices using a query/api/v/2/devices/{SystemKey}
PUTDEVICES - Update devices using a query/api/v/2/devices/{SystemKey}
POSTADAPTERS - Add an adapter/api/v/4/{SystemKey}/adapters
POSTDEPLOYMENTS - Creates a deployment/api/v/3/{systemKey}/deployments
POSTDATABASES - Create a external database connection/api/v/4/external-db/{systemKey}
DELETEDEVELOPER - Delete failed service run/codeadmin/failed/{systemKey}
POSTDEVELOPER - Retry failed service/codeadmin/failed/{systemKey}
DELETEDATA - Delete collection/api/v/3/collectionmanagement
PUTDATA - Update collection/api/v/3/collectionmanagement
POSTDEVELOPER - Add code service/codeadmin/v/2/{systemKey}/{serviceName}
POSTMESSAGING - Publish message/api/v/1/message/{systemKey}/publish
POSTEDGE - Create edge/api/v/3/edges/{systemKey}/{name}
POSTDEVICES - Adds a device/api/v/2/devices/{systemKey}/{name}
POSTFILES - Deletes a file from the bucket./api/v/4/bucket_sets/{systemKey}/{deploymentName}/file/delete
PUTADAPTERS - Map Adapter command to execute a file/api/v/4/{SystemKey}/adapters/{AdapterName}
POSTDEVELOPER - Create library/codeadmin/v/2/library/{systemKey}/{libName}
DELETEDATA(name) - Delete items/api/v/1/collection/{systemKey}/{collectionName}
PUTDATA(name) - Update items/api/v/1/collection/{systemKey}/{collectionName}
PUTADAPTERS - Update Existing File's content/api/v/4/{SystemKey}/adapters/{AdapterName}/files/{fileName}
POSTHANDLERS - Create timer handler/api/v/3/code/{systemKey}/timer/{name}
POSTHANDLERS - Create trigger handler/api/v/3/code/{systemKey}/trigger/{name}
POSTDATABASES - Create a external database connection/api/v/4/external-db/{systemKey}/{name}/data
POSTDATA - Create collection/api/v/4/data/{systemKey}/{collectionName}/index
POSTWEBHOOKS - Executing a webhook/api/v/4/webhook/execute/{systemKey}/{webhookName}
PUTADAPTERS - Send command to edge/api/v/4/{SystemKey}/adapters/{AdapterName}/control
POSTDATA - Create Unique Index/api/v/4/data/{systemKey}/{collectionName}/uniqueindex
POSTDEVICES - Authenticate device/api/v/2/devices/{SystemKey}/auth
POSTDEVELOPER - Add new role/admin/user/{systemKey}/roles
DELETEDEVELOPER - Delete code service/codeadmin/v/2/{systemKey}/{serviceName}
PUTDEVELOPER - Update code service/codeadmin/v/2/{systemKey}/{serviceName}
POSTDEVELOPER - Add new column/admin/user/{systemKey}/columns
DELETEEdge - Delete edge/api/v/3/edges/{systemKey}/{name}
PUTEDGE - Update edge/api/v/3/edges/{systemKey}/{name}
PUTDEVICES - Update info/api/v/2/devices/{systemKey}/{name}
POSTCODE - Call/Execute code service/api/v/1/code/{systemKey}/{serviceName}
DELETEDATABASES - Delete a external database connection/api/v/4/external-db/{systemKey}/{name}
PUTDATABASES - Update external database credentials/api/v/4/external-db/{systemKey}/{name}
DELETEADAPTERS - Delete adapter/api/v/4/{SystemKey}/adapters/{AdapterName}
POST2FA - Create Email Communication/admin/settings/email-service
DELETEDEVELOPER - Delete library/codeadmin/v/2/library/{systemKey}/{libName}
PUTDEVELOPER - Update library/codeadmin/v/2/library/{systemKey}/{libName}
DELETEDEPLOYMENT - Delete a deployment/api/v/3/{systemKey}/deployments/{deploymentName}
PUTDEPLOYMENT - Update deployment/api/v/3/{systemKey}/deployments/{deploymentName}
POSTDEVELOPER - Add user/admin/user/{systemKey}
DELETEADAPTERS - Delete adapter files/api/v/4/{SystemKey}/adapters/{AdapterName}/files/{fileName}

What HumDay can read from ClearBlade

These are the operations a schedule or a trigger can watch.

GETUSERS - Get all users/api/v/1/user
GETUSERS - Get user info/api/v/1/user/info
GETFILES - Returns a list of metadata for buckets in system/api/v/4/bucket_sets/{systemKey}
GETDEVELOPER - Gets the information for the platform/api/about
GETMESSAGING - Gets list of topics/api/v/4/message/{systemKey}/topics
GETDEVELOPER - Get all failed services/codeadmin/failed
GETDATA(id) - Get items/api/v/1/data/{collectionID}
GETMESSAGING - Get history/api/v/1/message/{systemKey}
GETGets list of configuration information for all adapter files/api/v/4/{SystemKey}/adapters/{AdapterName}/files
GETWEBHOOKS - Executes query string payload webhook/api/v/4/webhook/execute/{systemKey}/{webhookName}
GETDEVELOPER - Get system's failed services/codeadmin/failed/{systemKey}
GETCODE - Get all failed services using Query/api/v/4/{systemKey}/code/failed
GETDEVICES - Get connected device list/api/v/4/devices/{systemKey}/connections
GETFILES - Get a file's metadata in a box/api/v/4/bucket_sets/{systemKey}/{deploymentName}/file/meta
GETMESSAGING - Gets number of topics/api/v/4/message/{systemKey}/topics/count
GETDATA(name) - Get items/api/v/1/collection/{systemKey}/{collectionName}
GETFILES - Returns metadata for specified bucket/api/v/4/bucket_sets/{systemKey}/{deploymentName}
GETEDGE - Fetch all edges/api/v/2/edges/{systemKey}
GETDEVELOPER - Get list of users and information/admin/user/{systemKey}
GETDEVICES - Get all devices/api/v/2/devices/{SystemKey}
GETADAPTERS - Get all adapters/api/v/4/{SystemKey}/adapters
GETADAPTERS - Download file from adapter/api/v/4/{SystemKey}/adapters/{AdapterName}/files/{fileName}
GETDEPLOYMENTS - Gets all deployment names and descriptions for a system/api/v/3/{systemKey}/deployments
GETDATABASES - Retrieves all external database connections/api/v/4/external-db/{systemKey}
GETDEVELOPER - Get all libraries/codeadmin/v/2/library/{systemKey}
GETDATA - Get collections/api/v/3/allcollections/{systemKey}
GETDATA - Get list of indexes/api/v/4/data/{systemKey}/{collectionName}/listindexes
GETFILES - Get all files metadata in a box/api/v/4/bucket_sets/{systemKey}/{deploymentName}/files
GETHANDLERS - Get timer handlers/api/v/3/code/{systemKey}/timers
GETEDGE - Get count/api/v/3/edges/{systemKey}/count
GETHANDLERS - Get trigger handlers/api/v/3/code/{systemKey}/triggers
GETCODE - Returns code services and settings/api/v/3/code/codemeta/{systemKey}
GETDEVICES - Get count/api/v/3/devices/{systemKey}/count
GETEDGE - Get columns/api/v/3/edges/{systemKey}/columns
GETDATA(id) - Get columns/api/v/1/data/{collectionID}/columns
GETEDGE - Get device columns/api/v/3/devices/{systemKey}/columns

How automating ClearBlade works

Describe the outcome. Say what you want to happen, in your own words. No node graphs, no field mapping.
Approve the contract. HumDay writes down exactly what it will do, what it will touch, and what it will never do. You approve it before anything is built.
See it proven. The program runs and shows you the result before it is allowed near your live ClearBlade account.
Grant access, then go live. You approve the specific ClearBlade operations it may use — and only those.

Popular ClearBlade integrations

Connect ClearBlade to the tools people pair it with most.