Skip to content
Documentation
Contact
← Back to documentation
Technical Reference

Microsoft SQL Server

Microsoft's relational database engine, on-premise or as Azure SQL

CategoryDeveloper Tools
Authenticationcustom
Version0.0.2
Published scopes0 published scopes
Last updatedSeptember 30, 2026

Overview

Connect Microsoft SQL Server with Flows360

Microsoft's relational database engine, on-premise or as Azure SQL

Use the Microsoft SQL Server connector to include its declared actions and events in Flows360 workflows without duplicating the integration logic inside each consuming system. This pinned connector version currently exposes 6 actions and 1 trigger.

Available actions

  • Find Rows
  • Insert Row
  • Update Rows
  • Delete Rows
  • Get Tables
  • Run Query

Available triggers

  • New or Updated Row

The capability list above is generated from the exact reviewed connector package so the public description stays aligned with the version Flows360 operates.

Technical guide

Technical reference

Package identity

  • Connector: Microsoft SQL Server
  • Package: @activepieces/piece-microsoft-sql-server@0.0.2
  • Exact artifact digest: sha256:8edc3d2e967eb748d61d93689414ff45c6a6e5f75947251ad30ed4b1e10c596b
  • Runtime: Activepieces-compatible deterministic worker
  • Source: the exact reviewed Activepieces source

Authentication

CUSTOM AUTH. Connection values are tenant-specific and remain in the consuming Studio instance; CDK stores definitions and field metadata, not customer credential values.

Action contracts

  • Find Rows (find_rows), Reads rows from a table Classification: read.
  • Insert Row (insert_row), Inserts a new row into a table and returns it Classification: read.
  • Update Rows (update_rows), Updates every row whose search column matches a value Classification: read.
  • Delete Rows (delete_rows), Deletes every row whose search column matches a value Classification: read.
  • Get Tables (get_tables), Returns a list of tables in the database Classification: read.
  • Run Query (run_query), Runs a T-SQL statement and returns the rows it produced Classification: read.

Trigger contracts

  • New or Updated Row, polling.

Verification

Runtime execution evidence is managed separately from package metadata.

Capability summary

Authenticationcustom
Supported objects7
Supported actions6
Triggers1

Authentication

Authentication method: custom

Authentication profiles

connection · custom
  • Connection String Optional
  • Host Optional
  • Port Optional
  • Database Optional
  • Username Optional
  • Password Optional · protected credential
  • Encrypt Connection Required
  • Trust Server Certificate Required
  • CA Certificate Optional
  • Minimum TLS Version Optional

Supported objects

ObjectReadWriteNotes
Find Rows Yes No Reads rows from a table
Insert Row Yes No Inserts a new row into a table and returns it
Update Rows Yes No Updates every row whose search column matches a value
Delete Rows Yes No Deletes every row whose search column matches a value
Get Tables Yes No Returns a list of tables in the database
Run Query Yes No Runs a T-SQL statement and returns the rows it produced
New or Updated Row Yes No polling trigger declared by the pinned package.

Supported actions

Find Rows · Read

Reads rows from a table

find_rows · Risk: low · Retry: safe

Inputs

  • markdown · string · Optional, n **DO NOT** paste dynamic values straight into the query text.n nn Use **@name** placeholders in the query and put the values in the Parameters field, so they are sent separately and cannot cause **SQL injection**.
  • table · string · Required, The table to work with.
  • columns · array · Optional, Columns to return. Leave empty to return every column.
  • condition · string · Optional, The WHERE clause without the WHERE keyword, for example: balance >= @min AND is_active = 1. Leave empty to return every row.
  • parameters · object · Optional, Values for the @placeholders used in the condition. Enter the name without the @ prefix.
  • order_by · string · Optional, Column to sort the rows by.
  • order_direction · string · Optional
  • limit · number · Optional, Maximum number of rows to return. Leave empty for no limit.
Insert Row · Read

