Appearance
Strapi
undefined
| Detail | Value |
|---|---|
| Category | CMS |
| Base URL | https://{your-strapi-host}/api |
| Authentication | Bearer Token |
| Endpoints | 7 |
| Connector key | strapi |
Using Strapi in a workflow
- Go to Connections and click New Connection.
- Pick Strapi from the marketplace.
- Enter your credentials (see Authentication above for what's expected).
- In a workflow, drop an API Call node and select this connection.
- Pick the operation you need from the Operation dropdown — the full list is below.
Available endpoints
| Endpoint | Summary |
|---|---|
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
| Detail | Value |
|---|---|
| Operation ID | list_entries_0 |
| Method | GET |
| Path | `` |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Strapi connection from the Connection dropdown.
- In the Operation dropdown, select
list_entries_0. - 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
| Detail | Value |
|---|---|
| Operation ID | create_entry_1 |
| Method | GET |
| Path | `` |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Strapi connection from the Connection dropdown.
- In the Operation dropdown, select
create_entry_1. - 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
| Detail | Value |
|---|---|
| Operation ID | update_entry_2 |
| Method | GET |
| Path | `` |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Strapi connection from the Connection dropdown.
- In the Operation dropdown, select
update_entry_2. - 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
| Detail | Value |
|---|---|
| Operation ID | delete_entry_3 |
| Method | GET |
| Path | `` |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Strapi connection from the Connection dropdown.
- In the Operation dropdown, select
delete_entry_3. - 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
| Detail | Value |
|---|---|
| Operation ID | upload_file_4 |
| Method | GET |
| Path | `` |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Strapi connection from the Connection dropdown.
- In the Operation dropdown, select
upload_file_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
| Detail | Value |
|---|---|
| Operation ID | list_content_types_5 |
| Method | GET |
| Path | `` |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Strapi connection from the Connection dropdown.
- In the Operation dropdown, select
list_content_types_5. - 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
| Detail | Value |
|---|---|
| Operation ID | get_current_user_6 |
| Method | GET |
| Path | `` |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Strapi connection from the Connection dropdown.
- In the Operation dropdown, select
get_current_user_6. - 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.