Create A Person
create_a_personCreate a new person in Procore for a company ID, supplying required fields like name, status, and group IDs. Returns the created person with its new ID.
Instructions
Creates a Person for a given company ID. company_id defaults to the value set by procore_set_config when omitted. Creates the person and returns it with its new id (HTTP 201); calling it again creates another record. Failures come back as an error payload carrying the HTTP status — commonly 401 when the token has expired, 403 without tool permission, and 404 when an id does not resolve. Required parameters: company_id, first_name, last_name, is_user, is_assignable, status, group_ids. Procore API: Resource Management > Resource Planning. Endpoint: POST /rest/v1.0/workforce-planning/v2/companies/{company_id}/people
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| dob | No | JSON request body field — date of birth of the Person. Accepts ISO Date String, UTC Date String, or MS Numeric Epoch Time. | |
| No | JSON request body field — the email that the Person will log in with. Required if `is_user` is true. | ||
| phone | No | JSON request body field — the Person's phone number, including country and area code. Must be unique among all registered People. **Note:** Pass `null` or exclude the field if the Person should not have a phone number. | |
| status | Yes | JSON request body field — the status of the Person. `active` means the person is visible in all pages, while `inactive` hides the person unless filtered. Inactive People do not count against billing plans. | |
| country | No | JSON request body field — the country where the Person is located. | |
| is_user | Yes | JSON request body field — determines if the Person can log into the app. | |
| zipcode | No | JSON request body field — the postal/zip code of the Person. | |
| password | No | JSON request body field — password for logging in. If not provided, an email will be sent to the user to set their password. Must be at least 8 characters with one uppercase, one lowercase, and one number. | |
| address_1 | No | JSON request body field — first part of the Person's address. | |
| address_2 | No | JSON request body field — second part of the Person's address (e.g., Apartment, Suite, Unit). | |
| city_town | No | JSON request body field — the city or town where the Person is located. | |
| group_ids | Yes | JSON request body field — array of UUIDs representing the Groups this Person belongs to. Can be empty if the Person is an Admin. | |
| last_name | Yes | JSON request body field — last Name of the Person. | |
| no_invite | No | JSON request body field — if `true`, the Person will be created with all user properties but will not receive an invite until triggered manually by an Admin. | |
| company_id | Yes | URL path parameter — unique identifier for the company. This parameter accepts both formats: - **Recommended**: Procore company ID (integer) - Use this for new integrations - Legacy: LaborChart UUID format (uuid string... | |
| first_name | Yes | JSON request body field — first Name of the Person. | |
| hired_date | No | JSON request body field — date the Person was hired. Accepts ISO Date String, UTC Date String, or MS Numeric Epoch Time. | |
| hourly_wage | No | JSON request body field — hourly wage rate for the Person. Used for automatic spend tracking. | |
| job_title_id | No | JSON request body field — uUID reference to a Job Title in the LaborChart System. | |
| is_assignable | Yes | JSON request body field — determines if the Person can be assigned to tasks. | |
| state_province | No | JSON request body field — the state or province where the Person is located. | |
| can_receive_sms | No | JSON request body field — determines if the Person can receive SMS notifications. | |
| employee_number | No | JSON request body field — internal employee identifier. | |
| can_receive_email | No | JSON request body field — determines if the Person can receive email notifications. | |
| can_receive_mobile | No | JSON request body field — determines if the Person can receive mobile push notifications if they have the app installed. | |
| permission_level_id | No | JSON request body field — uUID of the Permission Level assigned to the Person. | |
| emergency_contact_name | No | JSON request body field — name of the Person's emergency contact. | |
| emergency_contact_email | No | JSON request body field — email address of the emergency contact. | |
| notification_profile_id | No | JSON request body field — uUID of the Notification Profile for the user. | |
| emergency_contact_number | No | JSON request body field — phone number of the emergency contact. | |
| emergency_contact_relation | No | JSON request body field — the relationship between the Person and their emergency contact. |