Reading and changing records
Record actions operate on an explicitly selected object and fields. They do not search across all objects or infer access to related records. Choose the object first, then configure the selector and the data the step can read or change.
Read Recordβ
Select a record ID, either as a fixed value or from a supported preceding field, and choose the readable attributes. For a record-triggered workflow, the trigger's record ID is a natural selector. A mapped record ID must come from a source that runs on every path to this step.
The result includes the record identity, display name and selected data. Selected data keys are present, with null for absent values. A read made after a Wait observes the record at that read step. Once accepted, its result is retained: delivery retries reuse it even if the record changes later.
Update Recordβ
Select a record ID and the attributes to write. Each value can be fixed or mapped. Attributes you omit are preserved. An explicit null clears a nullable attribute; it does not mean βleave unchanged.β Each attribute can appear only once.
A mapped value from a branch that did not run also supplies null, so it clears the existing nullable attribute. It does not leave that attribute unchanged. To preserve the old value when the branch is skipped, place the update inside that branch or omit the attribute from the update.
For choice and state attributes, select the actual configured choice identity rather than entering its display label as a value. Relationship targets and tracked locations require explicit related-record read access.
Example: update a request's review note from a preceding Script result while preserving its other fields. The accepted record result can be used by subsequent steps.
Upsert Recordβ
Use Upsert when a stable business key identifies a record. The key must be a writable, unique text attribute, with a non-null text value. A mapped key must come from a source that runs on every path to this step. Matching is case-sensitive. An existing match is updated; otherwise a new record is created.
Configure the key in the key selector, not again among the values to write. When creation is possible, provide the fields required to create a valid record. Upsert needs both create and update access, in addition to read access.
Access, schema changes and resultsβ
Publication fixes the selected object and readable/writable field contract. Later object-schema changes can invalidate that contract. Review and republish the affected workflow rather than assuming its field selection updates automatically. Parent-controlled objects and managed-field writes are unsupported.
Record operations retain their committed results. Earlier writes survive a later workflow failure or cancellation. Their ordinary record events and webhooks still occur, but workflow-originated writes do not automatically start further workflows.
Preview does not execute these operations or return their real output. Verify effects in an actual run. The record-action API reference documents selectors, value types and access declarations.