server-actions

Server actions in Next.js handle form submissions on the server. Mark a function with 'use server', add TypeScript types, validate inputs with Zod, and execute database operations directly. This keeps sensitive logic off the client and ensures type safety end-to-end.

Use Zod to define schemas that validate form inputs before database operations. Server actions parse and validate the data server-side, catching errors before mutations occur. This prevents invalid data from reaching your database and provides typed results.

Call Next.js revalidatePath after create, update, or delete operations to refresh cached pages. Server actions combined with revalidatePath ensure users see fresh data immediately after mutations without manual cache management.

Yes. Server actions handle file uploads with server-side validation and execute analytics tracking mutations. Both use the same 'use server' pattern, authentication via cookies, and database schema operations for consistent, secure handling.

Yes. Server actions should verify user identity via cookies before executing mutations like create, update, or delete. This prevents unauthorized data changes and is enforced server-side where it cannot be bypassed.

Server actions execute directly in React components with automatic type safety and form binding, while API routes require manual request handling. Server actions reduce boilerplate for form submissions and database mutations in Next.js apps.