Resources · Zapier integration

Kula Zapier integrationAutomate Kula with Zapier.

The Kula Zapier integration gives you 10 triggers and 1 action to follow every step of your hiring pipeline, from a new job to an accepted offer, and to add candidates from other tools. All 10 triggers are instant, and the app runs on the free plan.

See the 11 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the Kula Zapier integration actually does

Kula is an applicant tracking system, the tool where recruiters source candidates, run interviews and follow each application through the pipeline. Connected to Zapier, it tells your other tools the moment something moves in hiring, and it lets those tools add candidates to Kula, without anyone copying names between screens.

Three results teams usually build first. Onboarding that starts on the yes: Offer Accepted fires the second a candidate accepts, and the Zap opens their onboarding record in the HR tool or the IT ticket for their laptop. A pipeline everybody can see: Application Stage Changed posts each move to the hiring channel, so the hiring manager stops asking for status updates. Candidates from everywhere in one place: a referral form, an event sign-up sheet or a sourcing tool feeds Create Candidate, so nobody is left in a spreadsheet.

What the integration does not do is just as important. There is only one action: Zapier can create a candidate in Kula, but it cannot move an application, reject someone, update a record or create a job. There are no searches either, so a Zap cannot check whether a candidate already exists before adding them. Kula on Zapier is mostly a way to get hiring events out, not to drive the pipeline from outside.

If you are deciding which automation platform suits a recruiting team, the n8n vs Zapier comparison is a good place to start. The site has no Kula page for n8n or Make yet.

Vocabulary

Zapier vocabulary in one minute

Seven words carry this whole page. Here they are once, in plain English.

Zap
The automation you build in Zapier: one trigger, then one or more actions that run each time the trigger event happens.
Trigger
The event in an app that starts the Zap, like a candidate being hired. Once the Zap is on, Zapier waits for it.
Action
What the Zap does once it starts: the step that writes, sends or creates something for you in another app.
Task
The unit Zapier bills. One task is one action that completed successfully, and your plan counts nothing else.
Polling vs instant
A polling trigger is checked by Zapier on a timer. An instant trigger is pushed by the app the moment it happens, like all of Kula's.
Filter
A step that lets the Zap continue only when the incoming data meets your condition, and quietly stops it otherwise.
Connection
Your Kula account linked to Zapier once, then picked again by every Kula step in every Zap you build.
Cost

What a Kula Zap really costs

Kula is not a premium app, so it works on the free Zapier plan. And since all its triggers are instant, the plan's checking interval never slows a Kula trigger down.

  • Free plan100 tasks per month, unlimited Zaps
  • Free plan Zap sizeTwo steps: one trigger, one action
  • Premium appNo, Kula works on the free plan
  • Instant triggers10 of 10, no waiting on any plan

The trigger itself costs nothing, whatever the number of hiring events. Each action that completes counts as one task, and one that fails does not. A Zap that logs each hire in a sheet uses one task per hire. The catch: the free plan only builds two-step Zaps. Add a filter to keep only one department, or a second action, and the Zap becomes multi-step, which needs a paid plan. The interval grid below only matters for polling triggers of other apps.

Connect

Connect your Kula account in three steps

  1. 01

    Open the connection dialog

    In Zapier, open the Apps page of your account and click + Add connection. Type Kula in the search box and select it. You need an existing Kula account before you start.

  2. 02

    Sign in to Kula

    Click Add connection. A new tab opens on Kula: sign in with an account that can see the jobs and applications your Zaps should follow, and that has write access if you plan to create candidates.

  3. 03

    Grant Zapier access

    Approve the access request in that tab. The connection then appears on the Apps page and in every Kula step you add, so this happens only once per account.

First Zap

Your first Zap: log every hire in the onboarding sheet

GoalWhen a candidate is hired in Kula for a given team, add a row to the onboarding spreadsheet.

  1. 01

    Start the Zap on Kula

    Start a new Zap, pick Kula as the app and Candidate Hired as the event, then choose your Kula connection. The editor shows a lightning bolt: this trigger is instant.

  2. 02

    Test the trigger

    Run the test. Zapier brings back the three most recent hires from your account, so you can map a real candidate rather than a placeholder. The test costs nothing.

  3. 03

    Add a filter

    Add a Filter step from the plus icon: a field from the trigger that identifies the team, the rule, and the value you care about. Hires from other teams stop there without using a task.

  4. 04

    Add the sheet action

    Add your spreadsheet app, choose the action that creates a row, and map the candidate details returned by the Kula trigger into the columns.

  5. 05

    Test, then publish

    Test the action, check the new row, then click Publish. The filter makes this a multi-step Zap, so it needs a paid plan to stay on.

