Start free
ChangelogNewest first

What just shipped.

Every meaningful change to TinyCommand: product launches, new integrations, performance wins and fixes. Newest first, each one dated.

TinyDiscovery: describe your buyer, get the list

Describe who you sell to in plain words and get companies or people, each checked against the brief and added to a table. Priced per row.

Write the brief the way you would explain it to a colleague: who they are, where they are, and anything else that makes them a fit. Discovery picks where to look from the shape of that brief, pools candidates, and checks each one against what you asked for before anything reaches you.
Candidates that fail a defining criterion, such as what they are or where they are, are dropped rather than handed over. A signal from your brief that it cannot confirm ranks the row lower instead of removing it. You review the matches, tick the ones you want, and they are added as rows in TinyTables.
It finds companies or the people inside them, and creators where they post: name Instagram, YouTube, TikTok or X and the people search runs on that platform. People search reads search results, mostly LinkedIn result snippets, and never opens a profile page, so a person's details are only as good as what the result shows.
Pricing is per record, set by what you search for: 20 credits for local businesses, 10 for agencies, 10 for people and 20 for influencers. There is no licensed contact database underneath and no per-seat licence.
TCTinyCommand Team
Read full notes →

The products menu, rebuilt

The menu now fits on a laptop screen, reads in the order the work happens, and puts Discovery first. The top bar went from ten items to six.

The old products menu was 837px tall. On a 1440x900 laptop its last group sat below the bottom of the screen, and because a hover menu can't scroll, nothing there could be clicked. The new one is about 490px and fits every laptop size we test against.
It reads left to right in the order the work happens: find who to sell to, capture it and keep it, stop doing it by hand, look after your customers. SEO and AI visibility sit in their own strip underneath.
The top bar dropped from ten items to six: Products, Solutions, Pricing and Book a demo, plus Log in and Start free. Superpowers, Co-Founder and Integrations moved inside the Products menu.
The menu and the mobile menu now work from a keyboard, and the German, Spanish and Portuguese versions of the site are translated again.
TCTinyCommand Team
Read full notes →

The site now lists every product we actually ship

The marketing site advertised five products while the app shipped eleven. New /products index, and the nav, footer and sitemap now read from one registry.

For several months tinycommand.com sold Forms, Workflows, Agents, Tables and Email while the dashboard shipped eleven products. Discovery, Campaigns, SEO, AI visibility, Portals and Enrichment had no product page.
There is now a /products index, a page for each product that was missing, and a single product registry that the header, the footer, the hub and the sitemap all read from — so a product added to the app can no longer go unlisted on the site.
SEO and enrichment moved out of Superpowers and became products in their own right, matching how the app bills them. The old /superpowers/seo and /superpowers/enrichment URLs redirect to the new pages.
Every one of the new pages carries a "what this is not" section, and every claim on them was checked against the running product rather than its documentation. That check also caught older copy: the TinyEmails page said opens and clicks were written back to the source record, which nothing does. It has been corrected.
TCTinyCommand Team
Read full notes →

TinySEO and TinyAnswers: search and AI visibility, inside TinyCommand

Eleven SEO tools and fifteen AI-visibility tools, on the same login as your forms, tables and workflows. No separate seat.

TinySEO brings rank tracking, backlinks, site audits, keyword research, competitor gap analysis and Search Console reporting into TinyCommand. Site Explorer alone covers eleven views of a domain: organic keywords, top pages, backlinks, new and lost links, referring domains, anchors and broken links.
TinyAnswers is the other half of the same app. It checks whether ChatGPT, Gemini, Perplexity, Claude and Google AI Overviews actually name your brand when someone asks — with citation tracking, share of voice, an AI-readiness grade, and a robots.txt audit across twenty AI crawlers.
A note on how the AI checks work, because it matters: we query the engines through their APIs with web search enabled, and label every one of those runs "Sampled". It is a close, reproducible stand-in for a real chat, not a recording of one person's logged-in session. Google AI Overviews is captured from the live SERP and labelled differently.
Both are cache-first, so re-reading a report you already pulled costs nothing, and each project has a hard daily spend cap so one domain can't run away with your credits.
TCTinyCommand Team
Read full notes →

TinyPortal: give clients a login to their own data

Build a login-gated portal on a TinyTables view, publish it to your own domain, and let each customer see only their rows.

TinyPortal turns a table you already keep into a customer-facing portal. Eighteen block types — tables, lists, detail views, stats, charts, calendars, kanban, maps, pivots, embedded forms — all bound to a view you choose.
Row scoping is the part that matters. Point a block at an owner column and each signed-in customer sees their records and nobody else's, enforced on the server before anything is sent. Every data binding is stripped from the published payload.
End-users sign in with an email and password, or with credentials held as rows in a Users table you control. Add a hostname, verify the DNS records, and it serves over SSL on your domain.
Publishing takes an immutable snapshot after a completeness and safety review, so you can roll back to any earlier version without touching your draft.
TCTinyCommand Team
Read full notes →

