Setup workflow in Mailscript
A documented Mailscript operation that changes something in your account. Describe the outcome you want in plain words — HumDay writes the program, proves it, and runs it.
What this operation does
Setup workflow
- POSTChanges data · workflows
api.mailscript.com/workflows
How HumDay uses it
- You describe the outcome. Not this operation by name — what you want to happen. HumDay works out which operations it needs.
- The contract names it. Before anything is built, you see exactly which Mailscript operations the program may use, and this is one of them.
- You approve access. Because this one changes data, it cannot run until you have explicitly granted it.
Other Mailscript operations
- Send an emailPOST · changes data
- Update a userPUT · changes data
- Add an actionPOST · changes data
- Claim a new DomainPOST · changes data
- Claim a new Mailscript addressPOST · changes data
- Start verification process for external email address or sms numberPOST · changes data
- Setup a triggerPOST · changes data
- Claim a Mailscript workspacePOST · changes data
Questions
- Can HumDay setup workflow in Mailscript?
- Yes. This operation is published in Mailscript's own API description, so HumDay can use it without a hand-built connector — once you have approved it for your automation.
- Will this change my Mailscript data?
- Yes — this is a POST operation, so it changes something in Mailscript. HumDay holds anything that writes behind an approval you grant explicitly, and the contract you approve says what it may touch.
- Do I need to write code?
- No. You describe the outcome you want in plain words. HumDay agrees a contract with you, writes the program, and shows you a proof run before anything touches your Mailscript account.
Where this came from
Read from a published API description for Mailscript at api.mailscript.com/v2/swagger. The description above is the provider’s own wording, not ours. Last published 2021-04-12.