ActionAmplitudeUpdated June 2026

How do I update user properties in Amplitude?

Short answer: You can identify user in Amplitude by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Amplitude Identify User 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.

Use this action All 3 Amplitude actions

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
User ID user_id	string	Required	–
User Properties (JSON) user_properties_json	string	Required	–

Sample request

{
  "user_id": "{{trigger.user_id}}",
  "user_properties_json": "{{trigger.user_properties_json}}"
}

Returns

"success"

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

FAQ

Questions about Identify User.

What does the Identify User action do in Amplitude?

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.

What inputs does Identify User require?

Required: User ID, User Properties (JSON). 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 workflow pauses on the failed node, the error message is captured in the run log, and you can retry the run with one click. Auto-retry policies are configurable per workflow with exponential backoff up to 5 attempts.

Does Identify User support batch operations?

Yes. Run Identify User inside a Loop node to process arrays. TinyCommand handles Amplitude's rate limits automatically so you don't have to throttle manually.

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.