Skip to content
← Back to documentation
Technical Reference

Crisp

Crisp integration for Flows360 workflows.

CategoryCustomer Support
Authenticationcustom
Version0.2.0
Published scopes0 published scopes
Last updatedSeptember 19, 2026

Overview

Connect Crisp with Flows360

Crisp integration for Flows360 workflows.

Use the Crisp connector to include its declared actions and events in Flows360 workflows without duplicating the integration logic inside each consuming system. This pinned connector version currently exposes 7 actions and 2 triggers.

Available actions

  • Add Note to Conversation
  • Create Conversation
  • Create/Update Contact
  • Change Conversation State
  • Find Conversation
  • Find User Profile
  • Custom API Call

Available triggers

  • New Contact Created
  • New Conversation Created

The capability list above is generated from the exact reviewed connector package so the public description stays aligned with the version Flows360 operates.

Technical guide

Technical reference

Package identity

  • Connector: Crisp
  • Package: @activepieces/piece-crisp@0.2.0
  • Exact artifact digest: sha256:672be0c90c06a90a843da82620c223f1e742af16a6a6f192a4c2d9278296db04
  • Runtime: Activepieces-compatible deterministic worker
  • Source: the exact reviewed Activepieces source

Authentication

CUSTOM AUTH. Connection values are tenant-specific and remain in the consuming Studio instance; CDK stores definitions and field metadata, not customer credential values.

Action contracts

  • Add Note to Conversation (add_note), Adds an internal note to a conversation. Classification: read.
  • Create Conversation (create_conversation), Creates a new conversation. Classification: read.
  • Create/Update Contact (create_update_contact), Creates a new contact or updates an existing contact. Classification: read.
  • Change Conversation State (change_state), Updates the state of a conversation. Classification: read.
  • Find Conversation (find_conversation), Searches for conversations matching the specified criteria. Classification: read.
  • Find User Profile (find_user_profile), Finds a user profile by email address. Classification: read.
  • Custom API Call (custom_api_call), Make a custom API call to a specific endpoint Classification: read.

Trigger contracts

  • New Contact Created, polling.
  • New Conversation Created, polling.

Verification

Deterministic execution evidence is recorded for the pinned artifact, including 1 exercised action entrypoint and 0 exercised trigger entrypoints.

Capability summary

Authenticationcustom
Supported objects9
Supported actions7
Triggers2

Authentication

Authentication method: custom

Authentication profiles

connection · custom
  • Identifier Required · protected credential
  • Key Required · protected credential

Supported objects

ObjectReadWriteNotes
Add Note to Conversation Yes No Adds an internal note to a conversation.
Create Conversation Yes No Creates a new conversation.
Create/Update Contact Yes No Creates a new contact or updates an existing contact.
Change Conversation State Yes No Updates the state of a conversation.
Find Conversation Yes No Searches for conversations matching the specified criteria.
Find User Profile Yes No Finds a user profile by email address.
Custom API Call Yes No Make a custom API call to a specific endpoint
New Contact Created Yes No polling trigger declared by the pinned package.
New Conversation Created Yes No polling trigger declared by the pinned package.

Supported actions

Add Note to Conversation · Read

Adds an internal note to a conversation.

add_note · Risk: low · Retry: safe

Inputs

  • websiteId · string · Required, You can obtain website ID by navigating to Settings -> Workspace Settings -> Setup & Integrations.
  • sessionId · string · Required, You can obtain session from URL address bar.It starts with 'session_'.
  • content · string · Required
Create Conversation · Read

Creates a new conversation.

create_conversation · Risk: low · Retry: safe

Inputs

  • websiteId · string · Required, You can obtain website ID by navigating to Settings -> Workspace Settings -> Setup & Integrations.
  • email · string · Required
  • username · string · Required
  • messageFrom · string · Required
  • message · string · Required
Create/Update Contact · Read

Creates a new contact or updates an existing contact.

create_update_contact · Risk: low · Retry: safe

