Short answer: You can create strapi entry in Strapi by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Strapi Create Strapi Entry 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 |
|---|---|---|---|
Content Type (plural) content_type | string | Required | API ID of the content type in plural form |
Entry Data (JSON) data | string | Required | JSON object with field values matching your content type schema |
{"content_type": "e.g. articles","data": "{\"title\": \"New Article\", \"body\": \"Content here...\", \"published\": true}"}
{"data": {"id": 1,"attributes": {"body": "Content here...","title": "New Article","createdAt": "2025-01-15T12:00:00.000Z"}}}
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.