Inserts a new row into a table and returns it

insert_row · Risk: low · Retry: safe

Inputs

  • table · string · Required, The table to work with.
  • values · object · Required, Column name to value. Omit columns that the database fills in, such as an identity id or a default timestamp.
Update Rows · Read

Updates every row whose search column matches a value

update_rows · Risk: low · Retry: safe

Inputs

  • table · string · Required, The table to work with.
  • values · object · Required, Column name to new value.
  • search_column · string · Required, Rows are updated where this column equals the value below.
  • search_value · string · Required, The value the search column must equal.
Delete Rows · Read

Deletes every row whose search column matches a value

delete_rows · Risk: low · Retry: safe

Inputs

  • table · string · Required, The table to work with.
  • search_column · string · Required, Rows are deleted where this column equals the value below.
  • search_value · string · Required, The value the search column must equal.
Get Tables · Read

Returns a list of tables in the database

get_tables · Risk: low · Retry: safe

Run Query · Read

Runs a T-SQL statement and returns the rows it produced

run_query · Risk: low · Retry: safe

Inputs

  • markdown · string · Optional, n **DO NOT** paste dynamic values straight into the query text.n nn Use **@name** placeholders in the query and put the values in the Parameters field, so they are sent separately and cannot cause **SQL injection**.
  • query · string · Required, The T-SQL to run. Refer to values as @name and define them in Parameters below, for example: SELECT * FROM customers WHERE id = @id
  • parameters · object · Optional, Values for the @placeholders in the query. Enter the name without the @ prefix u2014 a key of id fills @id.
  • query_timeout · number · Optional, How long to wait for the statement before giving up.

Triggers

New or Updated Row · Poll

Fires when a row is added to, or changed in, a table

Inputs

  • description · string
  • table · string
  • order_by · string
  • order_direction · string

Setup

Setup

  1. Add the Microsoft SQL Server connector to the workflow in the target Flows360 Studio instance.
  2. Create or select the tenant-specific connection required by the connector. Connection secrets remain in the Studio connection boundary and are not copied into CDK documentation.
  3. Provide the connection fields declared by the pinned package:
  • Connection String (connection_string), optional.
  • Host (host), optional.
  • Port (port), optional.
  • Database (database), optional.
  • Username (user), optional.
  • Password (password), optional; stored as a sensitive connection value.
  • Encrypt Connection (encrypt), required.
  • Trust Server Certificate (trust_server_certificate), required.
  • CA Certificate (certificate), optional.
  • Minimum TLS Version (min_tls_version), optional.
  1. Select the required action or trigger and complete its declared input fields. Required and optional inputs are defined by the exact package schema.
  2. Test the workflow in the appropriate environment before enabling production scheduling or event delivery.

Limitations

Limitations and operational notes

  • This content describes @activepieces/piece-microsoft-sql-server@0.0.2; provider behaviour can change independently and should be revalidated when the provider or connector version changes.
  • Only the 6 actions and 1 trigger declared by this pinned package are represented here.
  • Tenant credentials and connection values are not stored in the public connector record.
  • Provider-side permissions, account entitlements, quotas and rate limits remain subject to the connected provider account and are not inferred when the package does not declare them.
  • Runtime execution evidence is managed separately from package metadata.

Troubleshooting

Why canu2019t the connector authenticate?

Check the tenant connection in Studio and confirm every required Microsoft SQL Server connection field is present. Re-authorise OAuth-based connections if the provider token or consent has expired. Do not place credential values in CDK content or logs.

Why is an action or trigger unavailable?

Confirm that the workflow is using @activepieces/piece-microsoft-sql-server@0.0.2 and compare the requested capability with the declared action and trigger list for this version. A capability that is not declared by the pinned package should not be presented as supported.

What should I check after a provider-side change?

Revalidate authentication, required fields, action/trigger behaviour and provider documentation before publishing refreshed connector content or moving a new package version into production.

github.com