Inputs

  • websiteId · string · Required, You can obtain website ID by navigating to Settings -> Workspace Settings -> Setup & Integrations.
  • email · string · Required
  • name · string · Required
  • phone · string · Optional
  • address · string · Optional
  • company · string · Optional
  • website · string · Optional
  • notepad · string · Optional
Change Conversation State · Read

Updates the state of a conversation.

change_state · Risk: low · Retry: safe

Inputs

  • websiteId · string · Required, You can obtain website ID by navigating to Settings -> Workspace Settings -> Setup & Integrations.
  • sessionId · string · Required, You can obtain session from URL address bar.It starts with 'session_'.
  • state · string · Required
Find Conversation · Read

Searches for conversations matching the specified criteria.

find_conversation · Risk: low · Retry: safe

Inputs

  • websiteId · string · Required, You can obtain website ID by navigating to Settings -> Workspace Settings -> Setup & Integrations.
  • searchQuery · string · Required
Find User Profile · Read

Finds a user profile by email address.

find_user_profile · Risk: low · Retry: safe

Inputs

  • websiteId · string · Required, You can obtain website ID by navigating to Settings -> Workspace Settings -> Setup & Integrations.
  • email · string · Required, The email address of the user to find.
Custom API Call · Read

Make a custom API call to a specific endpoint

custom_api_call · Risk: low · Retry: safe

Inputs

  • url · object · Required
  • method · string · Required
  • headers · object · Optional, Authorization headers are injected automatically from your connection.
  • queryParams · object · Optional, Appended to the URL as ?key=value.
  • body_type · string · Optional
  • body · object · Optional
  • response_is_binary · boolean · Optional, Enable for files like PDFs, images, etc.
  • failsafe · boolean · Optional, On a failed request, output the error instead of failing the step.
  • timeout · number · Optional, Seconds to wait for a response. Empty: up to the flow limit (10 min).
  • followRedirects · boolean · Optional, Follow 3xx redirects instead of returning them as the response.

Triggers

New Contact Created · Poll

Triggers when a new contact is added.

Inputs

  • websiteId · string
New Conversation Created · Poll

Triggers when a new conversation is started.

Inputs

  • websiteId · string

Setup

Setup

  1. Add the Crisp connector to the workflow in the target Flows360 Studio instance.
  2. Create or select the tenant-specific connection required by the connector. Connection secrets remain in the Studio connection boundary and are not copied into CDK documentation.
  3. Provide the connection fields declared by the pinned package:
  • Identifier (identifier), required; stored as a sensitive connection value.
  • Key (token), required; stored as a sensitive connection value.
  1. Select the required action or trigger and complete its declared input fields. Required and optional inputs are defined by the exact package schema.
  2. Test the workflow in the appropriate environment before enabling production scheduling or event delivery.

Limitations

Limitations and operational notes

  • This content describes @activepieces/piece-crisp@0.2.0; provider behaviour can change independently and should be revalidated when the provider or connector version changes.
  • Only the 7 actions and 2 triggers declared by this pinned package are represented here.
  • Tenant credentials and connection values are not stored in the public connector record.
  • Provider-side permissions, account entitlements, quotas and rate limits remain subject to the connected provider account and are not inferred when the package does not declare them.
  • Deterministic execution evidence is recorded for the pinned artifact, including 1 exercised action entrypoint and 0 exercised trigger entrypoints.

Troubleshooting

Why canu2019t the connector authenticate?

Check the tenant connection in Studio and confirm every required Crisp connection field is present. Re-authorise OAuth-based connections if the provider token or consent has expired. Do not place credential values in CDK content or logs.

Why is an action or trigger unavailable?

Confirm that the workflow is using @activepieces/piece-crisp@0.2.0 and compare the requested capability with the declared action and trigger list for this version. A capability that is not declared by the pinned package should not be presented as supported.

What should I check after a provider-side change?

Revalidate authentication, required fields, action/trigger behaviour and provider documentation before publishing refreshed connector content or moving a new package version into production.