Skip to main content
Connect Benchling from the Integrations page. Notebook entries from the projects you select become searchable content in Probe, filed in a dedicated team workspace.

​
Setup

1

Connect

Authorize the connection from the Integrations page.
2

Name the workspace

Connecting asks for the workspace name, prefilled with the source and editable. The slug is derived — lowercased, hyphenated, suffixed if taken.
3

Select projects

Choose which Benchling projects are in scope. The connector queries per project rather than sweeping everything.
4

Turn on live sync

New entries flow in as they appear.
Enabling live sync automatically queues a history pass over your selected projects, so existing notebook entries appear immediately. There is no separate backfill verb to remember.

​
Write-back

Writing generated prose back into custom entity fields is opt-in per connection and off by default.
Benchling is a customer’s system of record. Pushing generated content into it is a decision a person makes deliberately, per connection — not a default, and not something an agent turns on.

​
Scope and shape

  • Items carry their folder id; the connector queries by project id rather than by a global sweep.
  • Content lands in the named workspace as searchable documents, alongside everything else in Knowledge.

​
Disconnecting

As with every connector, disconnecting purges the installation’s own content before releasing the claim. Shared documents owned by a different installation are preserved, and the purge preview says so. Missing engine configuration is reported as an error rather than treated as proof of an empty index.