AnalyticsReal-timeUpdated May 2026

Amplitude

Amplitude product analytics events and export

Amplitude is the product-analytics platform — event tracking, funnels, retention, cohorts, dashboards — used by product teams to understand user behaviour. Tiny Command exposes three actions, no triggers (Amplitude is the destination for events, not a source; for "react to a behavioural cohort" workflows, use Amplitude's Behavioral Cohort sync feature pointing at a downstream destination): Send Event (push a discrete event into Amplitude — user_id, event_type, event_properties, user_properties), Identify User (upsert user properties — the user-state update), Export Events (paginated raw-event export by time range — useful for daily batch-load workflows into a warehouse, or for "what happened in the last hour" forensics). The connection uses an Amplitude API key + Secret key from Project Settings → API keys. The HTTP V2 API used by Send Event accepts batches of up to 1000 events per call for efficient bulk ingestion. Most workflows track events server-side (via Tiny Command) for events that don't fit a client SDK — webhook-triggered states, server-side actions, async backend events.

Connect Amplitude

0triggers

3actions

≈ 2 minto set up

Freetier · no card

Actions

Do anything Amplitude 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
Export Events	Returns raw events for a specified time window — useful for daily warehouse loads, ad-hoc forensics, or one-off cohort analyses. Events become available 5-15 minutes after ingestion, so for real-time reaction workflows this is the wrong tool; for batch ETL into a warehouse, this is the right one.	2 fields	View →
Identify User	Upserts user-level properties (plan, country, signup_date) on the Amplitude user record. Drives segmentation in dashboards and cohorts. Use $set_once for properties that should only set on first encounter (signup_date) — $set overwrites on every call.	2 fields	View →
Send Event	Sends a behavioural event into Amplitude with user_id, event_type, properties, and timestamp. The base hook for server-side tracking — events that don't fire from the client SDK (webhook-triggered states, async backend events, scheduled jobs). For bulk historical loads, use the Import endpoint instead.	5 fields	View →

Recipes

Pre-built Amplitude workflows.

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

Amplitude → Slack alerts

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

Amplitude → Google Sheets log

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

Amplitude → Notion database

Turn Amplitude 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 Amplitude 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 Amplitude 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 Amplitude integration.

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

How do I connect Amplitude to Tiny Command?

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

What Amplitude triggers does Tiny Command support?

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

What Amplitude actions can I run from a workflow?

3 Amplitude actions are available out of the box, covering analytics operations like "Export Events". Every action accepts dynamic inputs from upstream nodes, whether that's a search result, an AI output, or a form field.

Is the Amplitude integration real-time?

Amplitude actions execute synchronously inside your workflow. Tiny Command waits for Amplitude'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 Amplitude with Tiny Command?

No. Every Amplitude 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 Amplitude API endpoint directly.

How much does the Amplitude 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 Amplitude integration itself has no per-app surcharge.