Integration directory
Kamana logo
Recruiting and ATS•Limited availability

Kamana

Show the depth of the healthcare staffing data model Teambridge has connected for one Kamana implementation while clearly separating that proof from general availability.

Connection at a glance

Kamana logoKamana
TeambridgeTeambridge

Configured data movement between Kamana and Teambridge for one implementation.

How it works

How Teambridge connects with Kamana

The integration supports a deep healthcare staffing model covering talent, facilities, jobs, contracts, credentials, work history, medical history, and documents.

Both inbound and outbound production flows are currently bound to one account, so this is not generally available.

Verified data movement

What moves, where, and when

01
KamanaTeambridgeWebhook

Configured talent, facility, job, contract, credential, and document changes enter one implementation.

02
TeambridgeKamanaDomain event

Worker, placement, and document changes can return to Kamana for that same implementation.

03
KamanaTeambridgeFile transfer

Credential and profile documents can move with their related records.

What the connection supports

  • Twenty four mapped collection types
  • Talent and placement synchronization
  • Credential and document data
  • File attachment transfer
  • Webhook driven inbound updates

Scope and limitations

  • Current production data flow is single account
  • Other accounts do not receive a working sync
  • Do not market as generally available

Operational use cases

Where Kamana fits in the work

The connection matters when it removes a specific handoff without losing the worker, customer, job, approval, or document context behind it.

01

Connect the traveler profile

Map talent identity, work history, references, degrees, licenses, and medical history.

02

Carry staffing relationships

Connect facilities, clients, jobs, contracts, engagements, and placements.

03

Move credential documents

Transfer configured document types and their file attachments in both directions.

Implementation path

Set up the connection around one verified outcome

Configuration varies by account and system. These steps establish the minimum path Teambridge should validate before the connection is trusted in production.

  1. 1

    Confirm eligibility

    Teambridge engineering reviews whether a new implementation can be supported.

  2. 2

    Map the data model

    Select from the twenty four supported Kamana collection types and define sync order.

  3. 3

    Configure account routing

    Implement and verify the account specific webhook and outbound event routing.

  4. 4

    Validate files and records

    Test both structured data and document attachment movement before launch.

Questions and answers

What teams ask about Kamana

What does the Kamana integration with Teambridge do?+

Support configured healthcare talent, credential, and placement workflows for selected implementations. Show the depth of the healthcare staffing data model Teambridge has connected for one Kamana implementation while clearly separating that proof from general availability.

What data moves between Kamana and Teambridge?+

Configured data movement between Kamana and Teambridge for one implementation.

How do you set up the Kamana integration?+

Requires a Teambridge engineering review, account enablement, credentials, collection mapping, and implementation specific validation.

Is the Kamana integration generally available?+

The shipped capability is limited to selected implementations or has a material scope boundary. The most important current boundary is: Current production data flow is single account.

Related integrations

Bullhorn logo

Bullhorn

Self serve

Sync ATS entities on a near real time polling cycle and create candidates from Teambridge.

Job Robotix logo

Job Robotix

Self serve

Sync jobs into Teambridge daily or by webhook. Candidates and placements are not included.

SmartRecruiters logo

SmartRecruiters

Limited availability

Support a configured hired candidate and onboarding status workflow for selected implementations.

Get started