Setting up Textkernel Match Automation (PREVIEW)🔗
This feature is currently still under development. These instructions are preliminary and may change in the final version. If you are interested in becoming a beta tester when we are ready, please contact your Textkernel account manager.
Customers using this feature require a configured search and match environment. Also, to use this feature, Textkernel services must configure automatic match for the customer.
This feature makes REST api calls into Salesforce. Based on your Salesforce license and user count you have a limited daily allocation. Similarly, this feature publishes Salesforce Platform Events, which also have daily limits for publishing and consuming.
Matching candidates upon job creation🔗
This use case is triggered after a job (meeting certain agreed filter criteria) is created in your Salesforce ATS. When configured, the best-matching ATS candidates for the new job are automatically sent into the Salesforce environment via the Textkernel automation API webhook, and published inside Salesforce as Salesforce Platform Events.
Steps to configure match automation:
1 Configure the OAuth 2.0 Connected App and Automation API Webhook🔗
The Salesforce webhook is used by Textkernel to push automation events into Salesforce. The setup procedure is documented in Configure Connected App and Automation API Webhook within the Basic Textkernel Connector setup guide within this Admin installation guide.
As part of that procedure, you will configure the integration user and provide the following information to Textkernel:
- OAuth 2.0 Consumer Key
- OAuth 2.0 Consumer Secret
- OAuth 2.0 Token URL
- Salesforce Webhook URL
2 Work with Textkernel services to clarify what match-filtering criteria should be applied🔗
When setting up this feature, Textkernel services will consult with you to identify what are the right match-filter criteria for your business.
3 Setup a platform cache partition🔗
Textkernel's integration uses the Salesforce platform cache as part of our automation support. The Salesforce admin needs to configure this outside of our integration as part of this setup.
We recommend that you allocate 2 MB of the cache to our application. We use the cache to de-duplicate any events pushed into Salesforce from the automation API. If a match event or external Candidate import event is resent within 48 hours, we will not re-process the redudant event request(s).
To set up a platform cache, follow these steps:
Go to the Salesforce Setup page
Go to "Platform Cache" under the Custom Code section.
Click on MB on the KB / MB selector.
Click "Edit" next to the partition named "Events" with the Namespace Prefix "Textkernel1".
Leave the Session Cache Allocation field blank (we don't use this).
Under "Org Cache Allocation", Under "Organization", enter "2". (The partition is part of our managed package so it already has 1 MB of Provider Free Cache). The resulting total cache partition size is 3 MB.
Click "Save" to save your changes to the partition.
4 Create workflow automation to consume the match Platform Events🔗
The Textkernel integration publishes Platform Events whenever the automatic match is triggered. These events have the same generic structure of the Textkernel Portal Action, but they have a specific Action Name for the automation api match event (ie job_match/v1). This makes it simple to write shared workflow automation to handle automatic and manual matches the same way. Or, as an alternative, workflows can use the Action Name to distiguish between a manually-triggered match, and a fully automated match.
The Salesforce administrator configures workflow automation that is triggered by the Platform Events (for example, using Flow or APEX). The specific workflows depend on your specific way of working, but for example, you could use the matches to automatically create a job submission/application record; feed candidates into an email campaign; send a custom notification for the recruiter to follow-up; or other actions.
More details about monitoring Textkernel Platform Events are provided in the Operational Guide