# NEOGOV

> Read NEOGOV job postings, applications and hires, look up employees, departments and divisions, add new hires to Onboard and start their onboarding, and start workflows when postings go up, applications arrive or hires are made.

App · 17 actions. Web page: https://docs.lodol.com/docs/integrations/neogov

## Actions

### Create prehire

Add a new hire to Onboard as a prehire, with their start date, department, division and position, and send them an activation email if asked.

**Inputs**

- Email (`email`, text, required): The new hire's email address.
- First name (`first_name`, text, required): The new hire's first name.
- Last name (`last_name`, text, required): The new hire's last name.
- Start date (`expected_start_date`, date, required): The day they start.
- Username (`username`, text): Their NEOGOV username. Leave empty to use the email address.
- Middle name (`middle_name`, text): The new hire's middle name.
- Phone (`phone`, text): Their phone number.
- Street address (`address`, text): Their street address.
- City (`city`, text): Their city.
- State (`state`, text): Their state or province. One of: `1` (Alabama), `2` (Alaska), `3` (Arizona), `4` (Arkansas), `5` (California), `6` (Colorado), `7` (Connecticut), `8` (Delaware), `9` (District of Columbia), `10` (Florida), and 66 more.
- ZIP code (`zip_code`, text): Their ZIP or postal code.
- Department (`department`, text): Their department.
- Division (`division`, text): Their division.
- Position ID (`position_id`, text): Their position's NEOGOV ID, such as an employee's position ID.
- Status (`status`, text): Prehire, or Authorized prehire. Defaults to Prehire. One of: `0` (Prehire), `1` (Authorized prehire). Default: `0`.
- Send activation email (`send_activation`, true/false): Email the new hire a link to activate their NEOGOV account. Default: `false`.

**Outputs**

- `email` (text): Their email address
- `employee_id` (text): The prehire's employee ID
- `user_id` (text): The prehire's user ID
- `username` (text): Their NEOGOV username

**Example output**

```json
{
  "email": "mary.smith@example.gov",
  "employee_id": "f572f9b11ec166df3dd04d23e4f6d485",
  "user_id": "149430d2bf433fa1ac5b8809651e0e8d",
  "username": "mary.smith@example.gov"
}
```

### Find applications

Find applications by one of: a job posting, the dates applicants were placed on an eligible list, or the dates postings closed.

**Inputs**

- Job posting (`job_posting_number`, text): Applications to this job posting. Pick one, or type its job number.
- Eligible on or after (`eligible_after`, date): Applicants placed on an eligible list on or after this date.
- Eligible on or before (`eligible_before`, date): Applicants placed on an eligible list on or before this date.
- Posting closed on or after (`closing_after`, date): Applications to postings that closed on or after this date.
- Posting closed on or before (`closing_before`, date): Applications to postings that closed on or before this date.
- How many (`limit`, number): How many applications to return, 1 to 500. Defaults to 50. From 1 to 500.
- Skip (`skip`, number): How many to skip, such as 'next_skip' from an earlier step. At least 0.

**Outputs**

- `applications` (list): The applications
- `count` (number): How many were returned
- `filter` (text): The search, as sent to NEOGOV
- `next_skip` (number): The 'Skip' for the next batch, empty on the last

**Example output**

```json
{
  "applications": [
    {
      "application_id": "9114dc99d78dc1a0404fea873f31e77e4753067166a5e3bf",
      "exam_type": "Open",
      "first_name": "Mary",
      "last_name": "Smith",
      "middle_name": "Pauline",
      "person_id": "1165361"
    }
  ],
  "count": 1,
  "filter": "jobpostingnumber eq '2026-0412'",
  "next_skip": null
}
```

### Find employee by username

Get the employee ID and user ID that go with a NEOGOV username, for 'Start onboarding'.

**Inputs**

- Username (`username`, text, required): The person's NEOGOV username, often their email address.

**Outputs**

- `employee_id` (text): The employee's ID
- `user_id` (text): The user's ID
- `username` (text): The username, as given

**Example output**

