Send Email integration
Email yourself
Send-email is NoClick's built-in notification node, so any workflow can email you without connecting an inbox or supplying an API key. Its single operation emails you directly: you write the subject and body, and the message lands in the inbox tied to your NoClick account, wrapped in a branded template with a footer that names the sending workflow and a one-click link to disable it. Because the recipient is resolved from your own account rather than a config field, you cannot point it at anyone else, which keeps it firmly in notify-yourself territory. Drop it at the end of a run and you hear about the result instead of checking the canvas.
What you can automate with Send Email
Send Email operations
Questions
Only you. The recipient is resolved server-side from the email on your NoClick account, not from a field you fill in, so a workflow can notify you but cannot send mail to customers or third parties. That lock is deliberate and keeps the node to self-notifications.
No. Send-email needs no credentials at all; it sends from a NoClick address to your account inbox out of the box. Add the node, write a subject and body, and it works.
Yes. The node is request and response, so you wire it downstream of any trigger, schedule, or condition, and that upstream event decides when the email goes out. A form submission, a cron tick, or a failed check can each land a message in your inbox.
You control the subject and body, and you can template in values from earlier nodes so the message carries real run data. It arrives in a branded wrapper with a footer showing which workflow sent it and a one-click link to disable that node's emails.
Yes. Wired into an agent as a tool, the send operation becomes a callable tool that takes a subject and body, with the same recipient lock to your account. The agent can then email you a status or result mid-task without any extra setup.
