Skip to main content
Fires once when a record is created, on any object. There is no per-object subscription: filter on objectId in your handler if you only care about deals.

Payload

string
required
The new record’s id. Always present: a payload without one is not sent at all.
string
The object the record belongs to. Omitted if the emitter did not carry it.
object
The record’s fields, keyed by property key. Omitted entirely when the emitter carried no field list, which is not the same as a record with no fields.

Reading the fields

Keys are property keys (annual_value), stable across renames. Values are the stored shape, so a select is ["opt_…"] and a relation is ["rec_…"]. See Payload format. A field whose property key cannot be resolved is dropped rather than included under an empty key, so record may be narrower than the record itself.
Unlike record.updated, the record object here does not carry an id key. The record’s id is recordId on the payload.

Worth knowing

  • Bulk creation does not fire this. Imports, job runs and other automated bulk writes are suppressed. See the catalog.
  • A form submission creates a record, and fires both this and form.submitted. If you act on both, deduplicate on recordId.
  • The payload is a snapshot at creation. Anything set afterwards arrives as record.updated.

Example