```json
{
  "employee_id": "f572f9b11ec166df3dd04d23e4f6d485",
  "user_id": "149430d2bf433fa1ac5b8809651e0e8d",
  "username": "mary.smith@example.gov"
}
```

### Find employees by date

Find the employees added, or changed, in Perform between two dates.

**Inputs**

- Employees (`date_field`, text): Those added, or those changed. Defaults to added. One of: `created` (Added), `updated` (Changed). Default: `created`.
- From (`since`, date): On or after this date.
- To (`until`, date): On or before this date.

**Outputs**

- `count` (number): How many were returned
- `employees` (list): The employees

**Example output**

```json
{
  "count": 1,
  "employees": [
    {
      "active": true,
      "created_at": "2026-11-16T07:56:54",
      "department": "City Clerk",
      "division": "Records",
      "email": "mary.smith@example.gov",
      "employee_number": "1212123",
      "first_name": "Mary",
      "hire_date": null,
      "id": "0123456789abcdef0123456789abcdef",
      "last_name": "Smith",
      "manager": "Alex Rivera",
      "position": "Deputy City Clerk",
      "start_date": "2026-11-16T00:00:00",
      "updated_at": "2026-11-16T07:56:54",
      "username": "mary.smith@example.gov"
    }
  ]
}
```

### Get agency-wide answers

Get the applicant's answers to the agency-wide questions on an application.

**Inputs**

- Application (`application`, text, required): The application's ID, from 'Find applications', a hire or a trigger.

**Outputs**

- `answers` (list): Each question and its answers
- `application_id` (text): The application's ID
- `count` (number): How many were returned
- `questions` (object): NEOGOV's own answer

**Example output**

```json
{
  "answers": [
    {
      "answers": [
        "No"
      ],
      "question": "Have you worked for this agency before?"
    }
  ],
  "application_id": "9114dc99d78dc1a0404fea873f31e77e4753067166a5e3bf",
  "count": 1,
  "questions": {}
}
```

### Get application

Get an application: the applicant's details, education, work history and skills.

**Inputs**

- Application (`application`, text, required): The application's ID, from 'Find applications', a hire or a trigger.

**Outputs**

- `application` (object): The application as NEOGOV holds it
- `summary` (object): The application, in short

**Example output**

```json
{
  "application": {
    "applicationfinfo": {
      "classification": "Deputy City Clerk",
      "datereceived": "10/28/2026 11:07:00",
      "email": "mary.smith@example.com",
      "firstname": "Mary",
      "id": "9114dc99d78dc1a0404fea873f31e77e4753067166a5e3bf",
      "jobpostingurl": "https://api.neogov.com/rest/jobpostings/56789abcdef0123456789abcdef01234",
      "lastname": "Smith"
    },
    "educationhistory": [
      {
        "degree": "Bachelor's",
        "graduate": "True",
        "major": "Public Administration",
        "schoolname": "Sacramento State"
      }
    ],
    "skills": [
      {
        "skilllevel": "Skilled",
        "skillname": "Laserfiche",
        "yearsofexperience": "4"
      }
    ],
    "workhistory": [
      {
        "companyname": "County of Yolo",
        "endyear": "2026",
        "positiontitle": "Records Clerk",
        "startyear": "2020"
      }
    ]
  },
  "summary": {
    "application_id": "9114dc99d78dc1a0404fea873f31e77e4753067166a5e3bf",
    "city": "Sacramento",
    "email": "mary.smith@example.com",
    "first_name": "Mary",
    "job_posting_id": "56789abcdef0123456789abcdef01234",
    "job_title": "Deputy City Clerk",
    "last_name": "Smith",
    "received_at": "2026-10-28T11:07:00",
    "state": "CA"
  }
}
```

### Get employee

Get an employee by NEOGOV ID or employee number, with position, department and manager.

**Inputs**

- Employee (`employee`, text, required): The employee's NEOGOV ID, or employee number when 'Find by' says so.
- Find by (`find_by`, text): Whether 'Employee' is the NEOGOV ID or the employee number. One of: `id` (NEOGOV employee ID), `employeenumber` (Employee number). Default: `id`.

