Short answer: You can send loops event in Loops by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Loops Send Loops Event action to a workflow, map its 3 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 |
|---|---|---|---|
Contact Email email | Required | The email address. Used as the recipient or identifier depending on context. | |
Event Name eventName | string | Required | Event Name. e.g. "user_signed_up" |
Event Properties eventProperties | json | Optional | Event Properties. (JSON object). e.g. "{"plan":"pro"}" |
{"email": "e.g. user@example.com","eventName": "user_signed_up","eventProperties": "{\"plan\":\"pro\"}"}
{"success": true}
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.