The Workflow Creation Assistant provides the ability to quickly build and deploy your own custom lab data automation workflows, without needing to write any code or rely on internal IT teams to build custom data integrations. By using AI, the app helps scientists generate and deploy the Tetra Data Pipelines required to have their instrument data automatically processed, mapped, and delivered to electronic lab notebooks (ELNs) and Laboratory Information Management Systems (LIMS)—up to 40x faster than traditional, manual methods.

Prerequisites

The Workflow Creation Assistant requires the following.

TDP Requirements

All Workflow Creation Assistant setups must meet the following minimum Tetra Data Platform (TDP) requirements:

• TDP v4.2.0 or higher (v4.3.1 or higher is recommended).
• Customers must contact their customer account leader to activate the app in their TDP environment.
• App users must have either Developer or Administrator TDP permissions.
• A Tetra Data Pipeline deployed in the same TDP org as the Workflow Creation Assistant that uses one of the following protocols:
  • For Revvity Signals integrations: Use the python-exec-signals:v1.0.0 protocol or higher. The pipeline should be configured with access credentials to Revvity Signals, and pipeline triggers to process IDS files that become available in the TDP
  • For Benchling integrations: Use the python-exec-benchling:v1.0.0 protocol or higher. The pipeline should be configured with access credentials to Benchling, and pipeline triggers to process IDS files that become available in the TDP.

📘

NOTE

The Workflow Creation Assistant will configure the pipeline that you create with code to transform and push data to your selected ELN. Workflow Creation Assistant will not modify other pipeline configurations, which must be updated through the TDP user interface. For more information, see Set Up and Edit Pipelines.

Revvity Signals Requirements

To build Revvity Signals integrations, app users must have access to the following information about their organization's Signals account:

• Signals Base URL
• Signals API key

These settings may be saved as Tetra Shared Settings and Secrets or entered directly in the app. In addition, the Admin Defined Tables used for integration must already be defined, and a Signals Experiment must already exist for integration testing between TDP and Signals.

Benchling Requirements

To build Benchling integrations, app users must have access to the following information about their organization's Benchling account, which must have access to Output File Processors, Assay Runs, and Assay Results:

• Benchling Base URL
• Benchling Project ID
• Benchling App credentials with access to all schemas and Benchling Projects within the integration's scope, including the following:
  • A Client ID
  • A Client Secret
• Benchling Assay Run and Result schema definitions (IDs) defined and accessible in Feature Settings

The Benchling Base URL, Project ID, Client ID, and Client secret may all be saved as Tetra Shared Settings and Secrets or entered directly in the app.

User Guides

For more information about how to use the Workflow Creation Assistant, see the latest user guide:

• Workflow Creation Assistant User Guide (v1.0.x)

Documentation Feedback

Do you have questions about our documentation or suggestions for how we can improve it? Start a discussion in TetraConnect Hub. For access, see Access the TetraConnect Hub.

📘

NOTE

Feedback isn't part of the official TetraScience product documentation. TetraScience doesn't warrant or make any guarantees about the feedback provided, including its accuracy, relevance, or reliability. All feedback is subject to the terms set forth in the TetraConnect Hub Community Guidelines.