Meta tags:
description=Scenario outline Your company has a central database with information about employees. Name, email, the name of their manager and (often) a cost center. Specifics varies between organisations, but usually an Active Directory or payroll system will be the source of truth for employee data. You want t…;

Headings (most frequently used words):

integration, user, synchronisation, introduction, scenarios, when, things, go, awry, miscellaneous, scenario, outline, make, list, of, required, data, figure, out, where, it, at, write, the, code, scheduled, event, based, manager, changes, accidental, deletion,

Text of the page (most frequently used words):
the (35), skovik (18), and (12), you (10), for (10), manager (9), list (8), integration (7), scheduled (7), data (7), from (7), will (7), make (6), your (6), when (6), user (6), event (5), based (5), this (5), run (5), #synchronisation (5), that (5), employee (5), users (5), code (4), step (4), script (4), set (4), one (4), relevant (4), system (4), with (4), but (4), email (4), figure (3), out (3), required (3), scenario (3), employees (3), not (3), check (3), four (3), removed (3), should (3), error (3), may (3), all (3), during (3), are (3), new (3), changes (3), information (3), name (3), cost (3), guides (3), com (3), write (2), where (2), outline (2), sometimes (2), help (2), work (2), after (2), accidental (2), deletion (2), easy (2), flag (2), pulled (2), through (2), have (2), must (2), exist (2), integrations (2), consider (2), request (2), events (2), requests (2), lists (2), steps (2), two (2), each (2), update (2), these (2), extract (2), systems (2), every (2), hours (2), usually (2), recommend (2), approach (2), which (2), everything (2), place (2), multiple (2), need (2), want (2), center (2), changelog (2), api (2), reference (2), home (2), back (2), questions (2), protected (2), copy, page, while, can, recreate, deleted, involved, trivial, much, better, avoid, situation, altogether, would, above, percentage, modified, accounts, larger, than, terminate, report, small, cause, way, avoiding, such, include, sanity, solution, toggle, couldn, found, don, then, iterating, whole, trigger, immediate, case, was, guaranteed, present, changing, someone, keep, mind, most, common, type, yet, triggered, added, updated, appropriate, http, sure, emitted, 4th, effectively, synchronizing, ours, create, corresponding, desired, completed, memory, example, arrays, dicts, occur, group, add, remove, delete, put, post, iterate, compare, divide, into, groups, missing, needs, action, via, series, using, pagination, get, few, something, along, lines, itself, properties, say, both, equally, well, our, perspective, rare, contain, today, stored, could, either, pull, sources, adjust, internal, flows, available, determine, what, pieces, send, mandatory, almost, always, also, number, associated, business, spread, over, jurisdictions, legal, entity, employed, under, following, synchronise, colleague, joins, they, automatically, company, has, central, database, about, their, often, specifics, varies, between, organisations, active, directory, payroll, source, truth, powered, signed, receipt, links, identifying, single, sign, miscellaneous, asking, troubleshooting, things, awry, export, projects, centers, scenarios, first, introduction, jump, content, agents, visit, https, developer, llms, txt, index, pages, formatted, markdown, endpoints, openapi,

Text of the page (random words):
user synchronisation for ai agents visit https developer skovik com llms txt for an index of all pages formatted in markdown and endpoints in openapi jump to content home guides api reference changelog questions email protected back to skovik com guides questions email protected back to skovik com home guides api reference changelog user synchronisation introduction first step integration scenarios user synchronisation projects and cost centers data export when things go awry troubleshooting asking for help miscellaneous single sign on identifying users signed receipt links powered by user synchronisation scenario outline your company has a central database with information about employees name email the name of their manager and often a cost center specifics varies between organisations but usually an active directory or payroll system will be the source of truth for employee data you want to synchronise this data with skovik so that when a new colleague joins they will be set up in skovik automatically under this scenario we recommend the following approach 1 make a list of required data determine what pieces of information you ll need to send to skovik name and email is mandatory but you ll almost always also want to set the manager an employee number and an associated cost center if your business is spread over multiple jurisdictions you may need to consider which legal entity the employee is employed at 2 figure out where it s at figure out which systems contain this information today sometimes everything will be stored in one place but if not you could either a pull from multiple sources or b adjust internal data flows so that everything is available in one place 3 write the code the integration code itself will be event based when relevant properties for an employee changes or scheduled say every 3 hours both will work equally well from our perspective but event based integrations are rare we usually recommend the scheduled based approach scheduled integration the scheduled script will run every few hours and do something along these lines extract a list of users from your system or systems extract a list of users in skovik via a series of get requests using pagination iterate through the list from your system compare each user with the data in the list pulled from skovik and divide the users into four groups a missing in skovik b should be removed from skovik c needs an update in skovik d no action required for each group make the relevant post put delete request to add remove or update these users in skovik the steps 1 4 should all occur during one run of the scheduled script when steps 1 and 2 are completed you ll have two in memory lists for example two arrays of dicts during step 3 you ll create four new lists corresponding to the desired changes in skovik in the 4th step you ll make the relevant requests to skovik effectively synchronizing your system with ours event based integration when an event is triggered a user is added updated removed make the appropriate http request to skovik make sure that events will be emitted for the relevant events manager changes when changing someone s manager keep in mind that the manager must exist in skovik for scheduled integrations the most common type one must consider that the new manager for an employee may not exist in skovik yet an easy solution is to toggle a flag if the manager couldn t be found in the list pulled from skovik and don t set a manager then after iterating through the whole list check if the flag is set and trigger an immediate re run in case it was during this re run you are guaranteed to have the manager present accidental deletion a small error in your integration code may cause accidental deletion of all employees an easy way of avoiding such an error is to include a sanity check in the synchronisation script this check would run after step four above and if the percentage of removed or modified accounts is larger than 20 the script should terminate and report an error while we can sometimes help you recreate deleted employees the work involved is not trivial so it s much better to avoid the situation altogether copy page scenario outline 1 make a list of required data 2 figure out where it s at 3 write the code scheduled integration event based integration