Can HumDay connect to Google Apps Script?

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

Do I need to write code to automate Google Apps Script?

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 Google Apps Script account.

What can HumDay do in Google Apps Script?

7 of the 16 documented operations change something in Google Apps Script, and 9 read from it. HumDay only ever uses the specific operations your approved contract needs.

Is my Google Apps Script 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 Google Apps Script is held behind that approval.

Automate Google Apps Script

HumDay reads Google Apps Script’s own published API description and derives 16 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 Google Apps Script is

Manages and executes Google Apps Script projects.

API host: script.googleapis.com

What HumDay can do in Google Apps Script

7 documented operations change something in Google Apps Script.

POSTCreates a new, empty script project with no script files and a base manifest file./v1/projects
POSTCreates a new immutable version using the current code, with a unique version number./v1/projects/{scriptId}/versions
POSTCreates a deployment of an Apps Script project./v1/projects/{scriptId}/deployments
POSTRuns a function in an Apps Script project./v1/scripts/{scriptId}:run
PUTUpdates the content of the specified script project./v1/projects/{scriptId}/content
DELETEDeletes a deployment of an Apps Script project./v1/projects/{scriptId}/deployments/{deploymentId}
PUTUpdates a deployment of an Apps Script project./v1/projects/{scriptId}/deployments/{deploymentId}

What HumDay can read from Google Apps Script

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

GETList information about processes made by or on behalf of a user, such as process type and current status./v1/processes
GETList information about a script's executed processes, such as process type and current status./v1/processes:listScriptProcesses
GETGets the content of the script project, including the code source and metadata for each script file./v1/projects/{scriptId}/content
GETGet metrics data for scripts, such as number of executions and active users./v1/projects/{scriptId}/metrics
GETList the versions of a script project./v1/projects/{scriptId}/versions
GETGets a script project's metadata./v1/projects/{scriptId}
GETLists the deployments of an Apps Script project./v1/projects/{scriptId}/deployments
GETGets a version of a script project./v1/projects/{scriptId}/versions/{versionNumber}
GETGets a deployment of an Apps Script project./v1/projects/{scriptId}/deployments/{deploymentId}

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