Webstudio → BaserowREST API resourceEasy
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.
Webstudio → BaserowREST API resourceMedium
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.
Webstudio → SupabaseREST API resourceMedium
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.
Webstudio → SupabaseREST API resourceMedium
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.
Webstudio → DirectusREST API resourceMedium
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.
Webstudio → NocoDBREST API resourceMedium
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.
Webstudio → PocketBaseREST API resourceEasy
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.
Webstudio → n8nWebhookEasy
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.
Webstudio → ListmonkREST API resourceEasy
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.
Webstudio → ResendREST API resourceEasy
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.
Webstudio → Cloudflare Pages / WorkersNativeMedium
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.
Webstudio → CoolifyNativeMedium
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.