**Outputs**

- `employee` (object): The employee as NEOGOV holds it
- `summary` (object): An employee

**Example output**

```json
{
  "employee": {
    "active": "True",
    "createddate": "11/16/2026 7:56:54 AM",
    "department": {
      "id": "0123456789abcdef0123456789abcdef",
      "name": "City Clerk"
    },
    "directmanager": {
      "fullname": "Alex Rivera",
      "id": "89abcdef0123456789abcdef01234567"
    },
    "division": {
      "id": "cdef0123456789abcdef0123456789ab",
      "name": "Records"
    },
    "email": "mary.smith@example.gov",
    "employeenumber": "1212123",
    "firstname": "Mary",
    "id": "0123456789abcdef0123456789abcdef",
    "lastname": "Smith",
    "phone": "555-222-3333",
    "position": {
      "id": "23456789abcdef0123456789abcdef01",
      "title": "Deputy City Clerk"
    },
    "updateddate": "11/16/2026 7:56:54 AM",
    "user": {
      "id": "6789abcdef0123456789abcdef012345",
      "username": "mary.smith@example.gov"
    }
  },
  "summary": {
    "active": true,
    "created_at": "2026-11-16T07:56:54",
    "department": "City Clerk",
    "division": "Records",
    "email": "mary.smith@example.gov",
    "employee_number": "1212123",
    "first_name": "Mary",
    "hire_date": null,
    "id": "0123456789abcdef0123456789abcdef",
    "last_name": "Smith",
    "manager": "Alex Rivera",
    "position": "Deputy City Clerk",
    "start_date": "2026-11-16T00:00:00",
    "updated_at": "2026-11-16T07:56:54",
    "username": "mary.smith@example.gov"
  }
}
```

### Get hire

Get a hire: start and orientation dates, offer, approval and the application it came from.

**Inputs**

- Hire (`hire`, text, required): The hire's ID, from 'List recent hires' or the New hire trigger.

**Outputs**

- `hire` (object): The hire (personnel action) as NEOGOV holds it
- `summary` (object): The hire, in short

**Example output**

```json
{
  "hire": {
    "applicationinfourl": "https://api.neogov.com/rest/applications/9114dc99d78dc1a0404fea873f31e77e4753067166a5e3bf",
    "authorizeddate": "2026-10-30T21:24:10.407Z",
    "dthirestart": "11/16/2026 08:00:00",
    "id": "23456789abcdef0123456789abcdef0123456789abcdef01",
    "isapproved": "Active",
    "jobpostingurl": "https://api.neogov.com/rest/jobpostings/56789abcdef0123456789abcdef01234",
    "offeramount": "72000",
    "personid": "10591789",
    "requisitionurl": "https://api.neogov.com/rest/requisitions/123456789abcdef0123456789abcdef0",
    "status": "Active"
  },
  "summary": {
    "application_id": "9114dc99d78dc1a0404fea873f31e77e4753067166a5e3bf",
    "approved": true,
    "authorized_at": "2026-10-30T21:24:10Z",
    "employee_url": "https://api.neogov.com/rest/employees/employeenumber/0038",
    "hire_id": "23456789abcdef0123456789abcdef0123456789abcdef01",
    "job_posting_id": "56789abcdef0123456789abcdef01234",
    "offer_amount": "72000",
    "offer_date": "2026-10-30T14:00:00",
    "orientation_date": "2026-11-16T09:00:00",
    "person_id": "10591789",
    "processed_by": "Jordan Lee",
    "requisition_id": "123456789abcdef0123456789abcdef0",
    "start_date": "2026-11-16T08:00:00",
    "status": "Active"
  }
}
```

### Get job posting

Get a job posting with its description, qualifications, salary and dates.

**Inputs**

- Job posting (`job_posting`, text, required): The job posting. Pick one, or give its ID from an earlier step.

**Outputs**

- `job_posting` (object): The job posting as NEOGOV holds it
- `summary` (object): A job posting

**Example output**

