Send Message: Crisp action

Inputs

The fields this action accepts.

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

Field	Type	Required	Description
Session ID session_id	string	Required	The conversation session ID
Message content	string	Required	Message. e.g. "Hello! How can we help?"
Message Type type	options	Optional	Message 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.

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. Tiny Command handles Crisp's rate limits automatically so you don't have to throttle manually.

More actions