STEP 1
Connect BrioHR and WhosOff
Save credentials in WEXTL once. We store them encrypted and reuse the authorization across every workflow [3]. No coding or API skills required.
BrioHR and WhosOff Integration
Build hr integration workflows between BrioHR and WhosOff applications in 3 simple steps. Pick an action inside BrioHR, then subsequent action inside WhosOff, map fields once and automation will run exactly how you set it in visual builder.
3-day trialCancel anytimeUp to 10 minutes quick set up
- GDPR
- Data Encryption
- 2FA
- Local Data Region
Learn about BrioHR and WhosOff
Detailed info you need to know about BrioHR and WhosOff integrations in WEXTL. Explore which modules apps support and how you connect them.
How to connect BrioHR to WhosOff
Set up your BrioHR and WhosOff integration in 3 simple steps [2] — no coding required. Up to 10 minutes setup.
STEP 2
Build a workflow
Paste selected BrioHR and WhosOff nodes onto the canvas [4], or describe what you want and WEXTL wires the flow together with AI Builder.
STEP 3
Map your data
Choose which fields need to sync between BrioHR and WhosOff. Use filters or leverage a JS custom code step in between — everything is on the canvas.
How does the integration between BrioHR and WhosOff work in WEXTL?
WEXTL exposes actions and triggers for BrioHR and WhosOff that help you connect apps and automate repetitive tasks [1]. A trigger is an event that happens, an action — a step that performs when the event has occurred.
BrioHR actionsWhosOff actions
BrioHR modules
- Create a Claim ReportCreates a claim report in the system.
- Get Employee DetailsRetrieves employee details from the system.
- Get Leave SummariesRetrieves leave summaries from the service.
- Import Claim Report StatusImports the claim report status into the service.
- Import Employee Time Attendance DataImports employee time attendance data using API integration for clock-in and clock-out records.
- List Leave RecordsRetrieves a list of leave records.
- Make an API CallMakes an arbitrary API call to a specified endpoint.
WhosOff modules
- Approve or Decline LeaveApproves or declines a leave request for an employee.
- Approve OvertimeApproves overtime for a specific employee or project.
- Cancel LeaveCancels a leave request for an employee.
- Cancel OvertimeCancels an overtime record for a specific employee.
- Create a Calendar DayCreates a new calendar day with specified details.
- Create a DepartmentCreates a new department within the organization.
- Create a Leave TypeCreates a new leave type in the system.
- Create a Map User TagCreates a new tag for a user on a map.
- Create a TagCreates a new tag in the system.
- Create a UserCreates a new user account in the system.
- Create a User AllowanceCreates an allowance for a user in the system.
- Create a User NoteCreates a user note in the system.
- Create a User RestrictionCreates a restriction for a user.
- Create an Overtime TypeCreates a new overtime type entry in the system.
- Create WorkCreates a new work entry in the system.
- Decline Leave by IDDeclines a leave request using its ID.
- Delete a DepartmentDeletes a department from the service.
- Delete a Leave TypeDeletes a specified leave type from the system.
- Delete a Map User TagDeletes a tag from a user on the map.
- Delete a TagDeletes a tag from the system.
- Delete a UserDeletes a user from the system.
- Delete a User AllowanceDeletes a user's allowance from the system.
- Delete a User NoteDeletes a specific note belonging to a user.
- Delete a User RestrictionDeletes a user restriction from the system.
- Delete an Overtime TypeDeletes a specific overtime type from the system.
- Delete WorkDeletes a work item from the system.
- Get a CalendarRetrieves a calendar for viewing or processing.
- Get a Calendar SummaryRetrieves a summary of the calendar.
- Get a Company MessageRetrieves a message from the company database.
- Get a DepartmentRetrieves details of a specific department.
- Get a LeaveRetrieves information about a specific leave.
- Get a Leave by IDRetrieves a leave entry by its ID.
- Get a Leave TypeRetrieves the details of a specific leave type.
- Get a Message by IDRetrieves a message using its unique ID.
- Get a System MessageRetrieves a system message based on the provided parameters.
- Get a TagRetrieves a tag from the system.
- Get a UserRetrieves a user by ID from the service.
- Get a UserRetrieves information about a specific user.
- Get a UserRetrieves information about a user using version 4.1.
- Get a User AllowanceRetrieves the user's allowance information.
- Get a User NoteRetrieves a user note from the system.
- Get a User's Leave TypeRetrieves the leave type for a user.
- Get a User's MapRetrieves a map associated with a specific user.
- Get ApproversRetrieves a list of approvers for a specified process or document.
- Get CalendarRetrieves a calendar using version 4.1 of the API.
- Get Calendar DetailsRetrieves detailed information about a specified calendar.
- Get LeaveRetrieves leave information for the specified user or department using version 4.1 of the API.
- Get Leave by IDRetrieves a leave record by its ID.
- Get Leave Type by IDRetrieves a leave type by its ID.
- Get My LeaveRetrieves leave details for a specific user.
Explore alternative integrations
There are other apps [9] supported by WEXTL that can be paired with BrioHR and WhosOff integrations. Pick any from the list below if the current combination isn't the one you need.
Frequently asked questions
Common questions about connecting BrioHR and WhosOff.
Connect your BrioHR and WhosOff accounts once, pick an action in one app and an action in the other, then map the fields so data flows automatically between them. [3]
Example: use BrioHR's "Create a Claim Report" action to perform WhosOff's "Approve or Decline Leave" action. BrioHR has 7 actions (including Create a Claim Report, Get Employee Details, and Get Leave Summaries); WhosOff has 77 actions (including Approve or Decline Leave, Approve Overtime, and Cancel Leave). Add filters and transforms between steps when you need them. [1]
Yes — pick an action in either app, then an action in the other, and map the fields between them. [2]
No. BrioHR-to-WhosOff automations are built visually on the canvas. You can optionally add custom JavaScript with Functions when you need advanced logic. [4]
Yes. Trigger-based automations start the moment BrioHR (or WhosOff) fires a new event — webhook-backed apps run within seconds, and polling-only apps re-check on a schedule you control. [7]
A first automation typically takes 5–10 minutes: connect each app's credential once, drop a trigger + action onto the canvas, map the fields, and turn the workflow on.
You can build your BrioHR + WhosOff automation on a 3-day trial with every feature unlocked. Cancel anytime. For your protection, a small deposit is charged to your card when your trial starts. It counts toward your first payment and is non-refundable. [8]
References
List of sources used to gather information about the BrioHR and WhosOff integration.
- BrioHR and WhosOff integration source code, module specs and credentials implementation.
- Our BrioHR and WhosOff integration documentation, structured input and output parameters, scopes, and authentication methods.
- Official vendor API documentation for BrioHR and WhosOff — used to verify field meanings, authentication flows, and anything our own specs don't fully capture.
- WEXTL® visual workflow builder, anonymized data from our technical support team.
- BrioHR integration information
- WhosOff integration information
- WEXTL® Scheduling
- WEXTL® Pricing and Trial
- WEXTL® Apps Library