Oleeo and QGenda Integration

Demonstration of how apps are integrated in WEXTL workflow builder[4]

Keep Oleeo and QGenda matched by integrating their events and actions. When hr events happen in Oleeo, update the QGenda automatically - without any line of code in visual workflow builder.

  • 3-day trial
  • Cancel anytime
  • Up to 10 minutes quick set up
  • GDPR
  • Data Encryption
  • 2FA
  • Local Data Region

Learn about Oleeo and QGenda

Detailed info you need to know about Oleeo and QGenda integrations in WEXTL. Explore which modules apps support and how you connect them.

  • Oleeo

    • HR
    • 16 triggers
    • 39 searches
    • 23 actions

    Manage vacancies, candidates, applications and messages in the Oleeo recruiting platform.[5]

  • QGenda

    • HR
    • 2 triggers
    • 19 searches
    • 29 actions

    Medical staff scheduling and workforce analytics for healthcare organizations.[6]

How to connect Oleeo to QGenda

Set up your Oleeo and QGenda integration in 3 simple steps[2]. No coding required. Up to 10 minutes setup.

How does the integration between Oleeo and QGenda work in WEXTL?

WEXTL exposes actions and triggers for Oleeo and QGenda that help you connect apps and automate repetitive tasks[1]. A trigger is an event that happens, and an action is a step that performs when the event has occurred.

Oleeo triggersQGenda actions

