Resources · Zapier integration

Kylas CRM Zapier integrationAutomate Kylas CRM with Zapier.

The Kylas CRM Zapier integration gives you 6 triggers, 4 actions and 1 search. Every trigger is instant, so a new lead or an updated deal reaches your other tools without waiting. Here is what each one does, what it costs and where it breaks.

See the 11 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the Kylas CRM Zapier integration actually does

It links your Kylas CRM account to Zapier so that something happening in the CRM (a lead, a contact or a deal created or edited) starts work elsewhere, and so that other tools can create records in Kylas CRM without anyone typing them in. Nothing is coded: you pick events from menus.

Three results people usually build first. A lead that never sits unseen: New Lead fires the second the lead lands, and the next step can alert the rep or log it in a sheet. A pipeline that fills itself: a form or a booking tool calls Create Lead or Create Deal, so the record is in Kylas CRM before anyone opens it. Clean company records: Search Company checks whether the account already exists before Create Company adds a duplicate.

What Zapier does not do here matters just as much. There is no delete action, no update action and no way to edit an existing lead, contact or deal from a Zap: the four actions only create. The only search looks up companies, not people or deals. And there is no trigger on companies at all, so a new account in the CRM stays invisible to Zapier.

If you are weighing tools before you build, see our n8n vs Zapier comparison and our Zapier review. On the Zapier side, Kylas CRM brings 11 visible operations: 6 instant triggers, 4 actions and 1 search.

Vocabulary

Zapier vocabulary in one minute

Seven words come back on every line of this page. Here they are in plain English.

Zap
The automation you build on Zapier: one trigger, then one or more actions that run each time that trigger event happens.
Trigger
The event in an app that starts the Zap. Once the Zap is switched on, Zapier waits for that event and nothing else.
Action
What the Zap does after it starts: the step that creates, sends or moves something on your behalf, in Kylas CRM or elsewhere.
Task
The unit Zapier bills you for. One action that completes successfully is one task, and your plan counts those per month.
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 incoming data meets your condition, and quietly stops it the rest of the time.
Search step
A step that looks up a record that already exists in an app, so the steps after it can reuse what it found.
Cost

What it really costs to run

Kylas CRM is not a premium app, so it works on the free plan. The bill comes from tasks, not from the trigger.

  • Free plan100 tasks per month, unlimited Zaps
  • Free plan Zap size2 steps: one trigger, one action
  • Premium appNo, available on every plan
  • Kylas CRM triggers6 instant, 0 polling

A trigger firing never costs a task, and neither does Zapier listening for one. Each action that succeeds counts once, so a Zap with three actions eats three times as much as a Zap with one. An action that fails is not counted. The free plan stops at two steps: a filter, a second action or a Search Company step makes the Zap multi-step, which needs a paid plan. The interval grid below only matters for polling triggers, and all six Kylas CRM triggers are instant.

Connect

Connect Kylas CRM 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 Kylas CRM account linked once, then reused by every step that touches the app.

  2. 02

    Find Kylas CRM

    Type Kylas CRM in the search box of the dialog, select it, then click Add connection. A new browser tab then opens on the Kylas CRM side, where the actual sign-in happens.

  3. 03

    Sign in and grant access

    Log in to your Kylas CRM account in that tab and allow Zapier to use it. You need an account on the app, plus read or write access on any record you do not own and want a Zap to touch.

First Zap

Your first Zap: turn qualified leads into deals

GoalEvery new lead that passes your condition gets its own deal in Kylas CRM, without anyone typing it in.

  1. 01

    Build the trigger

    Create a Zap, pick Kylas CRM as the app and New Lead as the event, then choose your connection. Since the trigger is instant, the editor shows a lightning bolt on it.

  2. 02

    Test it on a real lead

    Run the test. Zapier brings back the three most recent leads of your account, so you map the next steps on a real record instead of a blank one.

  3. 03

    Add the filter

    Click the plus icon, add Filter, then set the field, the rule and the value. Use a text rule on a text field, or the filter will never pass.

  4. 04

    Create the deal

    Add Create Deal, map the name from the lead, then the owner email and the estimated value. Test the step and read what came back in Kylas CRM.

  5. 05

    Publish

    Click Publish to switch the Zap on. With a filter, this is a three-step Zap, so it runs on a paid plan only. On the free plan, drop the filter and keep New Lead then Create Deal.

Triggers

Kylas CRM triggers

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

1

New Contact

Instant trigger

