Can HumDay connect to Ijenko IoE² IoT to create end user applications?

Yes. HumDay reads Ijenko IoE² IoT to create end user applications's own published API description and derives the operations from it, so there is no hand-built connector to wait for. 67 operations are documented.

Do I need to write code to automate Ijenko IoE² IoT to create end user applications?

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 Ijenko IoE² IoT to create end user applications account.

What can HumDay do in Ijenko IoE² IoT to create end user applications?

35 of the 67 documented operations change something in Ijenko IoE² IoT to create end user applications, and 32 read from it. HumDay only ever uses the specific operations your approved contract needs.

Is my Ijenko IoE² IoT to create end user applications 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 Ijenko IoE² IoT to create end user applications is held behind that approval.

Automate Ijenko IoE² IoT to create end user applications

HumDay reads Ijenko IoE² IoT to create end user applications’s own published API description and derives 67 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.

What HumDay can do in Ijenko IoE² IoT to create end user applications

35 documented operations change something in Ijenko IoE² IoT to create end user applications.

POSTNew User/account/users
PATCHUpdate User information/me
DELETEDelete a User/account/users/{userId}
PATCHModify a User/account/users/{userId}
POSTCreate a Notification/places/{placeId}/notifications
POSTCreate a Place/account/places
POSTAsk for a new password/auth/reset-password
DELETEDelete a Notification/notifications/{notificationId}
PATCHModify a Notification/notifications/{notificationId}
POSTCreate a Program/places/{placeId}/programs
POSTAdd dynamically a functionality/devices/{deviceId}/functionalities
POSTGet a token using login+password/auth/login
POSTRevoke a token/auth/revoke
POSTRefresh a token/auth/refresh
PATCHModify metadata of a Notification/notifications/{notificationId}/metadata
POSTChange the password/account/change-password
PATCHModify metadata/account/users/{userId}/metadata
PATCHUpdate a Place/places/{placeId}
PATCHUpdate a Device/devices/{deviceId}
DELETEDelete a Program/programs/{programId}
PATCHModify a Program/programs/{programId}
PATCHModify a Functionality/functionalities/{functionalityId}
PATCHModify tags/devices/{deviceId}/tags
DELETERevoke a Token/account/tokens/{tokenId}
POSTRun the Program/programs/{programId}/run
PATCHModify metadata/places/{placeId}/metadata
PATCHModify metadata/devices/{deviceId}/metadata
PATCHModify metadata of a Program/programs/{programId}/metadata
PATCHModify tags/functionalities/{functionalityId}/tags
PATCHModify metadata/functionalities/{functionalityId}/metadata
POSTRun actions/places/{placeId}/run/{action}
POSTRun actions/devices/{deviceId}/run/{action}
POSTRun an action/functionalities/{functionalityId}/run/{action}
PUTOpen/Close the pairing window/places/{placeId}/buses/{busId}/pairing
PUTModify an Attribute value/functionalities/{functionalityId}/attributes/{attributeName}

What HumDay can read from Ijenko IoE² IoT to create end user applications

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

GETList Users of the Account/account/users
GETInformation about the User/me
GETList accessible Places/places
GETInformation about a User/account/users/{userId}
GETList Notifications/places/{placeId}/notifications
GETList Places of the Account/account/places
GETList active Tokens of the Account/account/tokens
GETList metadata/notifications/{notificationId}/metadata
GETList metadata/account/users/{userId}/metadata
GETInformation about a Notification/notifications/{notificationId}
GETList Buses/places/{placeId}/buses
GETList tags/devices/{deviceId}/tags
GETList of Devices/places/{placeId}/devices
GETList metadata/places/{placeId}/metadata
GETList Programs/places/{placeId}/programs
GETList metadata/devices/{deviceId}/metadata
GETList metadata/programs/{programId}/metadata
GETList Functionalities/places/{placeId}/functionalities
GETList tags/functionalities/{functionalityId}/tags
GETList metadata/functionalities/{functionalityId}/metadata
GETInformation about a Place/places/{placeId}
GETInformation about a Device/devices/{deviceId}
GETInformation about a Program/programs/{programId}
GETInformation about a Functionality/functionalities/{functionalityId}
GETHistory of executions of a Program/programs/{programId}/log
GETGet history of multiple attributes/functionalities/{functionalityId}/attributes
GETGet electricity virtual flows/places/{placeId}/electricity/flows
GETGet autonomy rate of the place/places/{placeId}/electricity/autonomy
GETGet self-consumption rate of the place/places/{placeId}/electricity/self-consumption
GETGet electricity flows setup/places/{placeId}/electricity/flows/setup
GETState of the pairing window/places/{placeId}/buses/{busId}/pairing
GETGet an Attribute value/functionalities/{functionalityId}/attributes/{attributeName}

How automating Ijenko IoE² IoT to create end user applications 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 Ijenko IoE² IoT to create end user applications account.
Grant access, then go live. You approve the specific Ijenko IoE² IoT to create end user applications operations it may use — and only those.