Resources · Zapier integration

Kustomer Zapier integrationAutomate Kustomer with Zapier.

The Kustomer Zapier integration gives you 6 triggers, 6 actions and 3 searches. Every trigger is instant, so new conversations, customers and messages reach your other tools straight away, and the actions let those tools open conversations, add notes or update customers in return.

See the 15 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the Kustomer Zapier integration does for a support team

Kustomer is a customer service platform that brings the channels a customer uses together in one place. The Zapier integration plugs it into your other tools: conversations, customers and messages created or changed in Kustomer can start automations, and other tools can create or update those same records without an agent copying anything by hand.

Three results support teams typically build. First, escalation alerts: Conversation Created or Message Created pushes a summary to a team chat or a ticket in your engineering tracker, the moment it happens. Second, a customer record that stays in sync: Customer Created copies new customers into your CRM, and Update Customer writes changes from the CRM back into Kustomer. Third, context for agents: an order or payment event elsewhere finds the right person with Find Customer, then opens a conversation or drops a note on it.

What Zapier does not do here. Every write needs Kustomer's own IDs: to update a customer or note a conversation, the Zap must already hold that ID, which usually means a search step first. There is no delete action and no way to send a reply to the customer from Zapier; the actions create and update records, they do not answer people. And all six triggers are instant, which is good news, but it also means an update action can set an update trigger off again.

If you want help designing these flows, our Zapier agency can build them with you, and the Make vs Zapier comparison is worth a read before you commit.

Vocabulary

Zapier vocabulary in one minute

Seven terms come back on every section of this page. Here they are in plain words.

Zap
The automation you build in Zapier: one trigger, then one or more actions that run every time the trigger event happens.
Trigger
The event in an app that starts the Zap, such as a new conversation in Kustomer. Once the Zap is on, Zapier waits for it.
Action
What the Zap does once it has started: the step that creates, updates or sends something for you in an app.
Task
The unit Zapier bills: one action your Zap completes successfully. The allowance on your plan is counted in tasks.
Polling vs instant
A polling trigger is checked by Zapier on a timer. An instant trigger is reported by the app itself the moment the event happens.
Filter
A step that lets the Zap continue only when the data that arrived meets your condition, and stops it otherwise.
Search step
A step that looks up a record that already exists, like a Kustomer customer, so the steps after it can use what it found.
Cost

What a Kustomer Zap really costs

Kustomer is not a premium app on Zapier, so it works on the free plan.

  • Free plan100 tasks per month, unlimited Zaps
  • Free plan Zap sizeTwo steps: one trigger, one action
  • Premium appNo, works on the free plan
  • TriggersAll 6 instant, the interval grid does not apply

None of the six triggers costs a task, and waiting for events is free too. Each action that succeeds, Create Notes or Update Customer for example, counts as one task; one that fails is not billed. Since every Kustomer trigger is instant, the plan interval grid never applies to them. The catch is the Zap size: the free plan stops at one trigger and one action. A Zap that runs Find Customer before an update, or filters conversations first, is multi-step and needs a paid plan.

Connect

Connect Kustomer to Zapier in 3 steps

  1. 01

    Open your connections

    In Zapier, go to the Apps page of your account and click + Add connection. A connection is your Kustomer account linked once, then reused by every Zap that works with it.

  2. 02

    Pick Kustomer

    Search for Kustomer in the dialog, select it and click Add connection. A new browser tab opens on the Kustomer side so you can sign in there with your own Kustomer account.

  3. 03

    Sign in and grant access

    Log in to Kustomer in that tab and let Zapier use the account. You need your own account, plus read or write access to the conversations and customers you did not create but want the Zap to touch.

First Zap

Your first Zap: flag urgent conversations to the team

GoalWhen a new Kustomer conversation matches a keyword, the team chat gets an alert right away.

  1. 01

    Create the Zap

    Start a new Zap, pick Kustomer as the app that starts it and Conversation Created as the event. Connect your Kustomer account when asked.

  2. 02

    Test the trigger

    Run the test: Zapier brings back the three most recent conversations of the connected account. Pick a real one so the next steps are mapped on actual data.

  3. 03

    Narrow it down

    Add a filter that lets through only conversations matching your keyword. It makes the Zap multi-step, which needs a paid plan; on Free, alert on every conversation instead.

  4. 04

    Add the alert

    Add the chat step and map the conversation details your team needs into the message. Test it once and read what came back before going on.

  5. 05

    Publish

    Click Publish to switch the Zap on. Each new conversation from then on triggers it at once, whatever your plan, but older ones stay untouched.

Triggers

Kustomer triggers on Zapier

6 events start a Zap when something happens in Kustomer, and 6 of them are instant: the app calls Zapier straight away, whatever your plan.

1

Conversation Created

Instant trigger

In Zapier“Triggers when a new conversation is created.”

