Integration directory
Sense logo
Communications•Self serve

Sense

Keep the worker and staffing data used by Sense engagement current from Teambridge events without implying that messaging activity returns to Teambridge.

Connection at a glance

Sense logoSense
TeambridgeTeambridge

Teambridge to Sense only.

How it works

How Teambridge connects with Sense

Teambridge listens to worker, job, location, placement, shift, and contact changes and pushes the related records into Sense.

The connection keeps the audience data behind Sense engagement current, but Sense messaging activity does not return to Teambridge.

Verified data movement

What moves, where, and when

01
TeambridgeSenseDomain event

Candidate, contact, company, job, placement, and location changes trigger an immediate upsert.

02
TeambridgeSenseDelete event

Deleted Teambridge records propagate a soft delete flag to Sense.

03
TeambridgeSenseShift event

Configured shift and claim events can refresh related Sense staffing context.

What the connection supports

  • Candidate and contact upsert
  • Company and location sync
  • Job and placement sync
  • Soft delete propagation
  • Account level pause control

Scope and limitations

  • One direction only
  • Delivery, opens, replies, and Sense edits do not return to Teambridge
  • Credentials are obtained through an implementation contact

Operational use cases

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

Keep candidate audiences current

Push live Teambridge candidate and worker changes into Sense engagement records.

02

Connect jobs and placements

Resolve Sense placement relationships against already linked candidate and job identifiers.

03

Pause without disconnecting

Temporarily stop outbound sync at the account level while preserving the connection.

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

    Obtain credentials

    Request the Sense client ID and secret through the implementation contact.

  2. 2

    Connect the account

    Enter the OAuth client credentials in Teambridge.

  3. 3

    Map each object

    Configure candidate, company, job, placement, and contact field mappings.

  4. 4

    Validate relationship order

    Confirm that candidate and job identifiers exist before placement events are sent.

Questions and answers

What teams ask about Sense

What does the Sense integration with Teambridge do?+

Push candidate, company, job, placement, and contact updates from Teambridge into Sense. Keep the worker and staffing data used by Sense engagement current from Teambridge events without implying that messaging activity returns to Teambridge.

What data moves between Sense and Teambridge?+

Teambridge to Sense only.

How do you set up the Sense integration?+

Enter the Sense client ID and secret, configure mappings for each supported object, and enable the account sync.

Is the Sense integration generally available?+

A customer administrator can start the connection without a Teambridge feature flag. The most important current boundary is: One direction only.

Get started