--- title: Test Connector Assets slug: turbine-user-guide/test-connector-assets docTags: createdAt: 2026-07-07T14:07:49.926Z --- Use connection testing to validate connector asset credentials, endpoints, and parameters before playbooks run. This topic covers prerequisites, eligibility by asset type, manual and automatic tests, history, and how connection testing differs from action testing on the **Usage** tab. ## Choose Your Path | Goal | Where to go | | ------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------- | | Test one asset while editing it | [Test Connection from an Asset](https://docs.swimlane.com/test-connector-assets#test-connection-from-an-asset) | | Test a new connector asset before saving | [Test Connection When Creating an Asset](https://docs.swimlane.com/test-connector-assets#test-connection-when-creating-an-asset) | | Test many assets across tenants | [Configuration Manager](docId\:O4geP3VQ8U6zCsjyL_JBo) — **Test** or **Test Connections** | | Run daily validation without manual tests | [Enable Automatic Testing](https://docs.swimlane.com/test-connector-assets#enable-automatic-testing) | | Review past test results | [Review Connection Test History](https://docs.swimlane.com/test-connector-assets#review-connection-test-history) | | Test a playbook action that uses the asset | [Connection Testing and Action Testing](https://docs.swimlane.com/test-connector-assets#connection-testing-and-action-testing) | | Understand why **Test Connection** is unavailable | [Eligibility and Limitations](https://docs.swimlane.com/test-connector-assets#eligibility-and-limitations) | ## Prerequisites Connection testing is available only when both of the following are in place. | Requirement | Details | | -------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Test Asset Connection** feature flag | An administrator must enable **Test Asset Connection** in feature flags. The flag is **disabled by default**. | | **Assets → Test** permission | Starting in **Turbine 26.2.0**, the user role must include **Assets → Test** on enhanced RBAC. **Test** requires **Read** and **Update** on the asset. **Account Admin**, **Tenant Admin**, and **Super Admin** receive **Test** by default; other roles must be granted **Test** explicitly. See [Enhanced Role-Based Access Control (RBAC)](docId:4c4ar7pxA6dE6TJ3DZB_S). | ## Eligibility and Limitations | Asset type | **Test Connection** visible | Connection test can run | Automatic testing | | ----------------------------------------------------- | --------------------------- | ---------------------------------------------------------- | ------------------------------------ | | **Connector-backed asset** (installed connector type) | Yes | Only when the connector supports a test action (see below) | Only when a test action is available | | **Custom asset** (key icon) | No | No | No | **When a connector-backed asset supports connection testing** The platform runs a connection test when the connector asset manifest defines a supported `test_asset_action`, or when **creating** a new asset and the connector exposes a **GET** action with no required inputs. **When creating an asset**, the platform may use that **GET** fallback to enable **Test Connection**. **When editing an existing asset**, the platform uses the persisted test action configuration or an explicit `test_asset_action` on the asset manifest. A **GET** fallback alone does not enable testing on edit if no test action was saved with the asset. :::hint{type="info"} The **Test Connection** button can appear for connector assets even when a test cannot run (for example, the connector has no supported test action). In that case the button is disabled or the test cannot complete until the connector supports testing. ::: ## Test Connection from an Asset Validate a connector asset from the **Configuration** tab without running a playbook. 1. Navigate to **ORCHESTRATION > Assets**. 2. Open the asset in **Edit Asset** mode. 3. On the **Configuration** tab, review or update asset parameters as needed. 4. Click **Test Connection**. 5. Wait for validation to complete. When the test finishes: - A successful validation displays **Test was successful**. - A failed validation displays **Test was failed**. Connection testing verifies that credentials, endpoints, and other configuration values are valid before the asset is used in playbooks. :::hint{type="info"} Manual connection tests performed before you **Save** the asset are **not** recorded on the **History** tab. ::: ## Test Connection When Creating an Asset When you create a connector-backed asset, **Test Connection** appears next to **Asset Parameters** when the connector type supports connection testing. 1. Navigate to **ORCHESTRATION > Assets**. 2. Click the **plus** icon and select a connector asset type. 3. Complete required **Title**, **Name**, and parameter fields. 4. Click **Test Connection**. 5. Review the result, then click **Create** to save the asset. Use this workflow to confirm configuration before the asset is used in playbooks. ## Enable Automatic Testing Automatic testing runs one connection validation per day for supported connector assets. 1. Open the asset in **Edit Asset** mode. 2. On the **Configuration** tab, enable **Enable automatic testing**. 3. Click **Save**. The scheduled test uses the same validation process as **Test Connection** and helps surface connectivity or authentication issues before playbook execution. Automatic testing is disabled by default and must be enabled per asset. It is available only for asset types that support connection testing. :::hint{type="info"} Automatic connection test entries appear on the **History** tab after the scheduled test runs. Because tests run once per day, new entries may not appear immediately after you enable automatic testing. ::: ## Review Connection Test History The **History** tab on **Edit Asset** shows asset changes and connection testing activity. **Summary fields** | Field | Description | | ---------------- | -------------------------------- | | Created | Date the asset was created | | Created By | User who created the asset | | Last Modified | Date the asset was last updated | | Last Modified By | User who last modified the asset | **Activity table** | Column | Description | | ----------- | -------------------------------------------------- | | Date | Date the activity occurred | | Description | Type of activity | | Status | Result of a connection test, when applicable | | User | User associated with the activity | | Details | Additional information for failed connection tests | **Connection test activity types** | Activity | Description | | --------------------------- | ------------------------------------------------ | | Connection Test (Manual) | A test initiated with **Test Connection** | | Connection Test (Automatic) | A test initiated by **Enable automatic testing** | **Connection test status** - **Success** — The connection test completed successfully. - **Failure** — The connection test was unsuccessful. Asset creation and modification activities do not display a status. **View failed test details** 1. On the **History** tab, locate a failed connection test row. 2. Click **View** in the **Details** column. A panel opens with diagnostic information for troubleshooting. **History retention** Asset history is retained for **seven days**. Older activities are removed from the history view. ## Test from Configuration Manager Administrators can test connector assets across tenants from [Configuration Manager](docId\:O4geP3VQ8U6zCsjyL_JBo): - **Test** (ellipsis menu) — Test a single asset. - **Test Connections** (toolbar) — Test multiple selected assets and review bulk results. Connection tests started in Configuration Manager update asset health metrics and appear on the asset **History** tab. Bulk tests require **Assets → Test** on each affected tenant. For step-by-step procedures and bulk result columns, see Configuration Manager. ## Connection Testing and Action Testing The **Usage** tab on **Edit Asset** lists playbooks and components that use the asset. **View & Test** opens the action **Test** console — this runs the **action** with optional inputs; it is **not** the same as asset **connection testing**. | | Connection testing | Action testing (Usage tab) | | ----------------------- | ------------------------------------------------------------------ | ------------------------------- | | **Purpose** | Validate asset credentials and connectivity | Run a specific connector action | | **Where** | **Configuration** tab — **Test Connection**; Configuration Manager | **Usage** tab — **View & Test** | | **Recorded on History** | Yes (after save; manual and automatic) | No | To test an action from the **Usage** tab: 1. Open the asset in **Edit Asset** mode. 2. Select the **Usage** tab. 3. Click **View & Test** for the playbook or component row. 4. Provide inputs (**From Previous Run** or manual entry) if required. 5. Click **Test** and review the **Result** section. ## When a Connector Does Not Support Testing If **Test Connection** is disabled or bulk testing reports unsupported assets: - The connector asset type may not define a supported test action. - **Custom assets** never support connection testing. - Mixed bulk selections that include unsupported assets must be corrected — deselect unsupported assets and test only eligible connector assets. **Request test support for a connector** Swimlane and connector authors can add connection testing by defining a `test_asset_action` on the connector asset manifest (or by exposing a **GET** action with no required inputs for new assets). To request test capability for a marketplace or custom connector, contact **Swimlane Support** with the connector name and asset type. ## See Also - [Assets](docId\:WCTH-W3LZbvhC4C_fwt1m) — Create, edit, and manage assets - [Configuration Manager](docId\:O4geP3VQ8U6zCsjyL_JBo) — Multi-tenant asset management and bulk connection tests - [Enhanced Role-Based Access Control (RBAC)](docId:4c4ar7pxA6dE6TJ3DZB_S) — **Assets → Test** permission