ActionStrapiUpdated September 2026

How do I create a Strapi entry?

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.

Create Strapi Entry in Strapi — start free All 5 Strapi actions

Create Strapi Entry in Strapi — start free

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
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

Sample request

{
  "content_type": "e.g. articles",
  "data": "{\"title\": \"New Article\", \"body\": \"Content here...\", \"published\": true}"
}

Returns

{
  "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.

Triggered by

Apps that pair well as the trigger for Create Strapi Entry.

Any of these apps can fire this action as part of a workflow.

Google Sheets → Strapi

2 Google Sheets triggers

HubSpot → Strapi

18 HubSpot triggers

FAQ

Questions about Create Strapi Entry.

What does the Create Strapi Entry action do in Strapi?

Inserts a new entry into a Strapi content type. For "external content → push to Strapi CMS" sync workflows.

What inputs does Create Strapi Entry require?

Required: Content Type (plural), Entry Data (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 Strapi returns an error?

The run history shows the failed step with its input and the error message Strapi returned, so you can fix the input and run the workflow again. Automatic retries are built into HTTP steps only, where you can also set your own retry count and delay.

Does Create Strapi Entry support batch operations?

Run Create Strapi Entry inside a loop to process each item in an array. TinyCommand does not throttle calls for you, so for large arrays add a Delay step if you need to stay within Strapi's rate limits.

More actions