Starts the Zap whenever a brand new conversation opens in Kustomer, whichever channel the customer used to reach you. It hands the following steps the details of that conversation.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
every new case should create a matching ticket in another tool, or ping a channel when the case looks urgent.
Watch out
a Zap that ends with Create Conversation will start itself again, so never pair the two on the same account.
2

Conversation Updated

Instant trigger

In Zapier“Triggers when a conversation is updated.”

Reacts to changes on an existing conversation, rather than to its creation. This is the one to watch when the lifecycle of a case matters more than its arrival.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
closing a case in Kustomer should mark the linked task done in your project tool.
Watch out
any change counts, so add a filter on the field you care about, or the Zap runs far more often than expected.
3

Customer Created

Instant trigger

In Zapier“Triggers when a new customer is created.”

Fires when a new customer record appears in Kustomer. Your next steps receive that customer's details.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
you want each new support contact copied into your CRM or added to a mailing list without waiting.
Watch out
customers who existed before you published the Zap are never picked up; bring them across with a separate import.
4

Customer Updated

Instant trigger

In Zapier“Triggers when a customer is updated.”

Watches existing customer records and wakes the Zap whenever one of them changes. It suits syncing jobs more than alerts.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
your CRM has to mirror every correction agents make in Kustomer.
Watch out
combined with Update Customer in the same direction, this trigger sets itself off in a loop, so keep the sync one way or filter it hard.
5

Message Created

Instant trigger

In Zapier“Triggers when a new message is created.”

Goes off for each new message inside a conversation, not only the first one, so a busy thread can start many runs. It is the finest-grained event Kustomer exposes on Zapier.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
you log every customer message in an archive sheet, or scan incoming text for words that need a supervisor.
Watch out
volume adds up fast, and each action after it costs a task per message, not per conversation.
6

Message Updated

Instant trigger

In Zapier“Triggers when a message is updated.”

Picks up edits to a message that already exists in Kustomer, so a corrected or changed message can be passed on instead of the stale version.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
an archive or a reporting sheet should keep the latest text of each message rather than its first draft.
Watch out
it only fires on changes made after the Zap is published; earlier edits are not replayed.
Actions

Kustomer actions on Zapier

Kustomer gives you 6 actions. For each one: what it does for you, when to reach for it, and what to watch out for.

1

Create Conversation

Action

In Zapier“Creates a Conversation”

Opens a new case in Kustomer, attached to a customer you name by ID, so the team can pick it up from their usual queue.

When to use it
a form, an order problem or a payment failure in another tool should land in front of support as a conversation.
Watch out
Customer ID is required, so run Find Customer just before when the source does not hold that ID.
2

Create Customer

Action

In Zapier“Create a new customer in Kustomer”

Adds a fresh customer profile to Kustomer from data held elsewhere, so the person is known before they ever write in.

When to use it
new signups or buyers in your shop should already exist in Kustomer when support hears from them.
Watch out
nothing checks for duplicates here; the Find or Create Customer variant described below avoids creating the same person twice.
3

Create Notes

Action

In Zapier“Creates a Note”

Adds a note to an existing conversation, so context from another system sits right where the case is handled.

When to use it
an order status, a refund decision or a delivery update should be in the conversation before an agent replies.
Watch out
the Conversation ID is mandatory, so the Zap needs a conversation trigger or Find Conversation upstream.
4

Create User

Action

In Zapier“Creates a User”

Sets up a new team member account in Kustomer, the agent side of the tool rather than a customer.

When to use it
hiring a support agent in your HR tool should give them a Kustomer seat on their first day.
Watch out
name, email and user role are all required, so the source has to provide all three.
5

Update Conversation

Action

In Zapier“Update a Conversation”

Changes an existing Kustomer conversation, based on what happened elsewhere.

When to use it
a bug fixed in your tracker should move the linked conversation forward without an agent touching it.
Watch out
it needs the Conversation ID, and pairing it with Conversation Updated on the same account creates a loop.
6

Update Customer

Action

In Zapier“Update an existing customer in Kustomer”

Edits a customer profile that already exists in Kustomer, so agents see the same details as your CRM or billing tool.

When to use it
a customer changes plan or address in another system and support should see it immediately.
Watch out
the Kustomer ID of that customer is required; an email alone will not do, so search first.
Searches

Kustomer searches on Zapier

3 search steps look for data that already exists in Kustomer, so a later step can use it.

A search step finds a Kustomer record that already exists and passes it to the next steps. In the editor, searches sit at the bottom of the Action event list, under SEARCH. Each one also has a find-or-create version: same search, with a box ticked. Three settings decide what happens when results are odd.

1

Find Conversation

SearchFind or create

In Zapier“Finds a Conversation”

Looks up an existing Kustomer conversation so later steps can add a note to it or update it.

When to use it
an event in another tool concerns a case already open, and you need its ID before writing to it.
Watch out
the editor also lists Find or Create Conversation; it is this same search with creation ticked, not a separate operation.
2

