Delete Entry

strapi.delete_entry
ActionBusiness appsconnection required

Calls the Strapi API with the connection's credentials.

Delete one entry of a content type by its document id.

Connection

Required
Yes — the node will not save without one
Auth type
API key
Providers
Strapi
Secret shape
the API token, or {"api_token": "…"}
Config it needs
base_url, collection
Resolved by
config.connection_id, else node.connection_id

Configuration

3 fields, 1 required. A dotted path is a nested object and name[] an array of objects — the editor renders the same tree.

FieldTypeRequiredDefaultConstraintsExample
collection
Plural API ID of the content type, as it appears in the URL, e.g. articles. Overrides the default content type on the connection.
stringNo——articles
document_id
Identifier of the entry: its documentId on Strapi 5, or its numeric id on Strapi 4.
stringYes——hgv1vny5cebq2l3czil1rpb3
locale
Locale code to act in, e.g. fr. Leave empty for the default locale.
stringNo——fr

Example configuration

Every value below is the contract’s own example or default — nothing invented.

{
  "collection": "articles",
  "document_id": "hgv1vny5cebq2l3czil1rpb3",
  "locale": "fr"
}

Output

One shape.

result

FieldTypeExample
entry
The entry Strapi returned, unwrapped from its data envelope.
object—
document_id
The entry's documentId, or its numeric id on Strapi 4.
string—
collection
The content type the entry belongs to.
string—
meta
Strapi's own meta object for this response.
object—
deleted
True once Strapi accepted the deletion.
boolean—
{
  "collection": "",
  "deleted": false,
  "document_id": "",
  "entry": {},
  "meta": {}
}

Notes

  • Strapi answers a deletion with 204 and no body; that is a success.

See Delete Entry run in a workflow.

In a technical demo we add the Strapi connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.