Partner: Week29 for Teamtailor

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 requirement text of the role being recruited for. The recruiter gets an ordered shortlist, and where the candidate's text supports a requirement, the card quotes the passage.

How the integration works

1. A company admin activates Week29 from the Teamtailor Marketplace and enters a Teamtailor Admin API key during activation.
2. Week29 reads the candidate base through the Teamtailor API and builds a searchable index of it. Candidates are read together with their pitch, Teamtailor's CV summary and the CV file.
3. 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. Only the trigger carries a job, so only the trigger gives a match level.
4. When the candidate arrives from a trigger, Week29 ranks the candidate against that job and writes the result back to Teamtailor: a match level on the candidate card as a partner result, and a tag. Nothing numeric is written.
5. 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. 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, and never writes one to Teamtailor. Match levels are qualitative: strong, good and possible match.

Teamtailor stays the master system. The match level Week29 writes, as a partner result and a tag, stays in Teamtailor even if the integration is deactivated later. The ranked list and the evidence live in the Week29 panel.

2. How to enable the integration

Before activating, contact hello@week29.se so Week29 can set up the account's dedicated EU instance. Activation is done together with Week29, and activating before the instance exists has no effect.

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

1. In Teamtailor, go to Settings.
2. Open Integrations, then API keys.
3. 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 back to the candidate card.
4. Copy the key. Teamtailor shows the value once.

The key can be revoked at any time from the same page. Revoking the key stops Week29 from reading the base and writing tags. To stop all processing, deactivate the integration.

Step 2. Activate Week29

1. In Teamtailor, open Marketplace.
2. Find Week29.
3. Click Activate.
4. Fill in the activation form. Admin API key (required): paste the key from step 1, the field is masked. Tag prefix (optional): the first part of the tag Week29 writes on the candidate card. The default is week29, which produces the tags week29:stark, week29:god and week29:mojlig (the Swedish level names for strong, good and possible match, written without diacritics so they work in tag filters). Field mapping (optional): map or let Teamtailor create Available from (date) and Notice period (select). Week29 uses them only to show availability.
5. 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

A trigger on a job stage gives a match level and a tag on the candidate card. Bulk select only indexes the candidates. Both can be used in the same account.

A trigger on a stage:

1. Open a job, then Triggers.
2. Click Add trigger on the stage where candidates should be ranked.
3. Choose Send to Week29.
4. Save. Every candidate who reaches that stage is now sent to Week29 automatically.

Bulk select:

1. Open a candidate list.
2. Select the candidates to rank.
3. Choose Send to Week29 in the bulk action menu.

Bulk select sends candidates to Week29 for indexing. A bulk action carries no job, so Week29 returns a partner result without a match level and writes no tag. Use a trigger on a job stage to get a match level on the card.

What happens next

A candidate sent by a trigger is ranked against that job, by comparing the candidate to the role's requirement text across the whole indexed base. 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 Swedish.

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 sent from Week29 to Teamtailor

Week29 writes the result back to the candidate card as a partner result with a qualitative match level. Teamtailor displays it with one of its own three grades, and the summary of the result states Week29's level in plain Swedish: Stark, God or Möjlig match, for strong, good and possible match. Week29 also writes a tag, week29:<level>, so the result can be filtered in Teamtailor. Nothing numeric is written: no score, no percentage and no ranking position ever reaches the Teamtailor account.

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, the candidate is deleted from Week29 within 24 hours. When the integration is deactivated, all candidate data for the account is deleted. Tags and partner results 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.

Candidate not yet indexed. A candidate created moments ago may reach Week29 before the candidate has been read and indexed, and then gets no result. If the candidate was added very recently, send it again after 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