Webhook In: POST records straight into a table — What a POST may write

Any field a person could type into — including AI fields, which store text like any other. Computed fields (Lookup, Rollup, Formula, AutoNumber) have no stored value to write, attachments only move through their own upload endpoints, a Doc is written on its own page, and a field governed by a lifecycle or approval policy is refused here for the same reason Email In refuses to map one: an anonymous URL must not move records through states. The endpoint's page lists exactly which fields are out, and why, under the example. Relation values are record ids. Every id is checked against the relation's own target table before anything is stored — a guessed or foreign id links nothing, and the POST is told so. People values name members of the workspace, each by email address or by person id — an array, or just one. An address is matched against the workspace's members, ignoring case, and stored as that member's id, so a sender that only knows who it means by address can still assign them. A name, an address or id that isn't a member's, or an address two members share is refused rather than stored, and the POST is told which field.