ExampleTemplate
New hires from NEOGOV to Munis (employee and payee vendor)
Every morning, reads yesterday's hires from NEOGOV and creates each one in Munis: an employee record for payroll, and a payee vendor so expense reimbursements can be paid.
This flow
6 steps
StartsOn a schedule
SystemsNEOGOV, Tyler Enterprise ERP (Munis)
Branches0
Stored recordsNone: pass-through
§ The flow
The whole flow, as it appears on the canvas.
Scroll sideways on small screens. Colors show the kind of step: start, read, change, decide, write.
§ Step by step
What each step does.
- 01 · Start · On a schedule
Daily at 6 am
- Cron
0 6 * * *(workspace time zone)
Then: Recent hires in NEOGOV
- Cron
- 02 · Read · Get records · NEOGOV
Recent hires in NEOGOV
- Reads Recent hires (personnel actions) from NEOGOV
- Filter:
startdate={{ $last_success_at | default:"" }} - At most 200 records per run
Then: Fields for: create the munis employee; Fields for: create the payee vendor
- 03 · Change · Map fields
Fields for: create the munis employee
- Shapes each record into 8 fields:
employeeNumber,firstName,lastName,email,department,jobClass,hireDate,status
Then: Create the Munis employee
- Shapes each record into 8 fields:
- 04 · Change · Map fields
Fields for: create the payee vendor
- Shapes each record into 5 fields:
vendorNumber,name,email,address1,status
Then: Create the payee vendor
- Shapes each record into 5 fields:
- 05 · Write · Send records · Tyler Enterprise ERP (Munis)
Create the Munis employee
- Creates Employees in Tyler Enterprise ERP (Munis)
- 06 · Write · Send records · Tyler Enterprise ERP (Munis)
Create the payee vendor
- Creates Vendors in Tyler Enterprise ERP (Munis)
§ Systems
Connectors used
Swap any of them for another system with the same kind of data.
Run this flow on your systems.
We'll set up a workspace with your systems in a sandbox and build your first flow with you.