Oleeo modules

  • Add an Application Comment Posts a Comment under an application of a given Application type. Use Parent Comment ID to reply to an earlier comment and Comment Type to set the numeric type.
  • Create a Candidate Registers a person from a Candidate URI, Given Name and Family Name. Add an Email, Phone, Address, Position History or Attachment to build out the profile.
  • Create a Contact Adds a user as a contact on an event under a Role Profile ID. Turn on Is Coordinator or Can View Applications, or set a Contact Category ID.
  • Create a Message Stores a Message for a user and returns its ID and URL. Turn on Is active to flag it active.
  • Create a Notification Adds a notification topic with a Name and a Description, and returns its UUID, Type and Expression.
  • Create a Recruiter Adds a recruiter account from First name, Last name, Email and Username. Set Role profile ID or Category ID, and turn on SSO only to restrict sign-in to single sign-on.
  • Create a Registration Registers a candidate for an event. Use Process Entry Point to start at the event and Allow Duplicate to permit a second registration. Returns the Process state and Checked in.
  • Create a Vacancy Adds a vacancy under a Vacancy ID with a Position Title, Position URI and Apply URLs. Add Position Locations, Position Remuneration or a Publication Start Date as well.
  • Create an Anonymous Candidate Sets up an anonymous candidate using an Email, First name and Last name. The only output is the new ID.
  • Delete a Notification Deletes a notification topic from Oleeo.
  • Delete a Subscription Cancels one subscriber entry on a notification topic.
  • Delete a Vacancy Deletes a single vacancy record from Oleeo.
  • Get a Campaign Looks up a CRM campaign by its Campaign ID and shows it.
  • Get a Candidate Loads a candidate profile with its Given name, Family name, Date of birth and Gender.
  • Get a Job Board Pulls the Title and Description of a job board by its Job Board ID. Use Rich Text Format to switch rich text between raw BBCode and HTML.
  • Get a Message Returns the Message text of one message, along with its Is active flag.
  • Get a Notification Fetches Name, Description, Type and Expression of a notification topic. A saved Layout can be applied.
  • Get a Posting Retrieves a posting by Posting ID, including its Start dt, Closing dt, Apply URL and Status. Set Rich Text Format to receive BBCode or HTML.
  • Get a Recruiter Finds a recruiter by Recruiter User ID. Use Layout for a prepared layout and Rich Text Format for BBCode or HTML output.
  • Get a State Shows a process state by its State ID, with its Title, Applicant title, Is terminal flag and Display order.
  • Get a Subscription Opens a notification subscription to show its Destination URL, Start dt, End dt and Signing key.
  • Get a Vacancy Loads a vacancy by Vacancy ID, with its Position title, Position URI and Apply URI. A saved Layout can be applied.
  • Get an Administrator Loads one administrator user from Oleeo and returns it as a single record.
  • Get an Agent Fetches an agent user from Oleeo by its User ID.
  • Get an Application Opens an application of a given Application type. Use Layout to apply a saved layout and Rich text format to render rich text as raw BBCode or HTML. Returns Submitted dt, Process state and Votes.
  • Get an Application CV Downloads the CV that was filed with an application of the matching Application type. The output is the File.
  • Get an Application Letter Downloads the cover letter filed under an application of that Application type. The output is the File.
  • Get an Event Shows the Title and Positions total of an event, plus its Hiring target. Use Layout to apply a prepared layout and Rich Text Format for BBCode or HTML.
  • Get an Event Template Retrieves an event template and returns Is template and Is draft, with a saved layout applied through Layout.
  • List Administrators Returns administrator users with their Username, Email and Last login. Use Sort to order them, Search to match conditions, and Limit to cap the count.
  • List Agents Fetches agent users, each with a Username, Firstname, Lastname and Date registered. Narrow them with a Saved Search or a Filter.
  • List Application Comments Pulls the comments on one application of an Application type. Each has a Comment, a Date and a User. Use Limit to trim the list.
  • List Application Forms Browses the forms attached to an application of the selected Application type. Each shows its Form ID, its Creator and Editor, and when it was Submitted.
  • List Applications Retrieves applications of an App Type. Filter by Status Groups, Historical Status Groups, My Vote or Pinned, and turn on Include Anonymous Users to add anonymous data.
  • List Campaigns Shows campaigns with their Name, Description and Color, along with whether each is a Draft or Archived. Use Quick search to filter by quick-searchable attributes.
  • List Candidate Campaigns Lists the campaigns of a candidate user, returning each ID and Name. Use Limit to keep the list short.
  • List Candidate Comments Gathers the comments about a candidate user, each with its Comment, Date and User. Use Limit to hold the list to a set length.
  • List Candidate Messages Collects the messages stored for a candidate user, each with its Message and Is active value. Use Sort to set the order and Search to narrow the result.
  • List Candidates Retrieves candidate profiles, each with a Given name, Family name and Date of birth. Turn on Anonymous users to include anonymous profiles, or use Quick search to filter.
  • List Event Contacts Returns the contacts of one event with their Roleprofile ID and Is coordinator value. Use Limit to shorten the list.
  • List Event Registrations Lists who registered for an event, with Process state and Checked in. Set Preregistered to keep registrations made before the event, or use Checked In to select by check-in state.
  • List Event Templates Fetches event templates with their Title and Hiring target. Use Now to sort by the start date closest to now, which cannot be combined with page or Sort.
  • List Events Browses events, each with a Title, Is active and Is archived. Use Now to put the start date closest to today first, or Selection to filter by a stored selection.
  • List Job Adverts Queries job adverts of one Job board type. Set a Language locale for the request, and leave Translation ID empty to get the API default of 3 for lookup values.
  • List Job Boards Returns job boards of one JobBoard type, each with a Title, URL and Description. Repeat Sort to order by several fields.
  • List Notifications Reads notification topics with their Name, Type and Expression. Use Config Search to apply a config saved search by its ID.
  • List Postings Pulls postings with a Start dt, Closing dt and Status. Use Saved Search to apply a stored filter, or Layout Only to return just the layout rows.
  • List Recruiters Retrieves recruiter users, each with a Username, Email and Last login. Use Search to combine conditions with AND and Limit to cut the list.
  • List States Lists process states with their Title, Applicant title and Display order. Filter with Process ID, Is Terminal or Is Deprecated, or turn on Fetch Status Groups to add status groups.
  • List Subscriptions Shows the subscriptions that belong to a notification topic, each with a Destination URL and Signing key. Use Selection to filter by a stored selection.

