Skip to content
For LLMsView as Markdown·

Strapi ​

undefined

DetailValue
CategoryCMS
Base URLhttps://{your-strapi-host}/api
AuthenticationBearer Token
Endpoints7
Connector keystrapi

Using Strapi in a workflow ​

  1. Go to Connections and click New Connection.
  2. Pick Strapi from the marketplace.
  3. Enter your credentials (see Authentication above for what's expected).
  4. In a workflow, drop an API Call node and select this connection.
  5. Pick the operation you need from the Operation dropdown. The full list is below.

Available endpoints ​

EndpointSummary
GET List Entries
GET Create Entry
GET Update Entry
GET Delete Entry
GET Upload File
GET List Content Types
GET Get Current User

Each endpoint is documented in full below. Use the outline on the right to jump to one.

GET ​

List Entries

DetailValue
Operation IDlist_entries_0
MethodGET
Path``

Parameters ​

No parameters.

Using this endpoint in a workflow ​

  1. Add an API Call node to your workflow.
  2. Pick your Strapi connection from the Connection dropdown.
  3. In the Operation dropdown, select list_entries_0.
  4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns ​

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Strapi API reference.

GET ​

Create Entry

DetailValue
Operation IDcreate_entry_1
MethodGET
Path``

Parameters ​

No parameters.

Using this endpoint in a workflow ​

  1. Add an API Call node to your workflow.
  2. Pick your Strapi connection from the Connection dropdown.
  3. In the Operation dropdown, select create_entry_1.
  4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns ​

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Strapi API reference.

GET ​

Update Entry

DetailValue
Operation IDupdate_entry_2
MethodGET
Path``

Parameters ​

No parameters.

Using this endpoint in a workflow ​

  1. Add an API Call node to your workflow.
  2. Pick your Strapi connection from the Connection dropdown.
  3. In the Operation dropdown, select update_entry_2.
  4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns ​

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Strapi API reference.

GET ​

Delete Entry

DetailValue
Operation IDdelete_entry_3
MethodGET
Path``

Parameters ​

No parameters.

Using this endpoint in a workflow ​

  1. Add an API Call node to your workflow.
  2. Pick your Strapi connection from the Connection dropdown.
  3. In the Operation dropdown, select delete_entry_3.
  4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns ​

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Strapi API reference.

GET ​

Upload File

DetailValue
Operation IDupload_file_4
MethodGET
Path``

Parameters ​

No parameters.

Using this endpoint in a workflow ​

  1. Add an API Call node to your workflow.
  2. Pick your Strapi connection from the Connection dropdown.
  3. In the Operation dropdown, select upload_file_4.
  4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns ​

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Strapi API reference.

GET ​

List Content Types

DetailValue
Operation IDlist_content_types_5
MethodGET
Path``

Parameters ​

No parameters.

Using this endpoint in a workflow ​

  1. Add an API Call node to your workflow.
  2. Pick your Strapi connection from the Connection dropdown.
  3. In the Operation dropdown, select list_content_types_5.
  4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns ​

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Strapi API reference.

GET ​

Get Current User

DetailValue
Operation IDget_current_user_6
MethodGET
Path``

Parameters ​

No parameters.

Using this endpoint in a workflow ​

  1. Add an API Call node to your workflow.
  2. Pick your Strapi connection from the Connection dropdown.
  3. In the Operation dropdown, select get_current_user_6.
  4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns ​

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Strapi API reference.