Skip to content

Recipes & patterns

Common Server Connect Actions recipes you can reuse: database CRUD, emails, security, and more.

Use these recipes when you know the outcome you want but have not yet decided how to structure the action. Each pattern connects a common backend job to the kind of steps Server Connect uses well, so you can choose a practical starting point before building the full action.

CRUD
Query Insert/Update/Delete
Integrations
Email Webhooks
Security
Auth Access control
Pick a recipe based on the outcome you want.
Start with database + security if your endpoint touches data.
Keep actions small and composable when possible.

Create a Database Connection for your target(s), then reuse it across all your Server Connect Actions.

Create one connection per environment/target.
Reuse the connection in all DB steps.

Use Database Query / Insert / Update / Delete steps to read and write data. Combine with input variables for filters and record IDs.

Validate inputs before writing.
Return consistent JSON shapes for the UI.

Use the Mailer step to send form data or notifications. Test locally first, then configure production credentials.

Test with a safe recipient first.
Store credentials in the right place for your deployment.

Use Security Provider settings to restrict access, protect data endpoints, and manage logged-in user sessions.

Protect endpoints that return private data.
Use session/user context in steps when needed.

Pick what you want to learn next.