OtherReal-timeUpdated May 2026

Stackby

Stackby spreadsheet-database with templates

Stackby is the spreadsheet-database hybrid with pre-built integration columns — columns can pull data from external APIs (LinkedIn enrich, Twitter info, weather, etc.) directly in the spreadsheet. Tiny Command exposes one action, no triggers: List Items (records from a Stackby stack). The connection takes a Stackby API key plus the stack ID. Stackby's differentiator vs Airtable/Notion is the built-in API columns — a Stackby cell can be configured to pull from external APIs in-cell, useful for data enrichment workflows without separate API calls. For workflows that integrate Stackby-managed data with other systems, this connector handles the read side. For richer Stackby interaction, the HTTP action against the v1 API covers more endpoints.

Connect Stackby

0triggers

1action

≈ 2 minto set up

Freetier · no card

Actions

Do anything Stackby can do, from a workflow.

Every action accepts dynamic inputs from upstream nodes, whether that's an AI output, a form field, or a search result.

Action	What it does	Inputs
List Stackby Records	Returns rows from a Stackby table. For sync workflows or for "fetch this config from Stackby" lookups.	0 fields	View →

Recipes

Pre-built Stackby workflows.

Clone any recipe and customize it in one click. Every recipe is fully editable.

Stackby → Slack alerts

AI-triage every Stackby event, ping the right channel only when it matters.

Stackby → Google Sheets log

Every event matching a filter, appended to a running spreadsheet.

Stackby → Notion database

Turn Stackby into a Notion-backed source of truth, auto-tagged.

Before you build

Three things worth knowing.

Filter at the trigger

Tiny Command counts a run the moment a trigger fires. Filtering early means only matching events spend your usage budget.

Authorize once, reuse anywhere

Connect Stackby once and every workflow on your account can use its triggers and actions. You don't have to re-auth per workflow.

No JSON to read

Every Stackby field shows up in the visual picker for downstream nodes. The raw payload is there for power users, optional for everyone else.

FAQ

Questions about the Stackby integration.

If we missed yours, ping support. We usually reply within an hour.

How do I connect Stackby to Tiny Command?

Open the Tiny Command workflow builder, drop in a Stackby node, and click Connect. Authorize Stackby once and any workflow on your account can use its triggers and actions. Most teams finish the connection in under two minutes.

What Stackby triggers does Tiny Command support?

Tiny Command focuses on outbound actions for Stackby today. Use Tiny Command's universal Webhook or Schedule trigger to start Stackby workflows, then run any Stackby action you need.

What Stackby actions can I run from a workflow?

1 Stackby action are available out of the box, covering other operations like "List Stackby Records". Every action accepts dynamic inputs from upstream nodes, whether that's a search result, an AI output, or a form field.

Is the Stackby integration real-time?

Stackby actions execute synchronously inside your workflow. Tiny Command waits for Stackby's API to confirm before continuing to the next step, so downstream nodes can rely on the result.

Do I need to write code to use Stackby with Tiny Command?

No. Every Stackby trigger and action is fully configurable from the visual workflow builder. For edge cases that aren't covered, drop in a custom HTTP node and call any Stackby API endpoint directly.

How much does the Stackby integration cost?

There's a free tier you can start on without a credit card. Higher run volumes and team features come with paid plans. The Stackby integration itself has no per-app surcharge.