Short answer: You can get directus item in Directus by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Directus Get Directus Item 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.
Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.
| Field | Type | Required | Description |
|---|---|---|---|
Collection Name collection | string | Required | Collection Name. Example: articles |
Item ID item_id | string | Required | Item ID. Example: 1 |
{"collection": "e.g. articles","item_id": "e.g. 1"}
{"data": {"id": 1,"title": "Article 1","status": "published"}}
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.