SmartRecruiters + Memtro

Only when you ask, and only what it has been granted: add tags to a candidate (existing tags are kept); record a 1 to 5 review of a candidate for a job, as a named reviewer; move a candidate to a new status on a job (rejection or hire may email them, per the account's automation); create a candidate, on a job or in the talent pool; correct a candidate's name, email, phone or location; delete a candidate, or their application to one job (permanent); create a draft job; change a job's status (sourcing, on hold, filled, cancelled...); publish a job to career pages and job aggregators, or unpublish it; replace a job's internal note; add a user to a job's hiring team, or remove them; schedule an interview for a candidate, or delete one made through the API. Every other tool reads, searches or lists. The Connections page labels the tools that act, an administrator grants each one by name to the teams that may use it, and a personal connection acts only after its owner allows it.

A personal connection serves only your own requests. A shared connection serves the organisation: everyone, or only the teams an admin chooses. Admins can always add shared connections; other members need the permission.

Credentials are encrypted at rest. Tool results are cached briefly so agent loops do not repeat identical calls, and the facts the model extracts are saved to your organisation's memory with provenance (system, record and link) so they can be checked and superseded.

API key. In SmartRecruiters open Settings → Administration → Credential Manager. Only a user with Administrator access can create a credential.

Yes. Turn events on in the connection's Events tab on the Connections page, choose the kinds you want, and Memtro registers its address with SmartRecruiters for you. A job set to start "When an event arrives" then runs once for each matching event, with the event as its input. The run treats the event as outside data, never as instructions, and anything the run remembers is kept as unverified.