New hires into Munis
Every morning, yesterday's hires from NEOGOV become a Munis employee record for payroll and a payee vendor for reimbursements.
NEOGOV is HR software built for the public sector. Cities use Insight for job postings and applications, Onboard for new hires, Perform for evaluations and Core HR for employee records.
SentraBridge reads job postings, applications, recent hires, employees and departments, and creates or updates employee records. The connector is built from NEOGOV's public OpenAPI file and is confirmed with the city's own API user during setup.
| resource | read | write | changes only | fields |
|---|---|---|---|---|
| Job postings | list, read one | create | — | ID, Link, Classification, Posted from, Posted until, Continuous… |
| Applications | list, read one | — | — | ID, First name, Middle name, Last name, Email, City… |
| Employees | list, read one | create, update | yes | ID, Employee number, Active, First name, Last name, Preferred name… |
| Recent hires (personnel actions) | list, read one | — | — | Hire ID, Link, Created, Authorized, First name, Last name… |
| Departments | list | — | — | ID, Name, Code |
Every morning, yesterday's hires from NEOGOV become a Munis employee record for payroll and a payee vendor for reimbursements.
New hires open a ServiceNow request so IT can set up accounts and equipment before the start date.
Open postings are published as a page on the city's Sentra CMS site with a link to apply.
Active employees and departments are upserted nightly into SQL Server for directories and reports.
Systems cities commonly connect with NEOGOV, each with its own connector page.
Yes. NEOGOV publishes an OpenAPI description of its API, covering postings, applications, personnel actions and employees, with basic sign-in for an API user.
Read recent hires each morning, map name, position and department, then create the employee and payee vendor in Munis. A template for this flow is ready to adapt.
It is built from NEOGOV's public OpenAPI file and tested on a sandbox. Paging and list shapes are confirmed with your API user before anything runs.
No. Records pass through in memory. Run history keeps counts and record IDs only.
We'll set up a workspace with your systems in a sandbox and build your first flow with you.