Create a recipient through Zapier
Creates a recipient through entities.create, including program counter allocation and configured custom-field processing. Requires manage_programs, program access and the primitive scope. Custom fields declared unique are checked across the program; tag names cannot contain commas.
Authorizations
Passport bearer token authentication for legacy admin sessions.
Body
Validated input accepted by this Zapier transport.
Program containing the recipient or sponsorship. Validation: required|integer.
11
Sponsor-count target accepted by the recipient program. Compatibility input retains the primitive accepted numeric/string or tag-list representation. Validation: nullable.
1
Sponsorship funding target accepted by the recipient program. Compatibility input retains the primitive accepted numeric/string or tag-list representation. Validation: nullable.
25
Whether the recipient is visible in public sponsorship listings. Validation: nullable|boolean.
true
Profile email address. Validation: nullable|email.
"jane@example.org"
Custom-field values keyed by the configured form field names. Validation: nullable|array.
Tag names assigned to the recipient; names cannot contain commas. Validation: nullable|array.
Stable caller key used by the selected mutation to prevent duplicate records. Validation: nullable|string|max:191.
191"external-record-001"
Response
Created, updated or replayed record; this transport unwraps the primitive success envelope.
A sponsorship recipient — the 'who/what' a donor sponsors. Entities can represent children, families, animals, projects, or any other sponsorable thing depending on the program. Like donors, entities have standardized columns plus arbitrary json_fields defined by the program's Hysform. Donations target an entity through the historical donation.designation column.
Internal entity ID.
4711
Owning Gratona client (multi-tenant scope).
207
Program this entity belongs to. The program's hysform_id defines which custom fields appear in json_fields.
11
Recipient sponsorship state, commonly0unsponsored or1sponsored. Compatibility serializers may retain the numeric string.
Whether the recipient is publicly visible. Raw compatibility model responses may use0/1.
Whether the recipient is featured in public listings. Raw compatibility model responses may use0/1.
Custom profile/record fields. Raw model responses retain the encoded JSON string; projection endpoints may return a decoded map or list. Use the record form definition to interpret field keys.
Set when the entity was created via CSV import.
null
"2025-09-01T14:00:00Z"
"2025-12-30T09:12:00Z"
null