Recipe: Send email from Retool or Appsmith
Call Notify from Retool or Appsmith with a REST query — x-api-key and POST /api/email/send.
Use Retool or Appsmith when an internal admin tool should send transactional email — password reset for a user row, receipt, ops notice. Still transactional, not newsletters.
Both products are REST clients. One HTTPS resource / query is enough.
Prerequisites
- API key (prefer a domain-locked sending_access key)
- Verified domain for production custom
from - A Retool or Appsmith app where the key can live in secrets / resource config
Shared request
- Method:
POST - URL:
https://notify.cx/api/email/send - Headers:
Content-Type:application/jsonx-api-key: your Notify API key (from a secret / resource credential)
- Body:
{
"to": "user@example.com",
"from": "noreply@your-verified-domain.com",
"subject": "Your account update",
"html": "<p>Your account was updated.</p>"
}
html is preferred; message and text also work.
Retool
- Resources → create a REST API resource with base URL
https://notify.cx. - Add a default header
x-api-keyfrom a Retool secret (Configuration Variables / Secrets). - In the app, add a query:
POST/api/email/send, body JSON as above. - Bind
to/subject/htmlto table row or form inputs ({{ table1.selectedRow.email }}, etc.). - Run the query from a button with a confirmation modal for sends.
Appsmith
- Create an Authenticated API datasource for
https://notify.cx. - Auth / headers: add
x-api-keyfrom Appsmith’s encrypted datasource field (not a widget). - New API query:
POST/api/email/sendwith JSON body. - Use
{{ InputEmail.text }}(or table bindings) fortoand other fields. - Trigger from a button; show success/error from the query response.
Sandbox vs production
Until the domain is verified, production custom from stays locked. Use sandbox vs production or POST /api/email/send/test for API rehearsal.
After you send
Check Email Logs or the logs API. Delivery events can go to a webhook on Pro+.