Can HumDay connect to Mailscript?

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

Do I need to write code to automate Mailscript?

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 Mailscript account.

What can HumDay do in Mailscript?

24 of the 38 documented operations change something in Mailscript, and 14 read from it. HumDay only ever uses the specific operations your approved contract needs.

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

Automate Mailscript

HumDay reads Mailscript’s own published API description and derives 38 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 Mailscript

What HumDay can do in Mailscript

24 documented operations change something in Mailscript.

POSTSend an email/send
PUTUpdate a user/user
POSTAdd an action/actions
POSTClaim a new Domain/domains
POSTClaim a new Mailscript address/addresses
POSTStart verification process for external email address or sms number/verifications
POSTSetup a trigger/triggers
POSTSetup workflow/workflows
POSTClaim a Mailscript workspace/workspaces
POSTCheck a new Domain/domains/verify/{domain}
POSTAdd address key/addresses/{address}/keys
POSTVerify an email address or sms number with a code/verifications/{verification}/verify
POSTSet a property on a workflow/workflows/set
DELETEDelete an action/actions/{action}
PUTUpdate an action key/actions/{action}
DELETERemove a domain/domains/{domain}
DELETEDelete a trigger/triggers/{trigger}
PUTUpdate a trigger/triggers/{trigger}
DELETEDelete a mailscript address/addresses/{address}
DELETEDelete a workflow/workflows/{workflow}
PUTUpdate an workflow/workflows/{workflow}
DELETEDelete an integration/integrations/{integration}
DELETEDelete address key/addresses/{address}/keys/{key}
PUTUpdate an address key/addresses/{address}/keys/{key}

What HumDay can read from Mailscript

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

GETGet the authenticated user/user
GETGet all actions for the user/actions
GETGet all integrations for the user/integrations
GETGet all verificats for the user/verifications
GETGet all inputs you have access to/inputs
GETGet all domains you have access to/domains
GETGet all triggers you have access to/triggers
GETGet all addresses you have access to/addresses
GETGet all workflows you have access to/workflows
GETGet all workspaces you have access to/workspaces
GETList address keys/addresses/{address}/keys
GETGet a token for opening a daemon connection/daemons/{daemon}/token
GETGet domain verification/domains/verify/{domain}
GETGet address key/addresses/{address}/keys/{key}

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