ActionAmplitudeUpdated September 2026

How do I push an event to Amplitude?

Short answer: You can send event in Amplitude by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Amplitude Send Event action to a workflow, map its 5 inputs from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.

Send Event in Amplitude — start free All 3 Amplitude actions

Send Event in Amplitude — start free

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
Event Type event_type	string	Required	–
User ID user_id	string	Optional	–
Device ID device_id	string	Optional	–
Event Properties (JSON) event_properties	string	Optional	–
User Properties (JSON) user_properties	string	Optional	–

Sample request

{
  "event_type": "{{trigger.event_type}}",
  "user_id": "{{trigger.user_id}}",
  "device_id": "{{trigger.device_id}}",
  "event_properties": "{{trigger.event_properties}}",
  "user_properties": "{{trigger.user_properties}}"
}

Returns

{
  "code": 200,
  "events_ingested": 1,
  "payload_size_bytes": 50,
  "server_upload_time": 1620000000000
}

Use these fields in downstream nodes for routing, logging, or error handling.

Triggered by

Apps that pair well as the trigger for Send Event.

Any of these apps can fire this action as part of a workflow.

Google Sheets → Amplitude

2 Google Sheets triggers

HubSpot → Amplitude

18 HubSpot triggers

FAQ

Questions about Send Event.

What does the Send Event action do in Amplitude?

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.

What inputs does Send Event require?

Required: Event Type. 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 Send Event support batch operations?

Run Send Event 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

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.

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.

Send Event in Amplitude — start free