Employee onboarding is one of the highest-leverage automation targets for HR teams, and also one of the most consistently under-automated. The reason is not a lack of awareness — every HR professional knows that a chaotic first week creates a poor impression and extends the time before a new hire is productive. The reason is that onboarding is genuinely multi-party: HR owns some steps, IT owns others, the hiring manager owns others, and the new hire themselves needs to complete document submissions. Coordinating across those parties with a checklist in a shared document, or worse, a series of manual emails, creates the chaos that everyone wants to avoid.
This guide walks through building a complete new-hire onboarding workflow in TASKBASE that handles document collection, IT provisioning triggers, and manager approval gates. The specific configuration choices here reflect a mid-size Japanese company context — a 200–500 person organization where HR, IT, and line managers are distinct functions with distinct systems, but without the dedicated onboarding software that larger enterprises might deploy.
Mapping the onboarding process before building the workflow
Before touching TASKBASE, spend 30 minutes mapping the actual onboarding process. The goal is a list of tasks, for each task: who is responsible, what input it needs (from the new hire, from HR, from the previous task), and what output it produces. A rough version might look like this:
- HR creates new hire record in HR system → triggers the workflow
- New hire submits required documents (employment eligibility, bank details, health certificate, emergency contact) via a form
- HR reviews submitted documents, confirms completeness
- IT receives provisioning request — company email, device assignment, system access based on role
- Manager receives pre-start briefing, confirms desk assignment, confirms first-day schedule
- HR sends welcome communication to new hire with first-day logistics
- HR schedules orientation and sends calendar invite
- End of first week: manager confirms new hire has all required access and has completed compliance training
Mapping this before building ensures the workflow reflects the real process, not an idealized version of it. In particular, notice where humans are in the critical path (document review, manager confirmation) versus where tasks can be automated without a human gate (sending calendar invites, posting notifications, logging records).
Step 1: The trigger node — HR record creation
In TASKBASE, create a new workflow and drop a Trigger node onto the canvas. For an organization using kintone as its HR system, configure the trigger as a kintone record creation event in the employee database. If you use a Google Sheet or Notion database as the HR record source, the same pattern applies with the respective connector.
The trigger fires when a new hire record is created. Map the data fields from the HR record to named workflow variables: employee_name, employee_email, start_date, department, role, manager_email, office_location. These variables will be referenced throughout the rest of the workflow.
One practical note: if the HR record is created weeks before the start date, you may want a Wait node after the trigger that holds the workflow until a defined number of days before the start date. A new hire record created three weeks out should not immediately send the new hire a document submission request — the timing of that communication matters for the new hire experience.
Step 2: Document collection request
After the trigger (or after the Wait node if you are using one), add a Notify action node that sends the new hire a document submission request. Configure it to send an email to employee_email with a link to a document collection form — either a TASKBASE native form, a Google Form, or a Notion form, depending on what your organization already uses.
Following the notification, add a Human Gate node configured to wait for the document submission event. When the form is submitted, the Human Gate receives the submission and passes the document data forward. Set an SLA timer on this gate — if the new hire has not submitted within 3 business days of receiving the request, send a reminder notification. Configure a second reminder at 5 days, and an escalation to HR at 7 days (in case the new hire has a question or a problem submitting).
The document collection step is also where an AI Step can add value if your HR team receives a high volume of new hires: the AI step can perform an initial completeness check on the submitted documents (are all required fields present, is the format correct, are the dates plausible) before the HR review gate. This does not replace the HR review — it surfaces obvious problems before a human spends time on the submission.
Step 3: HR document review gate
Add a Human Gate node configured with the HR reviewer role. The gate presents the submitted documents to the HR reviewer and asks them to confirm completeness and accuracy. The gate should display: the new hire's name and start date, a checklist of required documents and their submission status, and any flags raised by the AI completeness check if you included one.
Configure two outcomes: Approved (documents complete, proceed) and Revision Required (return to new hire for correction, re-trigger the document collection step). For the Revision Required path, the new hire notification node should include the specific items that need correction, not just a generic "please resubmit" message.
Step 4: IT provisioning trigger
Once HR approves the documents, a parallel branch handles IT provisioning. This is a split from the main flow: the IT provisioning tasks run in parallel with the manager briefing, not sequentially.
Add a Notify action node that sends the IT provisioning team a structured request: employee name, start date, department, role, office location, and the access profile associated with that role (if your organization maintains role-to-access mappings, this can be a lookup from a reference table). The notification can go to a Slack channel, a kintone ticket, or an email to the IT helpdesk queue — whatever the IT team uses as their work intake.
If your IT provisioning is fully automated (self-service account creation via a directory service), this step can be an API call instead of a notification. For most mid-size organizations without dedicated IT automation infrastructure, a structured notification to the IT team is the right starting point. The IT team completes the provisioning tasks manually; the workflow tracks whether they have confirmed completion.
Add a Human Gate for IT to confirm that provisioning is complete. This gate should have a clear completion definition: company email created, device ordered or assigned, system access roles applied. Set an SLA timer appropriate to your IT team's provisioning lead time — if device ordering takes 5 business days, the SLA timer should reflect that, not pressure IT with an unrealistic 24-hour window.
Step 5: Manager pre-start briefing
On the parallel branch, add a Human Gate for the hiring manager. The manager receives a notification — typically a Slack message or email — containing: the new hire's start date, their role summary, a link to the new hire's submitted documents (so the manager knows who is joining), a request to confirm desk assignment and first-day schedule, and a reminder about any role-specific orientation materials they are responsible for providing.
The manager confirms completion of their pre-start tasks in the gate interface. This confirmation is logged in the workflow run, which means HR has a record that the manager's pre-start responsibilities were completed, with timestamp.
Step 6: Converge and send welcome communication
After both parallel branches — IT provisioning and manager briefing — complete their gates, the workflow converges at an AND-join node. Only when both are confirmed does the workflow proceed to the welcome communication step.
This convergence point matters: it prevents sending the new hire a detailed first-day schedule before the manager has confirmed the desk assignment, and it prevents sending the schedule before IT has confirmed the device will be ready. The new hire's first-day experience is only as good as the coordination that preceded it.
The welcome communication node sends the new hire a personalized message — using the workflow variables to insert their name, manager name, office location, and start time — along with the first-day logistics. Schedule an orientation calendar invite using the Google Calendar or Outlook connector.
Step 7: First-week check-in
Add a final Wait node — set to fire 5 business days after the start date — followed by a Human Gate for the manager. The manager confirms: the new hire has the required system access, has completed any required compliance training, and any questions or issues from the first week have been addressed. This closes the onboarding workflow and creates a record that the onboarding process completed successfully.
The complete workflow, from trigger to first-week check-in, runs across approximately 10–12 nodes. It handles a process that previously required HR to manually track 8–10 email threads per new hire, across three different stakeholder groups, over a two-to-three-week period. The automation does not make the decisions — HR still reviews documents, IT still provisions access, managers still prepare for their new team member. It coordinates the handoffs and ensures nothing is missed.
