Integration directory
SmartRecruiters logo
Recruiting and ATSLimited availability

SmartRecruiters

Document the hired candidate and onboarding flow that Teambridge operates for one configured SmartRecruiters implementation without presenting it as a universal connector.

Connection at a glance

SmartRecruiters logoSmartRecruiters
TeambridgeTeambridge

SmartRecruiters to Teambridge hired candidate. Teambridge to SmartRecruiters onboarding status.

How it works

How Teambridge connects with SmartRecruiters

The shipped workflow can create a Teambridge worker from a hired SmartRecruiters candidate and return onboarding status and tags.

The production implementation is bound to one account and should not be represented as a generally available connector.

Verified data movement

What moves, where, and when

01
SmartRecruitersTeambridgeWebhook

A hired candidate event retrieves candidate, property, job, and offer data for one configured account.

02
SmartRecruitersTeambridgeHourly

A scheduled process refreshes data for that same configured account.

03
TeambridgeSmartRecruitersOnboarding event

Completed onboarding can return status, candidate state, and tags.

What the connection supports

  • Hired candidate webhook
  • Candidate, job, offer, and property lookup
  • Onboarding status writeback
  • Implementation specific role and location matching

Scope and limitations

  • Current production workflow is single account
  • Other accounts can authenticate without receiving a working sync
  • No general collection mapping interface

Operational use cases

Where SmartRecruiters 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

Create a worker after hire

Turn the configured hired candidate event into a Teambridge worker record.

02

Resolve operating context

Use implementation specific matching for role, location, and job title.

03

Return onboarding state

Update SmartRecruiters after the worker completes the configured Teambridge onboarding path.

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 verifies whether a new account can be supported.

  2. 2

    Review account mappings

    Document roles, locations, properties, offers, and job fields used by the implementation.

  3. 3

    Configure authorization

    Connect the API key only after the account routing is implemented.

  4. 4

    Test both directions

    Validate candidate creation and onboarding status return before any launch.

Questions and answers

What teams ask about SmartRecruiters

What does the SmartRecruiters integration with Teambridge do?+

Support a configured hired candidate and onboarding status workflow for selected implementations. Document the hired candidate and onboarding flow that Teambridge operates for one configured SmartRecruiters implementation without presenting it as a universal connector.

What data moves between SmartRecruiters and Teambridge?+

SmartRecruiters to Teambridge hired candidate. Teambridge to SmartRecruiters onboarding status.

How do you set up the SmartRecruiters integration?+

Requires Teambridge engineering review and implementation specific account mapping. API authorization alone is not sufficient.

Is the SmartRecruiters 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 workflow is single account.

Get started