Skip to content
For LLMsView as Markdown·

Crisp

undefined

DetailValue
CategorySupport
Base URLhttps://api.crisp.chat/v1
AuthenticationAPI Key
Endpoints6
Connector keycrisp

Using Crisp in a workflow

  1. Go to Connections and click New Connection.
  2. Pick Crisp 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 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

DetailValue
Operation IDlist_conversations_0
MethodGET
Path``

Parameters

No parameters.

Using this endpoint in a workflow

  1. Add an API Call node to your workflow.
  2. Pick your Crisp connection from the Connection dropdown.
  3. In the Operation dropdown, select list_conversations_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 Crisp API reference.

GET

Send Message

DetailValue
Operation IDsend_message_1
MethodGET
Path``

Parameters

No parameters.

Using this endpoint in a workflow

  1. Add an API Call node to your workflow.
  2. Pick your Crisp connection from the Connection dropdown.
  3. In the Operation dropdown, select send_message_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 Crisp API reference.

GET

List People

DetailValue
Operation IDlist_people_2
MethodGET
Path``

Parameters

No parameters.

Using this endpoint in a workflow

  1. Add an API Call node to your workflow.
  2. Pick your Crisp connection from the Connection dropdown.
  3. In the Operation dropdown, select list_people_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 Crisp API reference.

GET

List Operators

DetailValue
Operation IDlist_operators_3
MethodGET
Path``

Parameters

No parameters.

Using this endpoint in a workflow

  1. Add an API Call node to your workflow.
  2. Pick your Crisp connection from the Connection dropdown.
  3. In the Operation dropdown, select list_operators_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 Crisp API reference.

GET

Get Availability

DetailValue
Operation IDget_availability_4
MethodGET
Path``

Parameters

No parameters.

Using this endpoint in a workflow

  1. Add an API Call node to your workflow.
  2. Pick your Crisp connection from the Connection dropdown.
  3. In the Operation dropdown, select get_availability_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 Crisp API reference.

GET

List Helpdesk Articles

DetailValue
Operation IDlist_helpdesk_articles_5
MethodGET
Path``

Parameters

No parameters.

Using this endpoint in a workflow

  1. Add an API Call node to your workflow.
  2. Pick your Crisp connection from the Connection dropdown.
  3. In the Operation dropdown, select list_helpdesk_articles_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 Crisp API reference.