convex-functions

Convex functions support structured serverless logic by separating queries, mutations, actions, and HTTP actions. This separation provides clear boundaries for data access, external integrations, and structured function composition across reliable APIs and workflows.

The best way to structure HTTP actions in a Convex runtime is to maintain a clear separation of concerns from internal functions. Use typed validators and proper error handling to ensure consistent interfaces and reliable external integrations.

To handle errors in Convex actions and mutations, apply practical patterns for internal functions and runtime considerations. Implementing robust argument validation and structured error handling ensures reliable behavior across common automation tasks and APIs.

Yes, Convex supports typed validators for argument shapes and return values across HTTP actions. This satisfies validators for runtime behavior and return structures, ensuring consistent interfaces and runtime safety for external integrations.

You should use Convex actions instead of queries when external integrations require structured function composition beyond reliable data access. Actions handle external API calls and automation tasks, while queries strictly manage validated data retrieval.