Update Strapi Entry: Strapi action

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	Content Type (plural). Example: articles
Entry ID entry_id	string	Required	Entry ID. Example: 1
Update Data (JSON) data	string	Required	Update Data (JSON). e.g. "{"title": "Updated Title"}"

Sample request

{
  "content_type": "e.g. articles",
  "entry_id": "e.g. 1",
  "data": "{\"title\": \"Updated Title\"}"
}

Returns

{
  "data": {
    "id": 1,
    "attributes": {
      "title": "Updated Title"
    }
  }
}

Use these fields in downstream nodes for routing, logging, or error handling.

FAQ

Questions about Update Strapi Entry.

What does the Update Strapi Entry action do in Strapi?

Partial update on entry fields. For "external system changed → reflect in CMS" sync patterns.

What inputs does Update Strapi Entry require?

Required: Content Type (plural), Entry ID, Update 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 workflow pauses on the failed node, the error message is captured in the run log, and you can retry the run with one click. Auto-retry policies are configurable per workflow with exponential backoff up to 5 attempts.

Does Update Strapi Entry support batch operations?

Yes. Run Update Strapi Entry inside a Loop node to process arrays. Tiny Command handles Strapi's rate limits automatically so you don't have to throttle manually.

More actions