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.
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 | – |
{"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}}"}
{"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.
Any of these apps can fire this action as part of a workflow.