QGenda modules

  • Assign a Staff Member to a Location Places a staff member at a location with their credential status. Set Is Credentialed, Is Enrolled or Is Pending as needed, and add Start Date, End Date and Inactive Date to time-box the credential or record a termination.
  • Create a Contact Saves a credentialing contact for a Workforce company from a Name. Use Preferred Contact Method to choose between Email, Other Email, Phone, Work Phone or Mobile Phone, and the address fields to store a postal address.
  • Create a Daily Case Logs a daily case for a facility, tied to a task through Task ID or Task Key. Set Surgeon and Procedure for the case details, and fill the Supervisor and Direct Provider staff fields to assign people.
  • Create a Location Sets up a location from an ID and a Name. Use Address, Time Zone and Abbreviation to describe where it is, and Tags in Category:Name format to categorize it.
  • Create a Location Tag Labels a location with a tag made of a Category and a Name.
  • Create a Location Task Links an existing task to a location. Turn on Is Credentialed to flag the pairing as credentialed.
  • Create a Patient Encounter Records a patient encounter starting at Start DateTime. Add End DateTime or Duration, plus Assignments to place staff on encounter roles.
  • Create a Staff Member Registers a staff member using a Staff ID plus profile, contact and payroll fields. Turn on Update If Existing to match an existing record on NPI, billing system ID, staff ID or email. Omitted names default to CHANGEME.
  • Create a Task Defines a task with Task ID and weekday flags covering Sunday through Saturday, at least one of them on. Use Type to make it a Working or an Unavailable task, and Start Date and End Date to bound it.
  • Create a Task Tag Applies a tag to a task, supplying both the Category and the Name. Use Effective Date to set the first day of the range in which the tag applies.
  • Create a Time Event Captures a time punch beginning at Actual Clock In in UTC, optionally closed with Actual Clock Out. Add Task ID or Task Key to link a task, plus Staff Key, Staff ID or Staff Payroll ID to link a person.
  • Delete a Contact Association Removes a payer or location association from a credentialing contact. Set Association Type to payer or location, and add Payer Name for a payer or Location ID for a location.
  • Delete a Daily Case Deletes a daily case record from a company.
  • Delete a Location Removes a location entry under a company.
  • Delete a Location Tag Detaches the tag matching a Category and Name from a location.
  • Delete a Location Task Deletes the link between a task and its location.
  • Delete a Patient Encounter Deletes a patient encounter record at a facility.
  • Delete a Staff Member Deletes a staff member from QGenda. Supply Company Key or Location ID to say which company the staff belongs to.
  • Delete a Task Tag Unlinks a tag from the task, within a given Category. Add Name to target a single tag in that category.
  • Get a Daily Configuration by Key Fetches one daily configuration with its Name, Encounter fields and Encounter phi fields.
  • Get a Schedule Audit Log Reads the audit log for a company, starting at Schedule Start Date and ending at Schedule End Date. Each entry has its Activity type, Staff abbreviation and Schedule entry date.
  • Get a Staff Member Retrieves one staff member with their Email, Abbrev and End date. Use Includes to pull in related entities with the response.
  • Get Approved Requests Lists approved requests for a company between Start Date and End Date. Each request has its Request ID, Task ID, Call role and Credit.
  • Get Contacts Pulls the credentialing contacts of a Workforce company, with each Name, Contact key and Email. Use Limit to return fewer contacts in a run.
  • Get Daily Cases Returns daily cases from a Start Date onward, ending at an optional End Date. Each has its Surgeon, Date and Location name. Use $filter to narrow the rows with an OData expression.
  • Get Daily Configurations Reads the daily configurations set up for a company, each with its Name and Encounter roles. Pass an OData expression to Filter to narrow the list.
  • Get Location Tasks Shows the tasks linked to one location, one item per link, holding the Location and Task. Use Company Key to restrict the locations returned to one company.
  • Get Locations Lists locations with their Name, Address, Abbrev and Time zone. Use Includes to bring related entities along, or narrow and sort with Filter and Order By.
  • Get Open Shifts Looks up open shifts from a Start Date up to an optional End Date. Each one has its Open shift count, Call role and Credit.
  • Get Patient Encounters Gets patient encounters from Start Date to an optional End Date, including Encounter key, Daily case ID and Is cancelled values.
  • Get Requests Retrieves requests starting at Start Date. Turn on Include Removed to also see removed requests.
  • Get Room Assignments Shows room assignments by Date between Start Date and an optional End Date, each with its Rooms and Daily configuration key.
  • Get Rooms Reads the rooms of a company with their Room name, Room abbreviation, Location name and Room type.
  • Get Rotations Calculates rotations across the span of Range Start Date to Range End Date, each with its Start date, End date, Is published and Is locked. Turn on Ignore Weekend or Ignore Holiday to skip those days.
  • Get Schedules Pulls schedule entries from a Start Date, each with its Date, Staff abbrev and Task abbrev. Turn on Include Deletes to add deleted entries, and set Since Modified Timestamp to see only entries changed after it.
  • Get Staff Members Returns staff members with their Abbrev, Email and End date. Use Includes for related entities and $Filter, $OrderBy, $Select or $Expand for OData shaping.
  • Get Tasks Fetches tasks with their Abbrev, Call role and Department ID. Add Includes for related entities, or Select, Filter, Order By and Expand to shape the response.
  • Get Time Events Lists time punches for a company beginning at Start Date, with End Date as the last day. Use Pay Period to narrow the range to one pay period.
  • Make an API Call Runs a free-form request against the QGenda REST API using your saved credential.
  • Update a Contact Rewrites the Name, Title, Function, Email and phone details of a credentialing contact. Use Preferred Contact Method to change the preferred way of reaching them.
  • Update a Daily Case Revises a daily case, adjusting its Date, Surgeon, Procedure or times. Turn on Is Cancelled to cancel the case, and set Date Format to read dates written as dd/MM/yyyy.
  • Update a Location Changes the Name, Abbreviation, Address, Notes or Time Zone of a location, plus its General Ledger Code and Cost Center ID.
  • Update a Location Staff Assignment Changes a staff credential at a location with new pending, start and end values. Turn on Clear Inactive Date to remove the termination date.
  • Update a Location Task Changes how a location and task are paired. Use Is Credentialed to switch the credentialed flag on or off.
  • Update a Patient Encounter Amends a patient encounter, moving its Start Date Time, End Date Time, Duration or room. Turn on Retain Existing Field Values to clear or update only the fields you send, and Update External IDs to refresh the encounter External ID.
  • Update a Staff Member Changes the First Name, Last Name, Email and many profile fields of a staff member. Use Clear SSO ID or Clear End Date to blank those values, and Deactivation Date to schedule deactivation.
  • Update a Task Shift Edits a task shift from its Effective From Date, with new Start Time, End Time, Min Staff and Max Staff. Use Occurrence for when it repeats, and Is Active to switch it on.
  • Update a Time Event Edits a recorded time punch, changing Actual Clock In or Actual Clock Out, both in UTC. Use Is Struck to strike the event and Meal Break Override Label to override the meal break.
  • Watch Schedules Polls QGenda on a timer and emits each schedule entry it returns. Use Limit to cap how many entries one check handles.
  • Watch Tasks Checks QGenda on a schedule and runs the workflow for tasks that are new or updated since the last check.