Find Customer

SearchFind or create

In Zapier“Finds a Customer”

Retrieves a customer already stored in Kustomer and hands their ID to the steps that follow, which is how most update and create flows get started.

When to use it
your source does not hold the Kustomer ID that Update Customer or Create Conversation needs.
Watch out
Find or Create Customer is the same search with creation switched on, handy to avoid duplicates.
3

Find User

SearchFind or create

In Zapier“Finds a User”

Locates a team member account in Kustomer, the agent side, so a Zap can work with the right person on your staff.

When to use it
an onboarding flow should check whether an agent already has a seat before giving them one.
Watch out
Find or Create User is this search with creation ticked, and it then asks for the fields Create User requires.

The three settings every search exposes

  1. Successful if no search results are found?
    Left on its default, a search that finds nothing stops the Zap and the steps that needed it are skipped. Switched on, the Zap carries on with empty hands.
  2. Create X if it doesn't exist yet?
    Ticking it turns the search into find-or-create: the setting above disappears and the step asks for the fields needed to create the missing record.
  3. If multiple search results are found?
    Three ways out when several records match: keep the first one, which is the default, stop the Zap, or pass all of them on at once.
When it breaks

When a Kustomer Zap breaks

Zapier links no help article to Kustomer. The cases below are the general limits every Zap shares, read through a support platform with many update events.

Most failures come from loops and missing IDs rather than from Kustomer being down. If your case is not listed, our Zapier troubleshooting page is the next place to look.

  • The update loop

    A Zap that starts on Customer Updated and ends with Update Customer on the same account sets itself off again and again, burning your tasks fast.

  • Missing Kustomer ID

    Update Customer, Update Conversation and Create Notes refuse to run without the record's ID. Add a search step before them when the source does not hold that ID.

  • No backlog

    A Zap only reacts to what happens after it is published. Conversations and customers that already existed are never picked up; moving them is a separate job.

  • Bulk imports held back

    Importing customers in bulk into Kustomer can produce a sudden flood of events, and Zapier's flood protection can hold that batch back.
Need help

Need help automating Kustomer with Zapier?

A person reads every message.

FAQ

Kustomer Zapier integration: questions

01Is the Kustomer Zapier integration free?
Yes, on Zapier's side. Kustomer is not a premium app, so it runs on the free plan, which includes 100 tasks per month and unlimited Zaps. The limit is the size of each Zap: one trigger and one action. Most useful Kustomer flows need a search before an update, or a filter on conversations, and both make the Zap multi-step, which requires a paid plan. Your Kustomer subscription itself is a separate matter.
02How many tasks does a Kustomer Zap use?
One task per action that succeeds. A Zap that sends a chat alert for every new conversation costs one task per conversation. Triggers are free, and so is Zapier waiting for events. Watch Message Created: it fires per message, so a long thread can cost many tasks. Actions that fail are not counted. A loop between an update trigger and an update action is the fastest way to empty a monthly allowance.
03Is the Kustomer integration real time?
Yes. All six Kustomer triggers are instant: Kustomer itself tells Zapier when a conversation, customer or message is created or updated, and the Zap starts right away whatever your plan. The polling grid of 15 minutes on Free, 2 on Professional and 1 on Team or Enterprise does not apply to any of them. In the editor, a Zap built on one of them shows a lightning bolt. No setting changes that.
04What does it take to connect Kustomer to Zapier?
A Kustomer account and a Zapier account. Open the Apps page in Zapier, click + Add connection, pick Kustomer, click Add connection, then sign in and grant access in the tab that opens. Your account needs read or write access to the conversations and customers the Zap will touch. If you plan to use Create User, keep a name, an email and a user role at hand: all three are required. Then build the first Zap.
05Why does a Kustomer update action ask for an ID?
Because Kustomer identifies every customer and conversation by its own ID, and the update actions need it to know which record to change. Update Customer, Update Conversation and Create Notes all require one, and Create Conversation needs the customer's ID. When the source does not hold that ID, add Find Customer or Find Conversation before the action. That search makes the Zap multi-step, so it needs a paid plan. Plan it from the start.
06What if the Kustomer operation you need is missing?
On Zapier, Kustomer offers six triggers, six actions and three searches. There is no delete action and no step that sends a reply to a customer. When a move is missing, the usual way out is to do part of it with what exists, for example a note instead of a reply, or a status change via Update Conversation, and leave the rest to agents inside Kustomer. Check the action list before promising a flow.
07Zapier, Make or n8n for Kustomer?
Choose by criteria, not by a ranking. On Zapier, Kustomer is available on the free plan with six instant triggers, which covers alerts and simple syncs well. Flows that need a search plus an update on every event are multi-step, so compare how each platform bills those and whether it connects to Kustomer at all. Hosting, pricing model and how much configuration your team wants to own are the other criteria to weigh.
Same platform

Other docs you might need on this stack.

Browse all integrations