In Zapier“Triggers when a new contact is added in Kylas CRM.”

Starts your Zap each time someone adds a contact in Kylas CRM, whether a rep types it in or another tool creates it. The contact's details travel to the next step.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
push every fresh contact into your newsletter tool or your invoicing software so nobody has to type them in twice.
Watch out
contacts that existed before you published the Zap are never sent; only those added afterwards count.
2

Contact Updated

Instant trigger

In Zapier“Triggers when a contact is updated.”

Fires when an existing contact is edited in the CRM, which lets you keep a copy of that person elsewhere in step with what your team changes.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
keep the copy of that person in your support desk or a spreadsheet in step the moment someone corrects the record.
Watch out
every edit counts as an update, so a contact touched five times in a row can start the Zap five times and cost five rounds of tasks; a filter keeps only the changes you care about.
3

New Deal

Instant trigger

In Zapier“Triggers when a new deal is generated in the system.”

Launches the Zap as soon as a deal appears in your Kylas CRM pipeline, so the steps that follow can act on it.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
post an alert in your team chat when a new opportunity opens, or start a proposal draft in your document tool.
Watch out
if the same Zap also uses Create Deal, each deal it creates fires this trigger again and loops until your tasks run out.
4

Deal Updated

Instant trigger

In Zapier“Triggers when a new deal is generated in the system.”

Reacts when a deal already in the pipeline changes, for example when someone edits its value or moves it along, so other tools can follow the deal's life.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
pair it with a filter so only the changes you care about reach your invoicing or onboarding tool.
Watch out
Zapier's own description of this trigger repeats the wording of New Deal, so test it on a real edit to confirm what it sends before you rely on it.
5

New Lead

Instant trigger

In Zapier“Triggers when a new lead is generated in the system.”

Picks up every new lead the moment it is generated in Kylas CRM, from a web form, an import or a rep, and hands its fields to the steps that follow.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
this is the trigger for speed-to-lead: ping the owner, or start a welcome email while the prospect is still on your site.
Watch out
a bulk lead import can send a huge batch at once, and Zapier's flood protection may hold part of it back.
6

Lead Updated

Instant trigger

In Zapier“Triggers when a lead is updated in Kylas CRM.”

Fires on each change to an existing lead in Kylas CRM, which makes it the place to react when your team works on a lead.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
notify a manager when a lead changes, with a filter that keeps only the edits that matter.
Watch out
without a filter, routine edits by your team will start the Zap far more often than you expect.
Actions

Kylas CRM actions

Kylas CRM gives you 4 actions. For each one: what it does for you, when to reach for it, and what to watch out for.

1

Create Company

Action

In Zapier“Creates a new company on Kylas CRM.”

Opens a company record in Kylas CRM with the name the Zap hands it.

When to use it
right after Search Company comes back empty, so new accounts get created and known ones are left alone.
Watch out
the company name is required; map it from a field that is always filled, or the step fails on the entries where it is blank.
2

Create Contact

Action

In Zapier“Creates A Contact on Kylas CRM.”

Writes a contact into the CRM, for people you already know rather than prospects to qualify.

When to use it
when a customer pays in your billing tool, make sure they exist as a contact in Kylas CRM.
Watch out
only the last name is mandatory, and the integration has no contact search to check first, so doubles are on you.
3

Create Deal

Action

In Zapier“It will create deal”

Puts a deal in your pipeline with its name, owner and estimated value, ready for a rep to pick up.

When to use it
a signed quote or a booked demo elsewhere becomes an opportunity in Kylas CRM without manual entry.
Watch out
three fields are required: the name, the owner entered as a user's email, and the estimated value, which Kylas CRM can calculate on its own when a product is mapped.
4

Create Lead

Action

In Zapier“Creates a lead on Kylas CRM”

Adds a new lead to Kylas CRM from whatever reached the Zap: a form entry, a chatbot conversation, an event sign-up.

When to use it
send every inbound request into the CRM so the sales team works from one list.
Watch out
the last name is the one required field, so a form that only asks for a first name will fail at this step.
Searches

Kylas CRM search

1 search step looks for data that already exists in Kylas CRM, so a later step can use it.

A search step finds a record that already exists, so the next steps can use it. In the editor, searches sit at the bottom of the Action event list, under the SEARCH heading. Three settings decide what happens when the result is not clean.

1

Search Company

Search

In Zapier“This searches company by the name”

Looks up a company in Kylas CRM by its name and passes the record it finds to the following steps.

