Proven stacks and how the tools connect

Baserow table webhook (rows.created/updated) posts to an n8n Webhook node, e.g. to trigger a Cloudflare/Webstudio rebuild, send a Slack message on new submissions, or push approved leads to Listmonk.

Coolify one-click service templates deploy Listmonk with Postgres (and similarly n8n, Baserow, Directus, NocoDB, Umami, Plausible) with automatic HTTPS via Traefik.

Directus Flow with an Event Hook trigger (items.create/update) and a Webhook/Request URL operation to n8n; useful to sync newsletter opt-ins stored in Directus to Listmonk.

Verify the domain in SES (DKIM, custom MAIL FROM), get production access, create SMTP credentials and add them in Listmonk Settings > SMTP (email-smtp.<region>.amazonaws.com:587, STARTTLS) with a sensible rate limit. For bounces: SNS topic for bounces/complaints with HTTPS subscription to /webhooks/service/ses and enable SES bounce processing in Listmonk.

Create a Broadcast message stream in Postmark (marketing mail must not use the transactional stream), use its SMTP token in Listmonk SMTP settings with the X-PM-Message-Stream header, and point Postmark's bounce webhook to /webhooks/service/postmark.

AWS SES node sends templated or plain emails (notifications, lead confirmations) with IAM credentials scoped to ses:SendEmail.

Native Baserow node: Create Row with field mapping from the webhook payload; use Get Many for de-duplication by email before insert. Credentials: Baserow host + username/password or token.

HTTP Request node POST to https://<listmonk>/api/subscribers with API user + token (Basic auth), body {email, name, lists:[id], status:'enabled', preconfirm_subscriptions:false} to trigger double opt-in. Handle 409 (already exists) by updating lists via PUT /api/subscribers/lists.

After a Webstudio form webhook, use an HTTP Request node POST https://api.postmarkapp.com/email (n8n only ships a Postmark Trigger node, not a send node) with X-Postmark-Server-Token to send an internal notification and a confirmation to the visitor using a Postmark template.

HTTP Request node POST (form-urlencoded) to https://<sendy>/subscribe with api_key, list, email, name and boolean=true; Sendy returns '1' on success. The same call can be made from a Webstudio Form Resource if you accept the API key sitting in a server-side Resource.

Connect NocoDB to the Supabase Postgres connection string as an external data source, giving editors a spreadsheet UI over Supabase tables while the site reads through Supabase REST.

Enter AWS IAM access keys in Sendy settings; Sendy verifies identities and sends via the SES API. Set up SNS bounce and complaint topics pointing to Sendy's endpoints (Sendy can create them automatically). v7 shows SES enforcement status in the sidebar.

Sendy supports SMTP for non-SES providers per brand; enter Postmark broadcast-stream SMTP credentials. Bounce handling is less automatic than with SES, so check Postmark suppressions regularly.

Copy elements in the Webflow Designer and paste into Webstudio; the converter maps Webflow elements and styles to Webstudio instances. CMS content must be moved separately (CSV export to Baserow etc.).

Create a database token in Baserow. In Webstudio add a Resource variable (GET) to https://api.baserow.io/api/database/rows/table/<id>/?user_field_names=true with header Authorization: Token <token>; add filter/search params from URL system variables. Bind the result's .results to a Collection; use a dynamic page path (/blog/:slug) with a filter__field__equal param for detail pages. Resources run server-side, so the token is not exposed.

Export with the Webstudio CLI (webstudio link, sync, build --template cloudflare or static), then deploy with Wrangler or connect a Git repo to Pages. Static export loses server features (forms, dynamic resources at request time); the JS app keeps them on Workers.

Export the project with the CLI as a Docker-ready app, push to Git, and deploy as an application in Coolify on Hetzner or DigitalOcean; the same server can host Baserow, n8n and Listmonk.

Create a static token for a read-only role in Directus. Use a Resource on REST (/items/<collection>?filter[status][_eq]=published&fields=*,image.*) or GraphQL (/graphql with a query built in the Directus GraphQL playground). Images via /assets/<id>?width=... transformations.

Copy components/animations from the GitHub repo and paste into Webstudio (HTML Embed or the copy-paste data for Webstudio); animation scripts go into custom code. No licence file yet, so check with the author before commercial reuse.

Embed a Formbricks link survey via iframe in an HTML Embed, or load the JS SDK in custom code for in-page surveys; responses go to Baserow/n8n via Formbricks webhooks.

Generate an API token in NocoDB, then Resource GET to /api/v2/tables/<tableId>/records?where=(Status,eq,Published) with header xc-token. Response list is in .list. If NocoDB sits on a Supabase/Postgres DB, the same data can alternatively be read via Supabase REST.

Paste the Plausible script tag into Project Settings > Custom code (head). Track form submits as custom events with the plausible() call or tagged CSS classes.

Set the collection's List/View API rule to public (or pass a token), then Resource GET to https://<host>/api/collections/<name>/records?filter=(published=true). Bind .items to a Collection.

Enable Row Level Security with a public select policy, then add a Resource GET to https://<ref>.supabase.co/rest/v1/<table>?select=*&published=eq.true with headers apikey and Authorization: Bearer <anon key>. Bind to Collections and dynamic pages; PostgREST filters (eq, order, limit) map to query params.

Add the Umami tracker script to custom head code; add data-umami-event attributes to buttons in Webstudio's attribute panel for event tracking.

Create a POST Resource on the Form to /api/database/rows/table/<id>/?user_field_names=true with the token header and a JSON body bound to formData fields (formData.name, formData.email). Add it as a Form action (up to 10 actions run in parallel). Use a token with create-only permission on that table.

Without n8n: POST Resource to Listmonk's public endpoint /api/public/subscription with JSON {email, name, list_uuids:[...]} (no API key needed; enable public subscription and the lists must be public). Listmonk sends the double opt-in mail itself.

Add an n8n Webhook node (POST), copy the production URL, and add it as a REST Resource action on the Webstudio Form (or as the action URL of a legacy Webhook Form). n8n receives formData and can branch to any number of tools. Return a JSON response for success messages.

Email action without automation: POST Resource to https://api.resend.com/emails with Authorization: Bearer <key>, body {from, to, subject, html} with formData bound in. Webstudio Cloud also has built-in Email to owner/visitor actions, so Resend is mainly for self-hosted exports or custom domains/templates.

POST Resource to /rest/v1/<table> with anon key headers and Prefer: return=minimal, body from formData. Requires an RLS insert-only policy; for validation or spam checks route via an Edge Function or n8n instead.