Benchling Events via AWS EventBridge

Integrations that react to supported Benchling changes, including entity registration and workflow updates. Reviewed 2026-09-30. Payloads and AWS deployment snippets are illustrative; no tenant subscription or deployment was tested. Event names below were checked against the current EventBridge reference and SDK 1.25.0 event models.

Official docs:

• Getting Started with Events
• Events Reference (payloads and event types)
• Events FAQs
• List Events API

Delivery methods: Benchling supports Webhooks (recommended for new apps) and AWS EventBridge (customer-owned event bus). EventBridge payloads are hydrated (full v2 API objects in detail); webhooks use thinner payloads. See the getting-started guide for trade-offs.

Setup checklist

1. Tenant admin enables Developer Platform access and opens Event Subscriptions (Feature settings → Developer Console → Events).
2. Create a subscription with:
3. AWS account ID and region
4. Event bus name (e.g. benchling-integrations)
5. Event types to receive (see Events Reference)
6. Immediately associate the partner event source with a new EventBridge bus in AWS (within ~12 days or the source expires).
7. Create EventBridge rules with detail-type / detail filters and targets (Lambda, SQS, SNS, CloudWatch Logs).
8. Grant invoke permissions (AWS::Lambda::Permission, queue policies, etc.).
9. Validate with a CloudWatch Logs rule on the bus source, then trigger a test action in Benchling.

Subscription statuses: Pending (needs bus association), Active, Expired (resubscribe in Benchling).

EventBridge event envelope

All EventBridge deliveries share this top-level shape. The resource body lives under detail under a key that varies by event (for example entry, assayRun, request).

{
  "version": "0",
  "id": "a1b2c3d4-e5f6-7890-abcd-ef1234567890",
  "detail-type": "v2.request.created",
  "source": "aws.partner/benchling.com/your-tenant/your-subscription-name",
  "account": "123456789012",
  "time": "2026-09-29T14:30:00.000000+00:00",
  "region": "us-west-2",
  "resources": [],
  "detail": {
    "id": "evt_abc123",
    "eventType": "v2.request.created",
    "createdAt": "2026-09-29T14:30:00.000000+00:00",
    "deprecated": false,
    "excludedProperties": [],
    "schema": {
      "id": "ts_abc123",
      "name": "Validated Request"
    },
    "request": {
      "id": "req_example",
      "name": "Sequencing request",
      "apiURL": "https://your-tenant.benchling.com/api/v2/requests/req_example"
    }
  }
}

Naming: detail-type and detail.eventType follow <version>.<resource>.<action> (for example v2.request.created, v2.workflowTask.updated.status).

Do not treat payloads as authoritative. Events may arrive late or out of order. Re-fetch objects with the SDK/API when you need current state.

Truncated events: Benchling documents a 256 KB EventBridge payload threshold. Inspect detail.excludedProperties. Re-fetch by ID through the configured tenant SDK; do not send credentials to an arbitrary apiURL from an event.

Minimal EventBridge rule (CloudFormation)

Route v2.request.created events for a specific request schema to a Lambda:

AWSTemplateFormatVersion: "2010-09-09"
Transform: AWS::Serverless-2016-10-31
Description: Benchling request.created → Lambda

Parameters:
  BenchlingEventBusName:
    Type: String
    Description: Partner event bus name from Benchling subscription

Resources:
  RequestCreatedRule:
    Type: AWS::Events::Rule
    Properties:
      Name: benchling-request-created
      EventBusName: !Ref BenchlingEventBusName
      State: ENABLED
      EventPattern:
        detail-type:
          - v2.request.created
        detail:
          schema:
            name:
              - Validated Request
      Targets:
        - Id: HandleRequestCreated
          Arn: !GetAtt HandleEventLambda.Arn

  HandleEventLambda:
    Type: AWS::Serverless::Function
    Properties:
      Handler: app.handler
      Runtime: python3.12
      CodeUri: src/
      Timeout: 30

  AllowEventBridgeInvoke:
    Type: AWS::Lambda::Permission
    Properties:
      Action: lambda:InvokeFunction
      FunctionName: !Ref HandleEventLambda
      Principal: events.amazonaws.com
      SourceArn: !GetAtt RequestCreatedRule.Arn

Other filter examples (from Benchling docs):

