Qualiobee Make integrationAutomate Qualiobee with Make.

Create Convocation produces the convocation that tells a learner to attend, straight from your scenario. Nobody has to open Qualiobee and fill the form each time a place is confirmed.

Create Customer opens a new customer account in Qualiobee from data that already lives elsewhere, typically a company that just signed. Your sales pipeline and your training records then start from the same details.

Create Formation adds a new training program to your Qualiobee catalog. It saves rebuilding the same course sheet by hand when the content is already written in another tool.

Create Learner registers a person as a learner in Qualiobee, filled with the data your form or CRM already collected. It is the module behind most enrollment scenarios, and the one used in the first scenario above.

Create Location records a new venue in Qualiobee, the place where sessions will take place. Adding it from a scenario keeps your list of rooms and addresses in line with the one your logistics team maintains elsewhere.

Create Module adds one of Qualiobee's own modules, a record of the app that has nothing to do with the modules of a Make scenario. The naming clash is worth remembering when you read the editor, as both words appear side by side.

Create Session schedules a new learning session in Qualiobee, the actual run of a program that learners will attend. From Make, it lets a planning decision taken elsewhere turn into a bookable session without double entry.

Create Session Date adds one date to an existing learning session, so a multi-day program gets its calendar filled in from your scenario. Each bundle that reaches it produces one date.

Create Trainer adds a trainer profile to Qualiobee, so the person can be assigned to sessions as soon as their contract is signed. It spares the admin team a second round of typing.

Custom request is the universal module of the Qualiobee app, the one to reach for when no named module covers what you need. It stays inside your existing connection, so you do not set up a second link.

Delete Convocation removes a convocation from Qualiobee, which keeps your records clean when a learner drops out and the notice should no longer stand. The scenario does it for you once the cancellation is recorded elsewhere.

Delete Customer takes a customer account out of Qualiobee. Most teams use it rarely, when a duplicate needs to go or a client record created by mistake must disappear from lists and reports.

Delete Formation removes a whole training program from the Qualiobee catalog, which makes it the heaviest delete on this page and rarely the right tool for everyday cleanup.

Delete Learner erases a learner record from Qualiobee, for instance after a request to remove someone's data that arrives through your support desk. The scenario carries out the removal, so nobody has to open Qualiobee.

Delete Location drops a venue from Qualiobee so that nobody schedules a session in a room you no longer use. It keeps the location picker short and current.

Delete Module removes one of Qualiobee's own modules, the app record, not a brick of your Make scenario. Keep that distinction in mind: this step deletes data in Qualiobee, it does not tidy up the editor.

Delete Session cancels a learning session in Qualiobee by removing it entirely. It fits scenarios that react to a cancellation decided in another tool, so the session stops showing up anywhere.

Delete Session Date removes one day from a session's calendar while the session itself stays in place. It is the precise tool when a single date is dropped rather than the whole program.

Delete Trainer removes a trainer profile from Qualiobee. Use it with care: it is meant for profiles that should never have existed, such as a duplicate or a test entry, more than for trainers who simply stop working with you.

Update Convention edits an existing convention, the training agreement stored in Qualiobee. It is the only way this app lets Make write to conventions: there is no module to create or delete one.

Update Convocation corrects a convocation that already exists instead of deleting and recreating it. The learner's history stays in one record while the details change.

Update Customer keeps a Qualiobee customer in step with the version your sales or billing tool holds. When a client's details change there, Make writes the change here.

Update Formation edits a program already in your Qualiobee catalog, so a change approved elsewhere reaches Qualiobee without a second edit.

Update Learner changes the details of a learner who already exists in Qualiobee. It spares you a new record each time a learner's contact details move.

Update Location edits a venue that Qualiobee already knows, so sessions keep pointing to the same place while its details change. A moved entrance or a new room name no longer means a new record.

Update Module edits one of Qualiobee's own modules, the app record, as opposed to a brick of the Make editor. It lets content revised in another tool land on the existing record rather than a copy.

Update Session edits a learning session that is already planned. Changes decided in your planning tool reach Qualiobee without anyone reopening the session by hand.

Update Session Date moves or corrects a single date of a session, while the other days of the same session stay untouched. It is the right grain when only one day shifts.

Update Trainer refreshes a trainer profile in Qualiobee with the details held in your HR tool or a trainer form. The profile stays the same record, so past sessions keep their link to it.

Fetch many Convention lists training agreements from Qualiobee, each one arriving as a separate bundle. It turns your conventions into rows you can send to a report or loop through with other modules.

Fetch many Convocation retrieves a batch of convocations so you can check, export or act on them together. It suits follow-up work more than the moment a convocation is issued.

Fetch many Customer returns the customer accounts held in Qualiobee, ready to compare with your CRM or to copy into a sheet. It is also the check that prevents a second account for a company you already serve.

Fetch many Formation pulls your training programs out of Qualiobee, one bundle per program. With it, a website page, a price list or a catalog export can be rebuilt from the source instead of retyped.

Fetch many Learner searches the learners in Qualiobee and hands each match to the next module. It answers the question every enrollment scenario should ask first: is this person already in the system?

Fetch many Location lists the venues stored in Qualiobee. It gives your logistics team a live view of rooms and addresses and gives your scenarios a way to find a venue's UUID by its name.

Fetch many Module retrieves Qualiobee's own modules, the content records of the app, not the bricks of your scenario. Use it to inventory what exists before creating or editing anything.

Fetch many Session returns the learning sessions planned in Qualiobee. It is the base for any overview of upcoming intakes, whether that lands in a sheet, a dashboard or a message to the team.

Fetch many SessionDate lists the individual dates of learning sessions, the level at which a calendar actually works. Each date comes out as its own bundle, ready to become a calendar event elsewhere.

Fetch many Trainer brings back the trainer profiles held in Qualiobee. A staffing sheet, a directory or a check for duplicates can then be built from the same source your admin team maintains.

Fetch one Convention reads a single training agreement from its UUID and returns its full details. It is precise where Fetch many Convention is broad: one identifier in, one record out.

Fetch one Convocation reads one specific convocation in Qualiobee from its UUID and hands it to the next module. You work on its current content, not on an old copy.

Fetch one Customer gives your scenario one customer record from Qualiobee, found by UUID, so the modules after it reuse that client's data without retyping it.

Fetch one Formation brings one program from your Qualiobee catalog into the scenario, located through its UUID and ready to map further down.

Fetch one Learner retrieves one learner's record from Qualiobee with its UUID, so what Qualiobee stores on that trainee can feed the rest of the flow.

Fetch one Location returns one training venue, identified by its UUID. Later steps can then name the place instead of leaving it blank.

Fetch one Module reads a single Qualiobee module by UUID. Here module means a record inside Qualiobee, not a Make module, and the scenario can read it before acting.

Fetch one Session returns the Qualiobee session that matches a UUID, as a bundle the following steps can map freely.

Fetch one SessionDate reads one precise date of a learning session by its UUID, which keeps a reminder or a calendar entry anchored to the right day.

Fetch one Trainer gets a single trainer back from Qualiobee, looked up by UUID, so their details can travel to an email, a sheet or another app.