Appearance
Crisp
undefined
| Detail | Value |
|---|---|
| Category | Support |
| Base URL | https://api.crisp.chat/v1 |
| Authentication | API Key |
| Endpoints | 6 |
| Connector key | crisp |
Using Crisp in a workflow
- Go to Connections and click New Connection.
- Pick Crisp 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 Conversations |
GET | Send Message |
GET | List People |
GET | List Operators |
GET | Get Availability |
GET | List Helpdesk Articles |
Each endpoint is documented in full below. Use the outline on the right to jump to one.
GET
List Conversations
| Detail | Value |
|---|---|
| Operation ID | list_conversations_0 |
| Method | GET |
| Path | `` |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Crisp connection from the Connection dropdown.
- In the Operation dropdown, select
list_conversations_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 Crisp API reference.
GET
Send Message
| Detail | Value |
|---|---|
| Operation ID | send_message_1 |
| Method | GET |
| Path | `` |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Crisp connection from the Connection dropdown.
- In the Operation dropdown, select
send_message_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 Crisp API reference.
GET
List People
| Detail | Value |
|---|---|
| Operation ID | list_people_2 |
| Method | GET |
| Path | `` |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Crisp connection from the Connection dropdown.
- In the Operation dropdown, select
list_people_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 Crisp API reference.
GET
List Operators
| Detail | Value |
|---|---|
| Operation ID | list_operators_3 |
| Method | GET |
| Path | `` |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Crisp connection from the Connection dropdown.
- In the Operation dropdown, select
list_operators_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 Crisp API reference.
GET
Get Availability
| Detail | Value |
|---|---|
| Operation ID | get_availability_4 |
| Method | GET |
| Path | `` |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Crisp connection from the Connection dropdown.
- In the Operation dropdown, select
get_availability_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 Crisp API reference.
GET
List Helpdesk Articles
| Detail | Value |
|---|---|
| Operation ID | list_helpdesk_articles_5 |
| Method | GET |
| Path | `` |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Crisp connection from the Connection dropdown.
- In the Operation dropdown, select
list_helpdesk_articles_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 Crisp API reference.