Crisp
Crisp shared inbox conversation actions
Crisp is the customer-messaging platform that gives small teams a unified inbox across live chat, email, Messenger, WhatsApp, and Twitter — popular as a friendlier-priced Intercom alternative for SMB and early-stage SaaS. Tiny Command exposes four actions, no triggers (Crisp emits real-time events via WebSockets or via webhooks configured in the Crisp marketplace; for HTTP webhooks, configure them to fire at a Tiny Command webhook trigger URL): List Conversations (paginated, with filter by state, segments, channel), Get Conversation (full message history, customer profile, channel metadata), Send Message (operator reply on a conversation — the customer-facing path), Resolve Conversation (transition to resolved, the standard close-out). The connection uses Crisp's plugin tokens (server-side identifier + key pair scoped to a specific Crisp website). The website context matters — Crisp organises customers and conversations by "website" which is the org-level container; multi-product orgs typically have one Crisp website per product.
Do anything Crisp can do, from a workflow.
Every action accepts dynamic inputs from upstream nodes, whether that's an AI output, a form field, or a search result.
| Action | What it does |
|---|---|
| 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. |
| 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. |
| 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. |
| Send Message | 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. |
Pre-built Crisp workflows.
Clone any recipe and customize it in one click. Every recipe is fully editable.
Three things worth knowing.
Tiny Command counts a run the moment a trigger fires. Filtering early means only matching events spend your usage budget.
Connect Crisp once and every workflow on your account can use its triggers and actions. You don't have to re-auth per workflow.
Every Crisp field shows up in the visual picker for downstream nodes. The raw payload is there for power users, optional for everyone else.
Questions about the Crisp integration.
If we missed yours, ping support. We usually reply within an hour.
How do I connect Crisp to Tiny Command?
What Crisp triggers does Tiny Command support?
What Crisp actions can I run from a workflow?
Is the Crisp integration real-time?
Do I need to write code to use Crisp with Tiny Command?
How much does the Crisp integration cost?
More customer support apps people connect.
Same category as Crisp, ordered by how often teams pair them. Hover the carousel to pause.
Do more with Crisp.
Wire it to Slack, Notion, HubSpot, Stripe, or any of the other 438 apps in our catalog. Setup takes roughly two minutes. Free to try, no credit card.
