Skip to content
Documentation
Contact
← Back to documentation
Technical Reference

Smartsheet

Dynamic work execution platform for teams to plan, capture, manage, automate, and report on work at scale.

CategoryProductivity
Authenticationcustom
Version0.1.7
Published scopes0 published scopes
Last updatedSeptember 23, 2026

Overview

Connect Smartsheet with Flows360

Dynamic work execution platform for teams to plan, capture, manage, automate, and report on work at scale.

Use the Smartsheet 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 4 triggers.

Available actions

  • Add Row to Sheet
  • Update Row
  • Attach File to Row
  • Find Row
  • List Row Attachments
  • Find Sheet(s)

Available triggers

  • New Row Added
  • Row Updated
  • New Attachment Added
  • New Comment Added

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: Smartsheet
  • Package: @activepieces/piece-smartsheet@0.1.7
  • Exact artifact digest: sha256:c5e17b0d4ba64cad885e4fbedbc3534a0f55668491e0fbd636f9b353d34dde32
  • Runtime: Activepieces-compatible deterministic worker
  • Source: the exact reviewed Activepieces source

Authentication

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

Action contracts

  • Add Row to Sheet (add_row_to_sheet), Adds new row to a sheet. Classification: read.
  • Update Row (update_row), Updates an existing row. Classification: read.
  • Attach File to Row (attach_file_to_row), Adds a file attachment to a row. Classification: read.
  • Find Row (find_rows_by_query), Finds rows in a specific sheet or across all accessible sheets using text queries with advanced filtering options. Classification: read.
  • List Row Attachments (find_attachment_by_row_id), Get all attachments for a specific row in a Smartsheet, including row and discussion-level attachments with comprehensive pagination and filtering options Classification: read.
  • Find Sheet(s) (find_sheet_by_name), Fetches existings sheets matching provided filter criteria. Classification: read.

Trigger contracts

  • New Row Added, webhook.
  • Row Updated, webhook.
  • New Attachment Added, webhook.
  • New Comment Added, webhook.

Verification

Deterministic execution evidence is recorded for the pinned artifact, including 1 exercised action entrypoint and 0 exercised trigger entrypoints.

Capability summary

Authenticationcustom
Supported objects10
Supported actionsNot published
Triggers4

Authentication

Authentication method: custom

Authentication profiles

connection · custom
  • Access Token Required · protected credential

Supported objects

ObjectReadWriteNotes
Add Row to Sheet Yes No Adds new row to a sheet.
Update Row Yes No Updates an existing row.
Attach File to Row Yes No Adds a file attachment to a row.
Find Row Yes No Finds rows in a specific sheet or across all accessible sheets using text queries with advanced filtering options.
List Row Attachments Yes No Get all attachments for a specific row in a Smartsheet, including row and discussion-level attachments with comprehensive pagination and filtering options
Find Sheet(s) Yes No Fetches existings sheets matching provided filter criteria.
New Row Added Yes No webhook trigger declared by the pinned package.
Row Updated Yes No webhook trigger declared by the pinned package.
New Attachment Added Yes No webhook trigger declared by the pinned package.
New Comment Added Yes No webhook trigger declared by the pinned package.

Triggers

New Row Added · Webhook

Triggers when a new row is added.

Inputs

  • sheet_id · string
Row Updated · Webhook

Triggers when an existing row is updated.

Inputs

  • sheet_id · string
New Attachment Added · Webhook

Triggers when a new attachment is added to a row or sheet.

Inputs

  • sheet_id · string
New Comment Added · Webhook

Triggers when a new comment is added to a discussion on a sheet.

Inputs

  • sheet_id · string

Setup

Setup

  1. Add the Smartsheet 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:
  • No provider credential fields are declared by the pinned package.
  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-smartsheet@0.1.7; provider behaviour can change independently and should be revalidated when the provider or connector version changes.
  • Only the 6 actions and 4 triggers 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.
  • Deterministic execution evidence is recorded for the pinned artifact, including 1 exercised action entrypoint and 0 exercised trigger entrypoints.

Troubleshooting

Why canu2019t the connector authenticate?

Check the tenant connection in Studio and confirm every required Smartsheet 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-smartsheet@0.1.7 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