Explore alternative integrations

There are other apps[9] supported by WEXTL that can be paired with Oleeo and QGenda integrations. Pick any from the list below if the current combination isn't the one you need.

Automate Oleeo and QGenda on WEXTL®

Claim your 3-day trial to build Oleeo with QGenda integration and access every WEXTL® feature.

Cancel anytime.

Frequently asked questions

Common questions about connecting Oleeo and QGenda.

How do I connect Oleeo and QGenda?

Connect your Oleeo and QGenda accounts once, pick a trigger in one app and an action in the other, then map the fields so data flows automatically between them.[3]

What can I automate between Oleeo and QGenda?

Example: when the "Watch Administrators" trigger in Oleeo fires, WEXTL can "Assign a Staff Member to a Location" in QGenda. Oleeo has 16 triggers (including Watch Administrators, Watch Agents, and Watch Application Comments). QGenda has 48 actions (including Assign a Staff Member to a Location, Create a Contact, and Create a Daily Case). Add filters and transforms between steps when you need them.[1]

Can Oleeo trigger actions in QGenda, and QGenda in Oleeo?

Yes. The integration works in both directions. Use the triggers of each app to start a workflow and the actions of the other app to update it.[2]

Do I need to write code to integrate Oleeo and QGenda?

No. Oleeo-to-QGenda automations are built visually on the canvas. You can optionally add custom JavaScript with Functions when you need advanced logic.[4]

Does Oleeo integrate with QGenda in real time?

Yes. Trigger-based automations start the moment Oleeo (or QGenda) fires a new event. Webhook-backed apps run within seconds, and polling-only apps re-check on a schedule you control.[7]

How long does it take to set up a Oleeo + QGenda integration?

A first automation typically takes 5–10 minutes: connect the credential of each app once, drop a trigger + action onto the canvas, map the fields, and turn the workflow on.

Do I need a paid plan to connect Oleeo with QGenda?

You can build your Oleeo + QGenda automation on a 3-day trial with every feature unlocked. Cancel anytime.[8]

References

List of sources used to gather information about the Oleeo and QGenda integration.

  1. Oleeo and QGenda integration source code, module specs and credentials implementation.
  2. Our Oleeo and QGenda integration documentation, structured input and output parameters, scopes, and authentication methods.
  3. Official vendor API documentation for Oleeo and QGenda, used to verify field meanings, authentication flows, and anything our own specs don't fully capture.
  4. WEXTL® visual workflow builder, anonymized data from our technical support team.
  5. Oleeo integration information
  6. QGenda integration information
  7. WEXTL® Scheduling
  8. WEXTL® Pricing and Trial
  9. WEXTL® Apps Library

How we write our apps documentation

Explore how WEXTL® crafted Oleeo and QGenda integration page documentation. Used sources, the role of AI, and how the team validates the result.

Explore Oleeo and QGenda, or get started