Reference · built on requestConnectorFiles, documents & spreadsheets

Smartsheet

Sheets, rows, columns, attachments, and reports from Smartsheet through the Smartsheet API, with webhooks on sheet changes.

About

Smartsheet is a work-management grid. A sheet has typed columns, rows with cells, attachments, and discussions; reports gather rows from several sheets; workspaces and folders organize them. Project offices, facilities teams, and vendor managers run trackers in it. The API at api.smartsheet.com/2.0 reads and writes those objects, and sheet webhooks call back when rows, cells, attachments, or comments change.

Through Fibric, an operator reads the rows behind a tracker, checks dates and attachments, and proposes cell updates, new rows, or a discussion on a row. You approve the batch. The rows are written once, and a receipt names what changed, why, and how to undo it.

This is a reference listing. It documents what Fibric would read from Smartsheet and what it could propose, based on the vendor's published interfaces. Fibric builds it under a managed deployment when you request it; selecting it here installs nothing.

Inputs

  • Sheets the token can reach through GET /sheets, and a full sheet with columns, rows, and cells through GET /sheets/{sheetId}
  • Cell history behind one cell through GET /sheets/{sheetId}/rows/{rowId}/columns/{columnId}/history
  • Attachments on a sheet or row, downloaded through a temporary URL from GET /sheets/{sheetId}/attachments/{attachmentId}
  • Discussions and comments on sheets and rows through GET /sheets/{sheetId}/discussions
  • Reports that roll up several sheets through GET /reports and GET /reports/{reportId}
  • Sheet webhook callbacks for row, cell, column, attachment, discussion, comment, and sheet events, signed in Smartsheet-Hmac-SHA256
  • Text search across sheets through GET /search

Proposed actions

  • Target capability: propose new rows through POST /sheets/{sheetId}/rows, placed with toTop, toBottom, parentId, or siblingId
  • Target capability: propose cell updates on several rows in one PUT /sheets/{sheetId}/rows call
  • Target capability: propose a discussion on a row through POST /sheets/{sheetId}/rows/{rowId}/discussions
  • Target capability: propose attaching a file or URL to a row through POST /sheets/{sheetId}/rows/{rowId}/attachments
  • Target capability: propose sending a report as a PDF through POST /reports/{reportId}/emails

Proposed actions are target capabilities. Every action runs propose-first and needs a validated deployment and the appropriate permissions.

What you can build

  • Age the work-order sheet

    The operator reads a work-order sheet each morning, computes days open per row from cell history, and proposes cell updates that flag rows past their target. You approve the batch.

    With Work Order Aging

  • COI expiry from a vendor sheet

    A vendor sheet holds certificate dates as cells and the certificates as row attachments. The operator proposes a discussion on each row whose date falls inside the renewal window.

    With COI Expiry

  • Contractor credentials before the badge

    When a row arrives through a webhook callback, the operator fetches it, checks the credential attachments, and proposes a status cell change or a comment asking for what is missing.

    With Contractor Credentials

  • Follow up on owners in the tracker

    The operator reads an action sheet and proposes a discussion on each overdue row, addressed to the assigned contact, leaving a record of every nudge.

    With Action Follow-up

Requirements

  • A Smartsheet plan with API access: Business, Enterprise, or Advanced Work Management
  • A token generated for the right environment; tokens for Smartsheet, Smartsheet Regions, and Smartsheet Gov are not interchangeable
  • Sharing permissions on each sheet; an OAuth scope such as WRITE_SHEETS does not override VIEWER access
  • ADMIN_WEBHOOKS scope and an endpoint that echoes the Smartsheet-Hook-Challenge header to enable a webhook
  • A smartsheet-integration-source header naming the integration type, organization, and integrator
Authentication
An access token generated under Personal Settings > API Access, sent as Authorization: Bearer, or a three-legged OAuth 2.0 app with scopes such as READ_SHEETS, WRITE_SHEETS, and ADMIN_WEBHOOKS.

Limits

  • 300 requests per minute per API token; posting a file attachment or reading cell history counts 10x and is limited to 30 per minute
  • Sheet webhooks accept only the all-events pattern "*.*"; event filtering exists for plan webhooks only
  • On Smartsheet Commercial, callbacks are debounced for one minute; the payload is skinny, so the row must be fetched afterward
  • After 14 failed deliveries a webhook is set to DISABLED_CALLBACK_FAILED and must pass verification again

Access and pricing

Reference listing. Fibric builds the connector under a managed deployment when you request it. Your quote covers the build, capabilities, usage, and support.

Request Smartsheet ↗

Questions and answers

What does a Smartsheet webhook send?
A skinny callback: the scope object and an events array with objectType (sheet, row, column, cell, attachment, discussion, comment) and the affected id. Your application then reads the row or cell through the API. Each callback is signed with the webhook's sharedSecret in the Smartsheet-Hmac-SHA256 header.
Which plans include the API?
Smartsheet documents Business, Enterprise, and Advanced Work Management as the required plans for generating an API access token. Tokens are generated under Personal Settings > API Access, and each environment (Smartsheet, Regions, Gov) needs its own token.
How are rate limits applied?
300 requests per minute per API token for most operations. Posting a file attachment and fetching cell history carry a 10x multiplier and are limited to 30 per minute. A 429 returns "Rate limit exceeded"; Smartsheet suggests sleeping at least 60 seconds before retrying.
Ask about Smartsheet

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.