1. Introduction to Week29
Week29 ranks a company's existing Teamtailor candidate base against a specific role and presents the strongest candidates with evidence taken from each candidate's own material.
Most Teamtailor accounts hold thousands of candidates who applied once and were never revisited. Week29 reads all of them, including the text inside their CVs, and ranks them against the requirements of the role being recruited for. The recruiter gets an ordered shortlist where every candidate carries a short quote from their own profile or CV showing why the candidate came up.
How the integration works
- A company admin activates Week29 from the Teamtailor Marketplace and enters a Teamtailor Admin API key during activation.
- Week29 reads the candidate base through the Teamtailor API and builds a searchable index of it. Candidates are read together with their work history and CV text.
- A candidate is sent to Week29 either by a trigger on a stage in a job, or by selecting candidates in a list and using the bulk action.
- Week29 ranks the candidate against the role and writes the result back to Teamtailor: a match level on the candidate card as a partner result, a tag, and, when a numeric field has been chosen, a score in that field.
- The full view, with the ranked list, the evidence per candidate and the comparison table, opens in the Week29 panel through a link from the candidate card.
The integration uses two Teamtailor APIs. The Public API, with the customer's Admin key, reads the candidate base and writes the tag and the optional score. The Partner API receives the candidates sent by a trigger or a bulk action and returns the match level as a partner result on the candidate card.
What Week29 does not do
- Week29 never contacts a candidate. No email, no message, no candidate account.
- Week29 never rejects, archives or moves a candidate on its own. A recruiter takes every action, with a click.
- Week29 never shows a percentage or a numeric score to the recruiter. Match levels are qualitative: strong, good and possible match.
Teamtailor stays the master system. Every result Week29 produces is written back into Teamtailor, so the work remains in Teamtailor even if the integration is deactivated later.
2. How to enable the integration
Requirement: company admin. Activating a Marketplace integration and creating an API key both require company admin rights in Teamtailor. A user without those rights cannot complete these steps.
Step 1. Create a Teamtailor Admin API key
- In Teamtailor, go to Settings.
- Open Integrations, then API keys.
- Create a new API key with scope Admin and both read and write enabled. Read access lets Week29 read the candidate base including CVs. Write access lets Week29 write the tag and the score back to the candidate card.
- Copy the key. Teamtailor shows the value once.
The key can be revoked at any time from the same page. Revoking it stops Week29 from reading or writing immediately.
Step 2. Activate Week29
- In Teamtailor, open Marketplace.
- Find Week29.
- Click Activate.
- Fill in the activation form. Admin API key (required): paste the key from step 1, the field is masked. Score field (optional): the numeric custom field on candidates that Week29 writes the match score to; leave it empty to use only the match level and the tag. The field is created in Teamtailor under Settings, Custom fields, as a Number field on Candidate. Tag prefix (optional): the first part of the tag Week29 writes on the candidate card. The default is guldkorn, which produces the tags guldkorn:stark, guldkorn:god and guldkorn:mojlig (the Swedish level names for strong, good and possible match, written without diacritics so they work in tag filters).
- Save.
The activation form also links to this article, so the key can be created without leaving the flow.
Step 3. Send candidates to Week29
Either of the two ways below works, and both can be used in the same account.
A trigger on a stage:
- Open a job, then Triggers.
- Click Add trigger on the stage where candidates should be ranked.
- Choose Send to Week29.
- Save. Every candidate who reaches that stage is now sent to Week29 automatically.
Bulk select:
- Open a candidate list.
- Select the candidates to rank.
- Choose Send to Week29 in the bulk action menu.
What happens next
The candidate is sent to Week29, which ranks that candidate against the role by reading the whole indexed base and comparing the candidate to the requirements of the role. Within a short time, the candidate card in Teamtailor shows the partner result and the tag. Teamtailor labels the partner result with one of its own three grades, and the summary of the result states Week29's level in plain words. If a score field was chosen, the numeric score appears in that field, which makes the base sortable in Teamtailor.
The full view, with the ranked list for the role, the evidence per candidate and the comparison between candidates, opens in the Week29 panel through the link on the partner result.
3. Details regarding the integration
Data sent from Teamtailor to Week29
| Data | Purpose |
|---|---|
| Candidate profile fields (name, email, phone, location, links) | Identifying and displaying the candidate in the panel |
| Work history and education | Ranking the candidate against the requirements of the role |
| CV text and CV files | Ranking, and quoting evidence from the candidate's own material |
| Job title and stage | Knowing which role the candidate is ranked against |
| Tags | Ranking, and avoiding writing a tag that already exists |
| Custom fields on the candidate | Ranking, and writing the score to the field chosen at activation |
| Company id | Separating one customer's data from another's |
Data sent from Week29 to Teamtailor
| Data | Purpose |
|---|---|
| Match level as a partner result | Showing the result on the candidate card. Teamtailor displays a partner result with one of its own three grades: top fit, might be a fit or might not be a fit. Week29's own level is stated in plain words in the summary of the result (Stark, God or Möjlig match, Swedish for strong, good and possible match) and in the tag. |
| Tag with the chosen prefix and the level, for example guldkorn:stark | Making the result filterable in Teamtailor |
| Numeric score in the chosen custom field (optional) | Making the base sortable in Teamtailor |
Direction, storage and deletion
- Direction. Candidate data flows from Teamtailor to Week29. Results flow from Week29 back to Teamtailor. Week29 writes nothing else into the Teamtailor account.
- Purpose. The data is used only to rank the customer's own candidates for the customer's own roles. It is never used for another customer, and no models are trained on it.
- Storage. Candidate data is stored in the EU, on infrastructure in Frankfurt. All model calls are made within the EU. Week29 acts as a processor on behalf of the customer, who remains the controller.
- Deletion. When a candidate is deleted in Teamtailor, that candidate and every trace of the candidate is deleted in Week29 as well. When the integration is deactivated, all candidate data for the account is deleted. Tags and scores already written into Teamtailor stay in Teamtailor, because that work belongs to the customer.
4. Support
Contact
Questions about Week29, including pricing, go to hello@week29.se. Questions about Teamtailor itself go to Teamtailor support.
Common errors and how to solve them
Invalid API key. The key was mistyped, has been revoked, or does not have scope Admin with both read and write. Create a new key in Settings, Integrations, API keys, then open the Week29 activation in the Marketplace and paste the new key.
No score field selected. The activation was saved without a score field, so the match level and the tag are written but no number appears on the candidate card. Create a Number custom field on Candidate in Teamtailor under Settings, Custom fields, then reopen the activation and select it. Match levels work without a score field, so this is optional.
Candidate not yet indexed. A candidate created moments ago may reach Week29 before the candidate has been read and indexed. The candidate is ranked as soon as indexing finishes, which normally takes a few minutes. The first read of an entire candidate base takes longer, from a few minutes up to several hours for a large base with CVs, and the panel shows the progress while it runs.
The tag is not visible yet. Teamtailor indexes tags asynchronously, so a newly written tag can take a while to appear in filters and lists even though it is already on the candidate. Reload the candidate card, and give the filter a few minutes.
FAQ
Does Week29 make decisions about candidates? No. Week29 ranks candidates and presents evidence. It cannot reject, archive or move a candidate. Every action is proposed to the recruiter and carried out only when the recruiter confirms it with a click, and that boundary is enforced in code, not by an instruction to a model.
Does Week29 contact candidates? No. Week29 sends no email and no message to candidates, and candidates have no account and see nothing of the product. All candidate communication stays in Teamtailor.
Where is the data processed? In the EU. Candidate data is stored in Frankfurt and all model calls are made within the EU.
Is a percentage shown anywhere? Not to the recruiter. The interface shows qualitative levels only: strong, good and possible match. A numeric score is written to Teamtailor only if the customer chooses a score field, so that the base can be sorted.
What happens to the results if the integration is deactivated? Tags, scores and partner results already written stay in Teamtailor. Candidate data held by Week29 is deleted.