```json
{
  "job_posting": {
    "advfrom": "10/20/2026 08:00:00",
    "advto": "11/20/2026 17:00:00",
    "classification": "Deputy City Clerk",
    "closed": "Inactive",
    "departmenturl": "https://api.neogov.com/rest/departments/789abcdef0123456789abcdef0123456",
    "draft": "Inactive",
    "examplesofduties": "Prepares agendas and minutes.",
    "fulldescription": "Supports the City Clerk with records and elections.",
    "id": "56789abcdef0123456789abcdef01234",
    "jobnumber": "2026-0412",
    "jobtype": "Full-Time",
    "qualifications": "Two years of records experience.",
    "salarymax": "84000.00",
    "salarymin": "68000.00",
    "url": "https://api.neogov.com/rest/jobpostings/56789abcdef0123456789abcdef01234"
  },
  "summary": {
    "categories": [
      "Administration"
    ],
    "department_id": "789abcdef0123456789abcdef0123456",
    "exam_type": "Open",
    "id": "56789abcdef0123456789abcdef01234",
    "is_draft": false,
    "is_open": true,
    "job_number": "2026-0412",
    "job_type": "Full-Time",
    "location": "City Hall",
    "locations": [
      "CA-Sacramento"
    ],
    "posted_from": "2026-10-20T08:00:00",
    "posted_to": "2026-11-20T17:00:00",
    "salary_max": "84000.00",
    "salary_min": "68000.00",
    "title": "Deputy City Clerk"
  }
}
```

### Get requisition

Get a requisition: its title, status, class, department and vacancies.

**Inputs**

- Requisition (`requisition`, text, required): The requisition's ID, such as a hire's 'requisition_id'.

**Outputs**

- `requisition` (object): The requisition as NEOGOV holds it
- `summary` (object): The requisition, in short

**Example output**

```json
{
  "requisition": {
    "classtitle": "Deputy City Clerk",
    "datecreated": "09/01/2026 19:47:18",
    "departmentcode": "CLK",
    "desiredstartdate": "11/16/2026",
    "id": "123456789abcdef0123456789abcdef0",
    "requisitionnumber": "200399",
    "requisitiontitle": "Deputy City Clerk",
    "status": "Approved",
    "vacancies": "1"
  },
  "summary": {
    "class_title": "Deputy City Clerk",
    "created_at": "2026-09-01T19:47:18",
    "department_code": "CLK",
    "id": "123456789abcdef0123456789abcdef0",
    "number": "200399",
    "status": "Approved",
    "title": "Deputy City Clerk",
    "vacancies": "1"
  }
}
```

### List departments

List the agency's departments.

**Inputs**: None.

**Outputs**

- `count` (number): How many were returned
- `departments` (list): The departments

**Example output**

```json
{
  "count": 1,
  "departments": [
    {
      "active": true,
      "code": "CLK",
      "department": null,
      "id": "f0123456789abcdef0123456789abcde",
      "name": "City Clerk"
    }
  ]
}
```

### List divisions

List the agency's divisions, with the department each is in.

**Inputs**: None.

**Outputs**

- `count` (number): How many were returned
- `divisions` (list): The divisions

**Example output**

```json
{
  "count": 1,
  "divisions": [
    {
      "active": true,
      "code": "REC",
      "department": "City Clerk",
      "id": "cdef0123456789abcdef0123456789ab",
      "name": "Records"
    }
  ]
}
```

### List employees

List the agency's employees in Perform, a page at a time.

**Inputs**

- Page (`page`, number): Which page to return, from 1. Use the next page when 'has_more' is true. At least 1.
- Page size (`per_page`, number): How many to return per page, 1 to 500. Defaults to 50. From 1 to 500.

**Outputs**

- `count` (number): How many were returned
- `employees` (list): The employees
- `has_more` (true/false): Whether there may be a next page
- `page` (number): The page returned

**Example output**

