Can HumDay connect to Cloud Elements ecwid?

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

Do I need to write code to automate Cloud Elements ecwid?

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 Cloud Elements ecwid account.

What can HumDay do in Cloud Elements ecwid?

21 of the 42 documented operations change something in Cloud Elements ecwid, and 21 read from it. HumDay only ever uses the specific operations your approved contract needs.

Is my Cloud Elements ecwid 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 Cloud Elements ecwid is held behind that approval.

Automate Cloud Elements ecwid

HumDay reads Cloud Elements ecwid’s own published API description and derives 42 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 Cloud Elements ecwid

21 documented operations change something in Cloud Elements ecwid.

POSTCreate an order in the eCommerce system.With the exception of the 'id' field, the required fields indicated in the 'Order' model are those required to create a new order.The payme…/orders
POSTCreate a new customer in eCommerce system.With the exception of the 'id' field, the required fields indicated in the 'Customer' model are those required to create a new customer/customers
POSTCreate a new product in eCommerce system.With the exception of the 'id' field, the required fields indicated in the 'Product' model are those required to create a new product/products
POSTCreate an asynchronous bulk query job./bulk/query
POSTCreate a new bulk download job (asynchronous)/bulk/download
DELETEDelete an order associated with a given ID from your eCommerce system./orders/{id}
PATCHUpdate an order associated with a given ID in the eCommerce system./orders/{id}
DELETEDelete a customer associated with a given ID from your eCommerce system./customers/{id}
PATCHUpdate an customer associated with a given ID in the eCommerce system.The update API uses the PATCH HTTP verb, so only those fields provided in the customer object will be updated…/customers/{id}
POSTUpload a file of objects to be bulk uploaded to the provider./bulk/{objectName}
POSTCreate an {objectName}/{objectName}
PUTCancel an asynchronous bulk query job./bulk/{id}/cancel
DELETEDelete a product associated with a given ID from your eCommerce system./products/{id}
PATCHUpdate a product associated with a given ID in the eCommerce system./products/{id}
POSTCreate an {objectName}/{objectName}/{objectId}/{childObjectName}
DELETEDelete an {objectName}/{objectName}/{objectId}
PATCHUpdate an {objectName}/{objectName}/{objectId}
PUTUpdate an {objectName}/{objectName}/{objectId}
DELETEDelete an {childObjectName}/{objectName}/{objectId}/{childObjectName}/{childObjectId}
PATCHUpdate an {childObjectName}/{objectName}/{objectId}/{childObjectName}/{childObjectId}
PUTUpdate an {childObjectName}/{objectName}/{objectId}/{childObjectName}/{childObjectId}

What HumDay can read from Cloud Elements ecwid

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

GETFind orders in the eCommerce system, using the provided CEQL search expression./orders
GETFind customers in the eCommerce system, using the provided CEQL search expression./customers
GETFind orders in the customer associated with a given ID./customers/{id}/orders
GETRetrieve the payments in the eCommerce system for the specified order/orders/{orderId}/payments
GETRetrieve an order associated with a given ID from the eCommerce system./orders/{id}
GETRetrieve a customer associated with a given ID from the eCommerce system./customers/{id}
GETGet a list of all the available objects./objects
GETFind products in the eCommerce system, using the provided CEQL search expression./products
GETRetrieve the refunds in the eCommerce system for the specified order/orders/{orderId}/refunds
GETSearch for {objectName}/{objectName}
GETPing the Element to confirm that the Hub Element has a heartbeat./ping
GETGet a list of all the field for an object./objects/{objectName}/metadata
GETFetch all the bulk jobs for an instance/bulk/jobs
GETRetrieve the results of an asynchronous bulk query./bulk/{id}/{objectName}
GETRetrieve a product associated with a given ID from the eCommerce system./products/{id}
GETSearch for {childObjectName}/{objectName}/{objectId}/{childObjectName}
GETRetrieve the errors of a bulk job./bulk/{id}/errors
GETRetrieve the status of a bulk job./bulk/{id}/status
GETRetrieve an {objectName}/{objectName}/{objectId}
GETGet swagger docs for an object./objects/{objectName}/docs
GETRetrieve an {childObjectName}/{objectName}/{objectId}/{childObjectName}/{childObjectId}

How automating Cloud Elements ecwid 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 Cloud Elements ecwid account.
Grant access, then go live. You approve the specific Cloud Elements ecwid operations it may use — and only those.