Integrations
Sourcing
Kula
12 min
kula is a recruitment automation platform that lets you proactively reach out and engage with top talent everywhere with kula, you have complete control over your talent pipeline create an ashby api key for the kula integration you'll need to create an ashby api key to configure the ashby / kula integration follow the steps below to generate the key sign in to ashby and click admin in the top navigation bar next, click integrations on the left panel of the screen then click integrations to be taken to the integrations marketplace select the integration and click +create api key for kula copy the value provided you could also save the key somewhere secure for future reference 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 screen shot 2023 03 28 at 3 38 43 pm pngscreen shot 2023 03 28 at 3 39 13 pm png create a kula candidate source 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 docid\ ietsrgcsyxtkp9vhuynza guide for more information on how to create a source and source type on kula once you've completed the above steps on ashby, complete the following steps on your kula account navigate to the settings page via the side menu > under the organization tab > click the integrations section click on the setup toggle in the add integration modal, input the ashby api key created earlier once the ashby integration is added, the ashby records may take some time to be imported into kula ashby/kula stage mapping 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 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 ashby integration features the following features will be activated once you have enabled the ashby integration with kula kula flows when creating a kula flow, you may link it to an ashby job via the applicant tracking system dropdown 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 bi directional sync of candidate stages 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 candidate’s stage is also updated in ashby candidate referral 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 notes sync 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 private notes on kula will not be synced to ashby conversations sync 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 resume sync 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) kula will not attach the resume if one already exists on the application, whether or not kula uploaded it