EmailReal-timeUpdated May 2026

Kustomer

Kustomer omnichannel customer service

Kustomer is the customer-service platform that won by treating the customer (not the ticket) as the primary unit — a single timeline per customer across email, chat, SMS, social, plus structured data fields and lifecycle events. Tiny Command exposes four actions, no triggers (Kustomer has comprehensive outbound webhooks configured in admin Settings → Webhooks; point them at a Tiny Command webhook trigger for customer-created, conversation-created, message-created events): Create Customer (with email, phone, name, custom attributes, and tags), Search Customers (the lookup-before-create pattern; Kustomer's full-text search across customer attributes), Create Conversation (open a new conversation for a customer — choose the channel: email, chat, SMS), Create Message (post a message into an existing conversation, customer-visible or internal note). The connection uses a Kustomer API key (per-org, from Settings → Security → API Keys) with the right role permissions for the actions called.

Connect Kustomer

0triggers

4actions

≈ 2 minto set up

Freetier · no card

Actions

Do anything Kustomer 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	Inputs
Create Kustomer Conversation	Opens a new conversation for a customer on a specified channel (email, chat, SMS). For "external support channel → file in Kustomer" or proactive-outreach workflows.	4 fields	View →
Create Kustomer Customer	Inserts a new customer with email, phone, name, custom attributes. For "new lead → push to Kustomer so they're primed when they next contact us" sync workflows.	3 fields	View →
Send Kustomer Message	Posts a customer-facing message (out) or internal note. For "AI-summarised context → log as internal note" or "automated reply on routine ticket types" workflows.	4 fields	View →
Search Kustomer Customers	Full-text search across customer attributes. For "find customer by email" lookups or for "all customers in this segment" queries.	1 fields	View →

Recipes

Pre-built Kustomer workflows.

Clone any recipe and customize it in one click. Every recipe is fully editable.

Kustomer → Slack alerts

AI-triage every Kustomer event, ping the right channel only when it matters.

Kustomer → Google Sheets log

Every event matching a filter, appended to a running spreadsheet.

Kustomer → Notion database

Turn Kustomer into a Notion-backed source of truth, auto-tagged.

Before you build

Three things worth knowing.

Filter at the trigger

Tiny Command counts a run the moment a trigger fires. Filtering early means only matching events spend your usage budget.

Authorize once, reuse anywhere

Connect Kustomer once and every workflow on your account can use its triggers and actions. You don't have to re-auth per workflow.

No JSON to read

Every Kustomer field shows up in the visual picker for downstream nodes. The raw payload is there for power users, optional for everyone else.

FAQ

Questions about the Kustomer integration.

If we missed yours, ping support. We usually reply within an hour.

How do I connect Kustomer to Tiny Command?

Open the Tiny Command workflow builder, drop in a Kustomer node, and click Connect. Authorize Kustomer once and any workflow on your account can use its triggers and actions. Most teams finish the connection in under two minutes.

What Kustomer triggers does Tiny Command support?

Tiny Command focuses on outbound actions for Kustomer today. Use Tiny Command's universal Webhook or Schedule trigger to start Kustomer workflows, then run any Kustomer action you need.

What Kustomer actions can I run from a workflow?

4 Kustomer actions are available out of the box, covering email operations like "Create Kustomer Conversation". Every action accepts dynamic inputs from upstream nodes, whether that's a search result, an AI output, or a form field.

Is the Kustomer integration real-time?

Kustomer actions execute synchronously inside your workflow. Tiny Command waits for Kustomer's API to confirm before continuing to the next step, so downstream nodes can rely on the result.

Do I need to write code to use Kustomer with Tiny Command?

No. Every Kustomer trigger and action is fully configurable from the visual workflow builder. For edge cases that aren't covered, drop in a custom HTTP node and call any Kustomer API endpoint directly.

How much does the Kustomer integration cost?

There's a free tier you can start on without a credit card. Higher run volumes and team features come with paid plans. The Kustomer integration itself has no per-app surcharge.