Triggers

Kula triggers on Zapier

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

1

Candidate Hired

Instant trigger

In Zapier“Triggers when a candidate is hired.”

The Zap starts as soon as a candidate is marked hired in Kula. It is the end of the pipeline and the start of everything else: payroll, equipment, accounts, welcome messages.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
creating the employee record in your HR system the same minute the recruiter closes the hire.
Watch out
if hires go through an offer first, Offer Accepted may fire earlier; pick one of the two so onboarding does not start twice.
2

Candidate Rejected

Instant trigger

In Zapier“Triggers when a candidate is rejected from a job.”

Fires when a candidate is rejected from a job, with the application details attached. Useful for anything you want to happen after a no, from talent pools to reporting.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
adding strong rejected candidates to a talent pool list in your CRM, so the next opening starts with warm profiles.
Watch out
a rejection is still personal data; keep the destination tool access-restricted.
3

Application Stage Changed

Instant trigger

In Zapier“Triggers when an application moves to a different stage in the hiring pipeline.”

Each time an application moves to another stage of the hiring pipeline, from screening to interview for example, Kula pushes the move to Zapier with the new stage.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
posting stage moves in the hiring team's chat channel, or booking the next interview slot automatically.
Watch out
on a busy pipeline this fires often, and each action costs a task; filter on the stages that matter before publishing.
4

Application Updated

Instant trigger

In Zapier“Triggers when an application is updated.”

Starts whenever an application changes in Kula, which is broader than a stage move. The Zap receives the application as it stands after the change.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
keeping a mirror of all applications in a reporting sheet, where every edit should update the line.
Watch out
if only stage moves matter, Application Stage Changed is narrower and cheaper in tasks.
5

Candidate Create

Instant trigger

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

Kicks off when a new candidate profile is created in Kula, whether a recruiter sourced them or they came in another way. It concerns the person, not an application to a specific job.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
adding every new candidate to your recruitment newsletter list in the email tool.
Watch out
a Zap that ends with Create Candidate on the same account would wake this trigger again, in a loop.
6

New Application

Instant trigger

In Zapier“Triggers when a new application is submitted for a job.”

Someone applies to one of your jobs and the Zap starts with the application, tied to that job. This is the trigger for anything that should follow an incoming application.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
alerting the hiring manager for that role in chat, so the first review happens the same day.
Watch out
for a high-volume role, every applicant is a run; a filter on job title keeps the alerts and the task count in check.
7

New Job

Instant trigger

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

A new job is created in Kula and the Zap wakes up. The Zap gets the job's details, ready to spread the word or prepare the hiring workspace.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
opening a project card for the role in your team's task board, with the hiring manager assigned.
Watch out
every job created fires it, including ones you are not ready to advertise; a filter on the job's fields keeps those out.
8

New Offer Created

Instant trigger

In Zapier“Triggers when a new job offer is created.”

As soon as a job offer is drafted for a candidate in Kula, the Zap starts with that offer. It is the moment before the candidate decides, when approvals usually happen.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
sending the offer for sign-off to finance or the department head in the tool they already check.
Watch out
creating an offer is not sending it; do not start onboarding from this trigger.
9

Offer Accepted

Instant trigger

In Zapier“Triggers when a candidate accepts a job offer.”

The candidate says yes to the offer, and Kula tells Zapier about it. This is the clearest signal in the whole pipeline that a person is joining.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
requesting a laptop and accounts from IT, or adding the new joiner to the onboarding sheet.
Watch out
do not combine it with Candidate Hired for the same onboarding steps, or the newcomer gets everything twice.
10

Offer Declined

Instant trigger

In Zapier“Triggers when a candidate declines a job offer.”

Starts the Zap when a candidate turns down an offer. The role is back to square one, and that news usually needs to reach a few people fast.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
notifying the hiring manager and the recruiter together, and logging the decline in a sheet to spot patterns later.
Watch out
nothing reopens the job or contacts the runner-up by itself; those steps stay manual in Kula.
Actions

