ActionAmplitudeUpdated September 2026
How do I export Amplitude events for a date range?
Short answer: You can export events in Amplitude by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Amplitude Export Events action to a workflow, map its 2 inputs from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.
Inputs
The fields this action accepts.
Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.
| Field | Type | Required | Description |
|---|---|---|---|
Start (YYYYMMDDTHH) start | string | Required | 20260511T00 |
End (YYYYMMDDTHH) end | string | Required | – |
Sample request
{"start": "20260511T00","end": "{{trigger.end}}"}
Returns
"<gzipped archive>"
Use these fields in downstream nodes for routing, logging, or error handling.
Triggered by
Apps that pair well as the trigger for Export Events.
Any of these apps can fire this action as part of a workflow.
FAQ
Questions about Export Events.
What does the Export Events action do in Amplitude?
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.
What inputs does Export Events require?
Required: Start (YYYYMMDDTHH), End (YYYYMMDDTHH). Every input accepts a static value or a variable from any upstream node in your workflow.
Can I use dynamic inputs from earlier workflow nodes?
Yes. Any field on this action can pull values from upstream nodes, whether that's a form response, a trigger payload, an AI output, or a lookup result.
What happens if Amplitude returns an error?
The run history shows the failed step with its input and the error message Amplitude returned, so you can fix the input and run the workflow again. Automatic retries are built into HTTP steps only, where you can also set your own retry count and delay.
Does Export Events support batch operations?
Run Export Events inside a loop to process each item in an array. TinyCommand does not throttle calls for you, so for large arrays add a Delay step if you need to stay within Amplitude's rate limits.
More actions
Other Amplitude actions.
Action
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.
ActionSend 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.