Generate an identifier string for a new record or operation.
Before you begin
Section titled “Before you begin”- A Server Connect action using a supported Node.js or PHP runtime.
Generate an identifier string for a new record or operation.
Settings
Section titled “Settings”| Setting | Meaning and example |
|---|---|
| Name | Names the returned identifier string, for example record_id. Although the installed inspector rule labels its output type as boolean, the runtime returns a string. |
| Output | Includes the identifier string in the response when enabled. Default off. It can be used internally in a subsequent insert step without Output. |
Verification example
Section titled “Verification example”Generate an identifier in a test action and inspect its type: it should be a hyphenated string. Use the returned value for a new record’s identifier and retain a database uniqueness constraint rather than relying only on generation.
Behavior and limits
Section titled “Behavior and limits”Node.js uses crypto.randomUUID with a UUID v4 fallback. The installed PHP implementation places the variant-bit mask on a different byte than expected for a strict UUID v4 implementation; validate its output before using it with a strict UUID consumer. An identifier is not an authorization token or proof of permission.
Use the complete authentication flow
Section titled “Use the complete authentication flow”Use the security and login guides for the surrounding provider, form, session and server-access configuration.
Check your result
Section titled “Check your result”You can configure the documented fields and distinguish a successful result from the failure or limitation described here.