{
  "detail-type": ["v2.assayRun.updated.fields"],
  "detail": {
    "updates": ["fields.my_field"]
  }
}

{
  "detail-type": ["v2.entity.registered"],
  "detail": {
    "entity": {
      "schema": {
        "id": ["ts_MySchemaId"]
      }
    }
  }
}

Lambda handler skeleton (Python)

import logging

logger = logging.getLogger()
logger.setLevel(logging.INFO)

# Optional: re-fetch via SDK when payload may be stale or truncated
# import os
# from benchling_sdk.benchling import Benchling
# from benchling_sdk.auth.api_key_auth import ApiKeyAuth
#
# benchling = Benchling(
#     url=os.environ["BENCHLING_TENANT_URL"],
#     auth_method=ApiKeyAuth(os.environ["BENCHLING_API_KEY"]),
# )


def handler(event, context):
    """Process a single Benchling EventBridge delivery."""
    detail_type = event.get("detail-type")
    detail = event.get("detail") or {}

    logger.info(
        "benchling_event",
        extra={
            "detail_type": detail_type,
            "event_id": detail.get("id"),
            "benchling_event_type": detail.get("eventType"),
        },
    )

    if detail.get("deprecated"):
        logger.warning("deprecated_event_type: %s", detail_type)

    if detail.get("excludedProperties"):
        logger.warning(
            "truncated_payload excluded=%s", detail.get("excludedProperties")
        )

    if detail_type == "v2.request.created":
        request = detail.get("request") or {}
        request_id = request.get("id")
        if not request_id:
            raise ValueError("missing request.id in event detail")
        # Prefer API lookup for authoritative data:
        # current = benchling.requests.get_by_id(request_id)
        return {"status": "observed", "request_id": request_id}

    if detail_type == "v2.workflowTask.updated.status":
        task = detail.get("workflowTask") or {}
        return {"status": "ok", "task_id": task.get("id")}

    logger.info("no_handler_for_detail_type: %s", detail_type)
    return {"status": "ignored", "detail_type": detail_type}

This skeleton only validates/routes a payload. Add persistent deduplication keyed by detail.id before side effects: delivery is at least once and can be out of order. Mark an event complete only after processing succeeds. Configure retries and a dead-letter queue; do not rely on a Lambda return value to acknowledge a business operation.

For serverless timeouts, benchling.tasks.wait_for_task defaults to 600 seconds. Use a shorter explicit deadline or enqueue work; a server-side job continues after polling times out.

Validation steps

1. Subscription active: In Benchling, subscription status is Active (not Pending or Expired).
2. Partner source associated: In AWS EventBridge → Partner event sources, source is associated with your bus.
3. Log all events: Add a catch-all rule targeting a CloudWatch log group, filtering on your bus source (shown in Benchling subscription UI).
4. Trigger a test event: Create or update an object matching your rule filter (for example register a DNA sequence).
5. Inspect logs: Confirm detail-type, detail.id, and resource IDs match expectations.
6. Re-fetch check: Call the SDK/API for the resource ID and confirm it matches your integration logic.

Recovering missed events

Benchling does not replay EventBridge deliveries. After an outage:

1. Get the affected time window from Benchling support.
2. List historical events with the List Events API (retained ~2 weeks).
3. Re-route recovered events through your own infrastructure.

SDK 1.25.0 example (created_atgte is the actual parameter spelling):

events = benchling.events.list(
    created_atgte="2026-09-29T00:00:00+00:00",
    event_types="v2.request.created",
)

for page in events:
    for evt in page:
        print(evt.event_type, evt.id)

Events are ordered by processing order, not createdAt. Persist starting_after checkpoints only after successful processing and deduplicate overlapping recovery windows. Historical API results are event objects, not AWS envelopes; if feeding the handler above, explicitly adapt them to its detail and detail-type structure.

EventBridge vs Webhooks

For new Benchling Apps, Benchling recommends webhooks unless you already standardize on EventBridge in AWS. See Getting Started with Webhooks.

Do not assume event names are interchangeable between delivery mechanisms. Stable EventBridge uses v2.entry.updated.fields, not a generic v2.entry.updated; the current EventBridge reference does not list v2.dnaSequence.created or v2.dnaSequence.updated. For entity registration use v2.entity.registered and its entity payload. For webhooks, verify the signature and app-specific payload against the separate webhook reference.