When to use it
before Create Company, so you stop creating the same firm twice.
Watch out
the name is the only search key, and Kylas CRM decides how exact the match must be; a company stored with a different spelling will not come back.

The three settings every search exposes

  1. Successful if no search results are found?
    Left on its default, an empty search stops the Zap and skips the steps that relied on it. Switched on, the Zap carries on with nothing in hand.
  2. Create X if it doesn't exist yet?
    This box turns a search into a find-or-create. Search Company has no such variant on Kylas CRM, so pair it with Create Company instead.
  3. If multiple search results are found?
    Three options when several records match: keep the first one, which is the default, stop the Zap, or pass all of them on.
When it breaks

When the Kylas CRM Zap breaks

Zapier links no help article to Kylas CRM, so the failures below are the ones every Zap meets, read through this app's operations.

Most problems show up after publishing, not during the test. If a Zap stops without a clear reason, see our Zapier troubleshooting guide.

  • Old records never show up

    A Zap only reacts to what happens after you switch it on. Leads, contacts and deals already in Kylas CRM are not picked up; moving that backlog is a separate job.

  • The deal Zap that feeds itself

    New Deal plus Create Deal in the same Zap means every deal created starts the Zap again. It loops and burns through your task count fast.

  • A bulk import gets held back

    Importing a large list of leads can make New Lead return a huge batch at once, and Zapier's flood protection may hold it back instead of running it all.

  • Required fields left empty

    Create Lead and Create Contact need a last name, Create Company a name, Create Deal a name, an owner email and a value. A blank mapped field fails the step.
Need help

Need help automating Kylas CRM with Zapier?

A person reads every message.

FAQ

Kylas CRM Zapier integration: frequent questions

01Is the Kylas CRM Zapier integration free?
Yes, on the free plan. Kylas CRM is not a premium app, so a free Zapier account can use it with 100 tasks a month and as many Zaps as you like. The catch is size: on the free plan, a Zap holds one trigger and one action. Add a filter, a second action or the company search, and you need a paid plan. Your Kylas CRM subscription is a separate matter that Zapier does not change.
02How many tasks does a Kylas CRM Zap use?
One per successful action. The trigger costs nothing, however often a lead or a deal arrives. A Zap that creates a deal uses one task each run; one that also creates a company uses two. A failed action is not counted. Watch the update triggers: Lead Updated, Contact Updated and Deal Updated fire on every edit, so a busy record can run the Zap many times and multiply the bill unless a filter cuts the noise.
03Does Kylas CRM send data to Zapier in real time?
Yes. All six triggers are instant: Kylas CRM tells Zapier as soon as a lead, contact or deal is created or changed, and the Zap starts at once. The interval grid of the plans, with its 15 minutes on the free plan, applies to polling triggers only, so it does not slow these down. That is the main reason this app works well even on a free account. The editor shows a lightning bolt on instant triggers.
04What does it take to connect Kylas CRM to Zapier?
An account on Kylas CRM, plus read or write access to the records you want a Zap to touch when you do not own them. The connection is made once from the Apps page of Zapier with Add connection: you sign in to Kylas CRM in a new tab and grant access. Every Zap that uses the app then reuses that same connection, so there is nothing to repeat per Zap.
05Why does Create Deal fail when the other fields look fine?
Usually because of the owner. Create Deal requires a name, an estimated value and an owner, and the owner is entered as the email of a user in your Kylas CRM account. An email that matches nobody, or a mapped field that arrives empty, leaves the deal without a valid owner. Test the step with a real email first. If you map a product, Kylas CRM can work out the estimated value on its own.
06What if the Kylas CRM operation you need is not in the list?
Then Zapier cannot do it with this app today. The integration only creates leads, contacts, companies and deals, and only searches companies. Updating a record, deleting one or searching a lead or a deal is not offered, and no trigger watches companies. The usual workarounds are to check whether Kylas CRM can send the event itself through another tool, or to handle that part by hand. A specialist can tell whether another platform covers it.
07Zapier, Make or n8n for Kylas CRM?
It depends on your criteria, not on a winner. Zapier is the quickest to set up and its six instant triggers already cover leads, contacts and deals. Make tends to suit you when one scenario needs many steps and you watch the cost per run. n8n fits teams that want to self-host and have someone technical to maintain it. Compare the operations each one offers for Kylas CRM before choosing, because coverage differs from one platform to the next.
Same platform

Other docs you might need on this stack.

Browse all integrations