Start free
ActionCrispUpdated June 2026

How do I send a Crisp message?

Short answer: You can send message in Crisp by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Crisp Send Message action to a workflow, map its 3 inputs from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.

Use this actionAll 4 Crisp actions
Inputs

The fields this action accepts.

Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.

FieldTypeRequiredDescription
Session ID
session_id
stringRequiredThe conversation session ID
Message
content
stringRequiredMessage. e.g. "Hello! How can we help?"
Message Type
type
optionsOptionalMessage Type. Options: Text, Note (internal)
Sample request
{
  "session_id": "e.g. session_abc123",
  "content": "Hello! How can we help?",
  "type": "{{trigger.type}}"
}
Returns
{
  "from": "operator",
  "content": "Hello!",
  "timestamp": 1700000000,
  "fingerprint": 123456789
}

Use these fields in downstream nodes for routing, logging, or error handling.

Triggered by

Apps that pair well as the trigger for Send Message.

Any of these apps can fire this action as part of a workflow.

Gmail → Crisp
1 Gmail triggers
Slack → Crisp
13 Slack triggers
Google Sheets → Crisp
2 Google Sheets triggers
HubSpot → Crisp
18 HubSpot triggers
FAQ

Questions about Send Message.

What does the Send Message action do in Crisp?
Posts a customer-facing reply or an internal team note (type=note). Routes via the conversation's original channel by default. For posting AI context as internal note or for automated replies on low-complexity tickets.
What inputs does Send Message require?
Required: Session ID, Message. Every input accepts a static value or a variable from any upstream node in your workflow.
Can I use dynamic inputs from earlier workflow nodes?
Yes. Any field on this action can pull values from upstream nodes, whether that's a form response, a trigger payload, an AI output, or a lookup result.
What happens if Crisp returns an error?
The workflow pauses on the failed node, the error message is captured in the run log, and you can retry the run with one click. Auto-retry policies are configurable per workflow with exponential backoff up to 5 attempts.
Does Send Message support batch operations?
Yes. Run Send Message inside a Loop node to process arrays. TinyCommand handles Crisp's rate limits automatically so you don't have to throttle manually.
More actions

Other Crisp actions.

Action
Get Conversation
Returns the conversation with message history, customer profile, and metadata. The standard lookup for workflows that received a conversation ID via webhook and need richer context.
Action
List Conversations
Paginated conversations with filters by state, segments, channel. Useful for triage workflows ("show me open conversations assigned to no one") and for capacity reporting.
Action
Resolve Conversation
Transitions a conversation to resolved state — the standard close-out. Useful for "AI judge agrees customer is satisfied → auto-resolve" workflows or for bulk-resolve maintenance on inactive conversations.