Can HumDay connect to Adobe Experience Manager (AEM)?

Yes. HumDay reads Adobe Experience Manager (AEM)'s own published API description and derives the operations from it, so there is no hand-built connector to wait for. 48 operations are documented.

Do I need to write code to automate Adobe Experience Manager (AEM)?

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 Adobe Experience Manager (AEM) account.

What can HumDay do in Adobe Experience Manager (AEM)?

30 of the 48 documented operations change something in Adobe Experience Manager (AEM), and 18 read from it. HumDay only ever uses the specific operations your approved contract needs.

Is my Adobe Experience Manager (AEM) 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 Adobe Experience Manager (AEM) is held behind that approval.

Automate Adobe Experience Manager (AEM)

HumDay reads Adobe Experience Manager (AEM)’s own published API description and derives 48 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 Adobe Experience Manager (AEM) is

Swagger AEM is an OpenAPI specification for Adobe Experience Manager (AEM) API

API host: adobe.local

What HumDay can do in Adobe Experience Manager (AEM)

30 documented operations change something in Adobe Experience Manager (AEM).

POSTUpdate path/{path}/
POSTUpdate truststore/etc/truststore
POSTUpdate cqactions html/.cqactions.html
POSTUpdate truststore/libs/granite/security/post/truststore
POSTUpdate authorizables/libs/granite/security/post/authorizables
POSTUpdate querybuilder json/bin/querybuilder.json
DELETEDelete name/{path}/{name}
POSTUpdate name/{path}/{name}
POSTUpdate sslSetup html/libs/granite/security/post/sslSetup.html
POSTUpdate update jsp/crx/packmgr/update.jsp
POSTUpdate service jsp/crx/packmgr/service.jsp
POSTUpdate treeactivation html/libs/replication/treeactivation.html
POSTUpdate name/system/console/bundles/{name}
POSTUpdate configNodeName/apps/system/config/{configNodeName}
POSTUpdate name rw html/{path}/{name}.rw.html
POSTUpdate setpassword jsp/crx/explorer/ui/setpassword.jsp
POSTUpdate path/crx/packmgr/service/.json/{path}
POSTUpdate authorizableId ks html/{intermediatePath}/{authorizableId}.ks.html
DELETEDelete name/etc/replication/agents.{runmode}/{name}
POSTUpdate name/etc/replication/agents.{runmode}/{name}
POSTUpdate org apache felix http/apps/system/config/org.apache.felix.http
POSTUpdate org apache http proxyconfigurator config/apps/system/config/org.apache.http.proxyconfigurator.config
POSTUpdate com shinesolutions aem passwordreset Activator/apps/system/config/com.shinesolutions.aem.passwordreset.Activator
POSTUpdate action/system/console/jmx/com.adobe.granite:type=Repository/op/{action}
POSTUpdate org apache sling security impl ReferrerFilter/apps/system/config/org.apache.sling.security.impl.ReferrerFilter
POSTUpdate org apache sling servlets get DefaultGetServlet/apps/system/config/org.apache.sling.servlets.get.DefaultGetServlet
POSTUpdate com shinesolutions healthcheck hc impl ActiveBundleHealthCheck/apps/system/config/com.shinesolutions.healthcheck.hc.impl.ActiveBundleHealthCheck
POSTUpdate org apache sling jcr davex impl servlets SlingDavExServlet/apps/system/config/org.apache.sling.jcr.davex.impl.servlets.SlingDavExServlet
POSTUpdate com adobe granite auth saml SamlAuthenticationHandler/system/console/configMgr/com.adobe.granite.auth.saml.SamlAuthenticationHandler
POSTUpdate com adobe granite auth saml SamlAuthenticationHandler config/apps/system/config/com.adobe.granite.auth.saml.SamlAuthenticationHandler.config

What HumDay can read from Adobe Experience Manager (AEM)

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

GETRead health/system/health
GETRead querybuilder json/bin/querybuilder.json
GETRead name/{path}/{name}
GETRead configMgr/system/console/configMgr
GETRead installstatus jsp/crx/packmgr/installstatus.jsp
GETRead truststore p12/etc/truststore/truststore.p12
GETRead status productinfo json/system/console/status-productinfo.json
GETRead script html/crx/packmgr/service/script.html
GETRead truststore json/libs/granite/security/truststore.json
GETRead name json/system/console/bundles/{name}.json
GETRead authorizableId ks json/{intermediatePath}/{authorizableId}.ks.json
GETRead login html/libs/granite/core/content/login.html
GETRead name/etc/replication/agents.{runmode}/{name}
GETRead agents runmode 1 json/etc/replication/agents.{runmode}.-1.json
GETRead 1 json/crx/server/crx.default/jcr:root/.1.json
GETRead store p12/{intermediatePath}/{authorizableId}/keystore/store.p12
GETRead name version zip/etc/packages/{group}/{name}-{version}.zip
GETRead filter tidy 2 json/etc/packages/{group}/{name}-{version}.zip/jcr:content/vlt:definition/filter.tidy.2.json

How automating Adobe Experience Manager (AEM) 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 Adobe Experience Manager (AEM) account.
Grant access, then go live. You approve the specific Adobe Experience Manager (AEM) operations it may use — and only those.