Insider OneInstall

Summary

Create a new Insider One user record or update an existing one by sending identifiers, attributes, and events to the upsert API. Configure one or more identifiers, then supply data through the form fields or raw JSON; the operation can batch incoming items into API requests.

Inputs

• Identifiers (required) — Provide one or more of email, Insider One ID, phone number in E.164 format, UUID, or custom identifier key-value pairs.
• Attributes — In form mode, set standard fields such as name, age, birthday, country, consent flags, or static segment IDs. You can add other standard attributes and custom attributes; custom attribute names go under custom and do not need a c_ prefix. In JSON mode, provide the attributes object directly.
• Events — Add events with a required event name and RFC 3339 timestamp, plus optional standard and custom parameters. In JSON mode, provide an events array directly.
• Additional Settings — Set batch size for users sent per request, an error callback endpoint, whether existing attributes or arrays are overwritten (notAppend, default true), and whether hooks are skipped (default false).

Output shape

A list of items containing the API response, associated with the input item or batch.

The node sends a POST request to Insider One's user upsert endpoint. In form mode, empty string and zero-valued attributes are omitted; birthday and event timestamps receive a Z suffix if missing, and comma-separated static segment IDs are converted to integers. With batch size greater than one, one API request is made per batch; the batch size is read from settings, but the source does not apply a minimum beyond the UI declaration.

Links

• n8n community nodes installation guide