Integrations.
The API is the same everywhere — these guides only differ in how your stack sends the request. Pick yours and copy the example; every one of them works as it stands against a running instance.
Framework guides
Node.js
The official mailan-node client: send, read back, uploads, captcha, typed errors.
Open guideReact
A controlled form, one fetch call, three states — no library needed.
Open guideNext.js
Server action or client component — both routes to the same endpoint.
Open guideAstro
A static page with an island that submits — no server of your own.
Open guideVue
Composition API, v-model and the same three states.
Open guideWordPress & Elementor
Without a plugin: an HTML block, or Elementor's own form widget.
Open guideWebflow
Point the native Webflow form at Mailan and keep the designer workflow.
Open guideConnected services
Beyond the frontend there are the outgoing ones: Slack, Discord, Google Sheets, Notion, Zapier, Airtable and your own webhook receive every submission. They are switched on per form in the dashboard.
To the webhook reference- Slack
- Discord
- Google Sheets
- Notion
- Zapier
- Airtable
- Own webhook
Something else?
Anything that can send an HTTP POST can use Mailan — there is nothing framework-specific in the endpoint. The submit reference has the full contract; for plain HTML pages the client script saves you writing any JavaScript at all.