In order to have a seamless flow of information between Ashby and Kula, follow the below steps while integrating your ATS.

You'll need to create an Ashby API Key to configure the Ashby / Kula integration. Follow the steps in this article to generate the key.

When the Ashby API Key is created, it will be shown only once. Please store this API Key in a secure location accessible only to authorized persons.

This key will be needed in later steps when you configure the integration on Kula.

To ensure the applications exported from Kula are tagged with source, “Kula” creates a new source type “Integration,” and a new “Kula” source under it.
​
​

Please take a look at the Ashby Source Types and Sources article to create a source and source type.

Once you've completed the above steps on Ashby, complete the following steps on your Kula account.

Take a 10-minute break before proceeding with the next steps.

On the Settings page, under the Organization -> Integrations tab, click Configure.
​

You should now see the ATS - Kula Mapping & Kula - ATS Mapping tables.
​
​

Please verify that the mappings are correct for your organization or adjust accordingly.
​

NOTE: If your Ashby account is not using any custom stages, the default mappings provided by Kula should work out of the box in most cases.

The following features will be activated once you have enabled the Ashby integration with Kula.
​

When creating a Kula Flow, you may link it to an Ashby job via the Applicant Tracking System dropdown.
​
​NOTE: Only open jobs will be listed in the selection.
​

Whenever a candidate is added to this Kula Flow, Kula will create a new Ashby application against the linked Ashby job. If the corresponding candidate does not already exist on Ashby, one will be created.
​

If you click the Ashby icon, you will be redirected to the corresponding candidate on Ashby.
​
​

Changes to the candidate stage on Kula will be synced with the Ashby application (and vice versa) based on the Kula/ATS stage mapping (as configured during integration setup). For example, when you move a candidate to the Interested stage on Kula, the candidate will also move to the corresponding stage on Ashby.
​
​

The stage would also be updated on Ashby:
​
​

When referring a candidate using Circles, you may select an Ashby job to refer the candidate to. This will create an Ashby application (and the corresponding candidate, if one does not already exist) against the selected job.
​

When a note is added to a candidate on Kula, a corresponding note will be added to the candidate on Ashby (only if one already exists)

When a candidate is created on Ashby (by Kula via Kula Flows or candidate referral), existing notes on the Kula candidate will be added to the Ashby candidate accordingly
​

NOTE: "Private" notes on Kula will NOT be synced to Ashby

Whenever a conversation message with a candidate is logged on Kula (e.g., Kula Flow messages & replies), a corresponding note will be added to the candidate on Ashby (only if one already exists)
​

When a candidate is created on Ashby (e.g., via Kula Flow or candidate referral), existing conversations with the Kula candidate will be added to the Ashby candidate accordingly.

When a resume is uploaded to a candidate on Kula, a corresponding resume will be added to the candidate's current application on Ashby (only if Kula created it)

​NOTE: Kula will not attach the resume if one already exists on the application, whether or not Kula uploaded it