mutations

Kinetic submission creation is handled by targeting a specific form within a kapp and passing the required data parameters. You can create standard records or public unauthenticated submissions by supplying the appropriate form identifier and payload.

Executing server-side Kinetic integrations with custom parameters is fully supported. You can call integrations directly to pass dynamic data between systems, automate external workflows, or trigger backend processes without requiring client-side execution.

Updating user profiles and kapp settings is best achieved through dedicated CRUD functions. You can modify user attributes like email addresses or change application configurations such as kapp themes directly using targeted administrative update calls.

The @kineticdata/react library is required for client-side interactions with the Kinetic platform. While server-side integration calls and submission lifecycle management can run independently, client-side data manipulation requires this dependency to function correctly.

Submission lifecycle management for Kinetic records allows you to create, fetch, and delete entries programmatically. This includes handling public unauthenticated creations and managing the full record lifecycle from initial data entry through deletion.