Actions252
- Api Keys Actions
- Attachments Actions
- Blocklists Actions
- Calendar Channel Event Associations Actions
- Find Many Calendar Channel Event Associations
- Create One Calendar Channel Event Association
- Create Many Calendar Channel Event Associations
- Find One Calendar Channel Event Association
- Delete One Calendar Channel Event Association
- Update One Calendar Channel Event Association
- Find Calendar Channel Event Association Duplicates
- Companies Actions
- Calendar Channels Actions
- Calendar Event Participants Actions
- Calendar Events Actions
- Connected Accounts Actions
- Favorite Folders Actions
- Favorites Actions
- Message Channel Message Associations Actions
- Find Many Message Channel Message Associations
- Create One Message Channel Message Association
- Create Many Message Channel Message Associations
- Find One Message Channel Message Association
- Delete One Message Channel Message Association
- Update One Message Channel Message Association
- Find Message Channel Message Association Duplicates
- Message Channels Actions
- Message Folders Actions
- View Fields Actions
- Message Participants Actions
- Messages Actions
- Message Threads Actions
- Notes Actions
- Note Targets Actions
- Opportunities Actions
- People Actions
- Tasks Actions
- Task Targets Actions
- Timeline Activities Actions
- View Filter Groups Actions
- View Filters Actions
- View Groups Actions
- Views Actions
- View Sorts Actions
- Webhooks Actions
- Workflow Automated Triggers Actions
- Workflow Runs Actions
- Workflows Actions
- Workflow Versions Actions
- Workspace Members Actions
Overview
This node allows you to create multiple people records in bulk within the "People" resource of the connected API. It is useful when you need to add many contacts or user profiles at once, such as importing a list of clients, team members, or leads into a system. For example, you could use this node to upload a batch of new employees with their contact details and social links in one operation, saving time compared to creating each person individually.
Properties
| Name | Meaning |
|---|---|
| Depth | Determines how much related nested data is included in the response: - 0: Only the primary person's information. - 1: The person plus directly related objects (no further nesting). - 2: The person, directly related objects, and their related objects. |
| Body | JSON object representing one or more people to create. This includes fields like name (first and last), phones (primary and additional), links (primary and additional), LinkedIn link, and emails. The structure must follow the expected schema for a person. |
Output
The node outputs JSON data representing the created people records. The output includes the newly created person objects with their properties as returned by the API, respecting the requested depth level for nested related objects. There is no binary data output.
Dependencies
- Requires an API key credential to authenticate requests to the Twenty API.
- The base URL for the API is configured via credentials.
- The node uses the OpenAPI specification bundled internally to build requests.
Troubleshooting
- Invalid JSON in Body: If the JSON provided in the Body property is malformed, the node will fail. Ensure the JSON syntax is correct.
- Authentication Errors: Missing or invalid API credentials will cause authentication failures. Verify that the API key credential is correctly set up.
- Depth Parameter Misuse: Providing an unsupported depth value may result in unexpected responses or errors. Use only 0, 1, or 2.
- API Rate Limits: Creating many people at once might hit API rate limits; consider batching requests if errors occur.
- Schema Mismatch: The body JSON must conform to the expected schema for people objects; missing required fields can cause errors.
Links and References
- Twenty API Documentation (example placeholder, replace with actual)
- n8n Documentation on JSON Input