Kula actions on Zapier

Kula gives you 1 action. For each one: what it does for you, when to reach for it, and what to watch out for.

1

Create Candidate

Action

In Zapier“Create a candidate.”

Adds a new candidate profile to Kula from data that lives in another tool. It is the only way in: Zapier can create a candidate, but not update or move one afterwards.

When to use it
employee referrals submitted through a form land in Kula straight away, instead of waiting in someone's inbox.
Watch out
there is no search to check for duplicates first, so the same person sent twice becomes two profiles.
When it breaks

When a Kula Zap breaks

Zapier attaches no help article to Kula, so the failures you will meet are the general ones. In recruiting they hit candidates directly, which raises the stakes.

Most broken Kula Zaps come down to one of these three cases. If the cause stays unclear, the Zapier troubleshooting guide is the next stop.

  • Existing candidates are ignored

    A Zap only reacts to events after it is published. Hires, offers and applications from before never trigger it; moving that history is a separate job.

  • Create Candidate feeds its own trigger

    A Zap on Candidate Create that ends with Create Candidate on the same account restarts with every profile it adds, and the loop eats your tasks.

  • A bulk import gets held back

    Import a large batch of candidates at once and Candidate Create can return a flood. Zapier's flood protection may hold that batch back.
Need help

Need help automating Kula with Zapier?

A person reads every message.

FAQ

Kula Zapier integration: frequently asked questions

01Is the Kula Zapier integration free?
Yes, Kula is not a premium app, so it works on the free Zapier plan, which gives 100 tasks per month and unlimited Zaps. That plan only builds two-step Zaps, one trigger and one action. As soon as you add a filter, for example to keep a single department, or a second action, the Zap becomes multi-step and requires a paid plan. You also need your own Kula account with access to the jobs you want to follow.
02How many tasks does a Kula Zap use?
One task for each action that completes, and nothing for the trigger. A Zap that posts every new application to chat uses one task per application, so a role with many applicants adds up quickly. A filter in front of the action helps: runs it stops do not cost a task. An action that fails is not counted either. Triggers like Application Updated fire more often than Candidate Hired, so pick the narrowest one that fits.
03Does Kula trigger Zaps in real time?
Yes, all 10 Kula triggers are instant. Kula tells Zapier the moment a candidate is hired, rejected, moved to a new stage, or when an offer is created, accepted or declined. That holds on every plan, including the free one, so the polling interval grid never applies to Kula. In the editor, Zaps built on these triggers show a lightning bolt. Only a trigger from another app could add a delay.
04What does it take to connect Kula to Zapier?
A Kula account and a Zapier account. On the Apps page in Zapier, click + Add connection, choose Kula, sign in in the tab that opens and approve the access. The account should see the jobs and applications your Zaps will follow, and have write access if you plan to create candidates. You do this once per account, and every Kula step in every Zap reuses the same connection. Test it once before you build anything.
05Can Zapier move or reject a candidate in Kula?
No. The only Kula action on Zapier is Create Candidate. Moving an application to another stage, rejecting a candidate, updating a profile or creating a job all have to happen inside Kula. The integration is built to send hiring events out to your other tools, through its ten triggers, and to bring new candidates in. Plan your Zaps around that: Kula stays the place where recruiters make decisions. Your other tools only listen and report.
06What if the Kula action you want does not exist?
With 10 triggers and 1 action, most of what Zapier offers for Kula is about reacting to events, not changing records. If an update or a stage move is missing, the usual workaround is to send a reminder or a task to the recruiter so the change is made in Kula by hand. For a missing operation, raise the request with Kula. Keep in mind that adding that reminder after another action makes the Zap multi-step, which needs a paid plan.
07Zapier, Make or n8n for Kula?
It depends on your criteria rather than on a winner. Zapier has a ready-made Kula app with 11 operations, every trigger instant, so a recruiting team without developers starts from something already built. Make and n8n are worth weighing if cost per run or control over complex logic matters more to you. On those platforms, check first that a ready-made Kula module exists, since the comparison only works if both sides can reach the app.
Same platform

Other docs you might need on this stack.

Browse all integrations