TinyCampaigns: broadcast email from a domain that's yours

Send to a TinyTables audience from your own DKIM-verified domain, with a fail-closed consent gate and automatic suppression.

TinyCampaigns is the sending machinery that sits behind the templates you design in TinyEmails: audience resolution, a durable per-recipient queue, throttling, your own sending domain, suppression, bounce handling and reporting.
Verify a domain once with three DKIM records and every address on it becomes a valid sender. Name a consent column on your table and the gate is fail-closed — a row has to match an allowed value to be queued at all.
Hard bounces, complaints and unsubscribes suppress themselves, and the suppression list is checked twice: once when the audience is built and again immediately before each message goes out. Unsubscribe is RFC 8058 one-click, so Gmail and Outlook show the native button.
If bounces pass 5% or complaints pass 0.1% after fifty sends, the campaign pauses itself rather than burning your domain reputation.
TCTinyCommand Team
Read full notes →

TinyEnricher: nine lookups, as a table column

Company details from a domain, people from a name, email addresses with deliverability checks — priced per row, free on a miss.

Add an enrichment column to a table and it fills in the rest: company details from a domain, person details from a name, an email address, deliverability checks, people by role, reverse lookup from an email, social profiles and more.
Credits are charged per record and only when the lookup actually writes a value. A no-match costs nothing. Turn on auto-enrich and anything arriving from a form, a workflow or an import gets filled in on the way.
Worth being straight about the source: this is not a licensed B2B database. There is no Apollo, ZoomInfo or Clearbit underneath. Everything is found on the public web and structured by a model, which is why it costs a fraction of those and why coverage varies. Inferred answers are marked inferred in the product rather than dressed up as verified facts.
TCTinyCommand Team
Read full notes →

Pipedrive and Keap triggers ship with shape-validated payloads

Every Pipedrive and Keap trigger now ships with a typed output shape — flatten, filter, and map fields with zero guesswork.

We've finished rolling out shape-validated outputs across the Pipedrive and Keap integrations. Every trigger now publishes a typed payload schema, with sample data and per-field types surfaced inline in the workflow builder.
Why it matters: building automations against Pipedrive's `deal.added` or Keap's `contact.created` used to mean writing custom JSON expressions to dig into nested fields. With shapes, every field is a top-level variable in the expression editor.
Under the hood: this is the same shape framework that powers our Pipedrive end-to-end test runner. The 18 Pipedrive deal fields and 11 Keap contact fields are now type-checked at build time.
TCTinyCommand Team
Read full notes →

ActiveCampaign + ClickUp trigger update

We moved ActiveCampaign and ClickUp triggers to real-time webhooks. No more polling, no more 15-minute lag.

We've rebuilt the ActiveCampaign and ClickUp trigger surface on top of their official webhook APIs. Triggers fire within seconds of the event instead of running on a polling schedule.
Triggers in the catalog today: ActiveCampaign — Contact Added, Contact Added to List, Deal Created, Deal Updated, Tag Added to Contact. ClickUp — Comment Posted, New List, New Task, Task Deleted, Task Status Updated, Task Updated.
Existing workflows continue working unchanged. New workflows get the lower-latency, lower-API-cost path.
TCTinyCommand Team
Read full notes →

JotForm webhooks ship with the right Content-Type

JotForm's webhook receiver rejects `application/json` bodies. The Tiny Command SDK now respects the requested Content-Type and sends `application/x-www-form-urlencoded` when JotForm asks for it.

JotForm's registration endpoint always returned `WebHook URL is wrong` even when the URL was clearly valid. The cause: our SDK was sending JSON when JotForm expects form-urlencoded.
Now: the SDK's `registerTrigger` honors per-app Content-Type configuration. Other apps with non-JSON registration APIs benefit too.
TCTinyCommand Team
Read full notes →

Asana triggers no longer require manual webhook setup

Five stacked fixes — Lambda X-Hook-Secret handling, schema rewrite, SDK fanOut patching, OAuth provider backfill, IM cache invalidation — and Asana triggers register themselves end-to-end.

Setting up an Asana trigger used to require visiting Asana's developer console and pasting a webhook URL. That's gone — Tiny Command now negotiates Asana's X-Hook-Secret handshake and registers the webhook on your behalf.
The fix touched five layers: trigger-enabler Lambda, schema definitions, the SDK's fanOut source, OAuth provider config, and the integration manager's cache invalidation logic.
TCTinyCommand Team
Read full notes →