Skip to main content

​
Prerequisites

The connector should already be set up, with a Connector Profile and a Linked Account. See Getting Started on the Teamtailor connector page.

​
Copy your Native Webhook URL

The Native Webhook URL is generated once a Teamtailor account has been linked in StackOne. Teamtailor sends every webhook event to this URL.

  • Open the linked account in StackOne.
  • Copy the value from Native Webhook URL.
  • Treat this URL as a secret. Anyone holding it can post events to your account.

​
Creating the webhook in Teamtailor

Teamtailor webhooks are created in the Teamtailor settings. One webhook covers every event you tick, across the whole company.

1

Activate the Webhooks add-on

Sign in to your Teamtailor account. If Webhooks does not appear under Integrations in the settings menu, activate the add-on first.

  • Open Settings and go to Add-ons > Activated add-ons.
  • Click Activate add-ons and find Webhooks (category Enterprise, type Free).
  • Activate the add-on.
2

Open the Webhooks settings

In Settings, scroll to Integrations and click Webhooks.

Teamtailor settings menu with Webhooks highlighted under Integrations.
3

Create a new webhook

Click Create new (or Create new webhook when webhooks already exist).

Empty Teamtailor Webhooks page with the Create new button highlighted.
4

Enter the label and Webhook URL

Fill in the top of the New Webhook form.

  • Label: a name you will recognize, such as StackOne.
  • Webhook URL: paste the Native Webhook URL you copied from StackOne.
New Webhook form with the Label and Webhook URL fields highlighted and the URL value hidden.
5

Select the events

Under Subscriptions, tick create, update and destroy for each resource whose events you enabled in StackOne (AuditEvent, Candidate, JobApplication, Job, User).

Subscriptions column of the New Webhook form with create, update and destroy ticked for every resource.
6

Choose the signature version and save

Under Signature version, select v2 (Teamtailor recommends v2 over the deprecated v1), then click Save.

Signature version options with v2 selected and the Save button highlighted.
7

Confirm the webhook was created

The webhook now appears in the list with its Webhook ID, Label and Signature key. Click Copy signature key if you want to verify the TT-Signature header on your side. StackOne does not verify the signature.

Teamtailor Webhooks list showing the new webhook with the Webhook ID and Copy signature key button highlighted and the key hidden.

​
Available webhook events

The following Teamtailor events can be handled. Only events ticked in the Teamtailor webhook and enabled in StackOne are delivered.

1

Candidate events

Events related to candidates.

  • Candidate Created (candidate.create) — Fired when a new candidate is created
  • Candidate Updated (candidate.update) — Fired when a candidate’s email, name, phone, pitch, LinkedIn URL, picture, referring site or URL, internal flag, restriction, custom fields or locations change
  • Candidate Deleted (candidate.destroy) — Fired when a candidate is deleted
2

Job events

Events related to jobs.

  • Job Created (job.create) — Fired when a new job is created
  • Job Updated (job.update) — Fired when a job’s title, body, pitch, status, employment details, salary, dates, recruiter, owner, department, role, tags, custom fields, locations or team memberships change
  • Job Deleted (job.destroy) — Fired when a job is deleted
3

Job application events

Events related to job applications.

  • Job Application Created (job_application.create) — Fired when a new application is submitted
  • Job Application Updated (job_application.update) — Fired when an application’s stage, rejection, cover letter, job title or promotion changes
  • Job Application Deleted (job_application.destroy) — Fired when an application is deleted
4

User events

Events related to Teamtailor users (recruiters, hiring managers and admins).

  • User Created (user.create) — Fired when a new user is added to the company
  • User Updated (user.update) — Fired when a user is updated
  • User Deleted (user.destroy) — Fired when a user is deleted
5

Audit events

Events related to the company audit log.

  • Audit Event Created (audit_event.create) — Fired when a new audit log entry is recorded
  • Audit Event Updated (audit_event.update) — Fired when an audit log entry is updated
  • Audit Event Deleted (audit_event.destroy) — Fired when an audit log entry is deleted

​
Delivery format

Details of how Teamtailor delivers events to StackOne.

1

One event per request

Each request carries a single event as a flat JSON object: event_name, the resource id, company_uuid and the resource fields in snake_case (for example updated_at). The signature is sent in the TT-Signature header. The event ID is the Teamtailor ID of the affected record (candidate, job, application, user or audit event).

2

No retries

Teamtailor does not retry a delivery that fails. Events sent while the webhook URL is unreachable are lost.

​
Verify

Your Connector should now be able to receive and process events. Try triggering an event and you should see an Event appear in the Connector logs.