```json
{
  "count": 1,
  "employees": [
    {
      "active": true,
      "created_at": "2026-11-16T07:56:54",
      "department": "City Clerk",
      "division": "Records",
      "email": "mary.smith@example.gov",
      "employee_number": "1212123",
      "first_name": "Mary",
      "hire_date": null,
      "id": "0123456789abcdef0123456789abcdef",
      "last_name": "Smith",
      "manager": "Alex Rivera",
      "position": "Deputy City Clerk",
      "start_date": "2026-11-16T00:00:00",
      "updated_at": "2026-11-16T07:56:54",
      "username": "mary.smith@example.gov"
    }
  ],
  "has_more": false,
  "page": 1
}
```

### List job postings

List the agency's job postings in Insight, a page at a time.

**Inputs**

- Page (`page`, number): Which page to return, from 1. Use the next page when 'has_more' is true. At least 1.
- Page size (`per_page`, number): How many to return per page, 1 to 500. Defaults to 50. From 1 to 500.

**Outputs**

- `count` (number): How many were returned
- `has_more` (true/false): Whether there may be a next page
- `job_postings` (list): The job postings
- `page` (number): The page returned

**Example output**

```json
{
  "count": 1,
  "has_more": false,
  "job_postings": [
    {
      "categories": [
        "Administration"
      ],
      "department_id": "789abcdef0123456789abcdef0123456",
      "exam_type": "Open",
      "id": "56789abcdef0123456789abcdef01234",
      "is_draft": false,
      "is_open": true,
      "job_number": "2026-0412",
      "job_type": "Full-Time",
      "location": "City Hall",
      "locations": [
        "CA-Sacramento"
      ],
      "posted_from": "2026-10-20T08:00:00",
      "posted_to": "2026-11-20T17:00:00",
      "salary_max": "84000.00",
      "salary_min": "68000.00",
      "title": "Deputy City Clerk"
    }
  ],
  "page": 1
}
```

### List recent hires

List the hires made in Insight since a date (and until one), a page at a time.

**Inputs**

- Since (`since`, date and time, required): Hires made since this time.
- Until (`until`, date and time): Hires made until this time. Leave empty for up to now.
- Page (`page`, number): Which page to return, from 1. Use the next page when 'has_more' is true. At least 1.

**Outputs**

- `count` (number): How many were returned
- `hires` (list): The hires
- `page` (number): The page returned

**Example output**

```json
{
  "count": 1,
  "hires": [
    {
      "authorized_at": "2026-10-30T21:24:10Z",
      "created_at": "2026-10-30T13:17:56",
      "hire_id": "23456789abcdef0123456789abcdef0123456789abcdef01"
    }
  ],
  "page": 1
}
```

### Set employee status

Make an employee active or inactive in Perform, cancelling their open evaluations if asked.

**Inputs**

- Employee (`employee`, text, required): The employee's NEOGOV ID, usually from an earlier step.
- Active (`active`, true/false, required): On to make the employee active, off to make them inactive.
- Cancel their evaluations (`cancel_evaluations`, true/false): Also set the employee's evaluations to Cancelled. Default: `false`.

**Outputs**

- `active` (true/false): Whether they are now active
- `cancelled_evaluations` (list): Evaluations cancelled
- `employee_id` (text): The employee's ID

**Example output**

```json
{
  "active": false,
  "cancelled_evaluations": [
    "8f774b941635facee4d00ed0ae412cfc"
  ],
  "employee_id": "0123456789abcdef0123456789abcdef"
}
```

### Start onboarding

Start onboarding for an employee or prehire, assigning their onboarding checklists.

**Inputs**

- Employee (`employee_id`, text, required): The employee ID, from 'Create prehire' or 'Find employee by username'.
- Assign checklists (`assign_checklists`, true/false): Assign the onboarding checklists. On unless turned off. Default: `true`.

**Outputs**

- `checklists_assigned` (true/false): Whether checklists were asked for
- `employee_id` (text): The employee's ID
- `started` (true/false): True once onboarding started

**Example output**

```json
{
  "checklists_assigned": true,
  "employee_id": "f572f9b11ec166df3dd04d23e4f6d485",
  "started": true
}
```
