Feature · Action columns
Action columns turn rows into execution queues
A spreadsheet should not only describe work. It should help finish it. Action columns let teams run external actions from cells with previews, approvals, dry runs, retries, quotas, and full execution history.
- Dry-run mode before any real call
- Approval flows for sensitive actions
- Bulk-send guards, rate limits, and workspace quotas
- Per-row execution history, retries, and idempotency
- Preview first
- Approve before sending
- Audit every run
What action columns can trigger
- Send emails (Gmail or your connected mail tool)
- Create and update CRM records (HubSpot, Salesforce, and more)
- Post messages or threads to Slack
- Create Linear, Notion, or task-system items
- Schedule social posts (where supported by the connected tool)
- Trigger a custom webhook or downstream workflow
Safer execution for real workflows
Action columns are built for workflows where mistakes matter. Before running actions at scale, teams can preview the exact payload, dry-run the full path, require approval, inspect execution history, and cap bulk runs.
- Dry-run mode runs the full path without making the external call
- Approvals queue sensitive runs for an owner or admin
- Bulk-send guard prompts before more than N rows execute
- Per-workspace rate limits and monthly quotas
- Retries with exponential backoff on transient failures
- Idempotency keys prevent duplicate sends
Example: outbound approval workflow
- 01
Import accounts
Paste, upload, or connect Google Sheets.
- 02
Enrich the company and contact
Add integrated columns for CRM context and AI columns for research.
- 03
Generate a first email
AI column drafts copy per row using the enriched context.
- 04
Mark approved rows
A select column flips to 'Approved' after a human reviews.
- 05
Dry-run the action column
Inspect the payload, preview the rendered email, fix anything wrong.
- 06
Admin approves
An approval flow holds the send until an authorised teammate signs off.
- 07
Send and log
Sheetlane sends emails and writes status, message id, and timestamp back to the row.
What stays on the row
Every run is tied to the row that started it. That row records the payload sent, the response received, retries attempted, the user who approved it, and the final status. Auditability without a separate logging tool.
Frequently asked questions
Can I test an action before sending it?
Yes. Dry-run mode runs the full path, column lookup, field mapping, payload assembly, without making the external call. You can also preview the exact payload that would be sent.
Can actions require approval?
Yes. Approval flows hold sensitive actions until an admin or owner approves. Approvals can be required per column or for runs above a row-count threshold.
Can Sheetlane prevent duplicate sends?
Yes. Sheetlane includes idempotency protection so re-running an action against a row that already executed will not send twice unless you explicitly re-queue it.
What happens if an action fails?
Failed runs are visible in the row's execution drawer, retried automatically where appropriate, and never silently dropped. You can retry, edit the payload, or cancel a queued run.
Related reads
Build an action workflow
Start with a blank spreadsheet, import a file, or apply a template. Connect tools when you are ready to take action.