Ashby and Textkernel Tx Integration
Demonstration of how apps are integrated in WEXTL workflow builder[4]
Build hr workflows between Ashby and Textkernel Tx on a visual canvas. Set up data fields sync between apps once and let data flow when events come automatically. Integration will work without code and your team will see the workflow inside WEXTL® builder.
- 3-day trial
- Cancel anytime
- Up to 10 minutes quick set up
- GDPR
- Data Encryption
- 2FA
- Local Data Region
Learn about Ashby and Textkernel Tx
Detailed info you need to know about Ashby and Textkernel Tx integrations in WEXTL. Explore which modules apps support and how you connect them.
Ashby

All-in-one recruiting ATS with analytics, scheduling, and candidate CRM.[5]
Textkernel Tx

Resume and job parsing, matching and search powered by the Textkernel Tx Platform.[6]
How to connect Ashby to Textkernel Tx
Set up your Ashby and Textkernel Tx integration in 3 simple steps[2]. No coding required. Up to 10 minutes setup.
STEP 1
Connect Ashby and Textkernel Tx
Save credentials in WEXTL once. We store them encrypted and reuse the authorization across every workflow[3]. No coding or API skills required.
STEP 2
Build a workflow
Paste selected Ashby and Textkernel Tx nodes onto the canvas[4], or describe what you want and WEXTL wires the flow together with AI Builder.
STEP 3
Map your data
Choose which fields need to sync between Ashby and Textkernel Tx. Use filters or a JS custom code step in between. Everything is on the canvas.
How does the integration between Ashby and Textkernel Tx work in WEXTL?
WEXTL exposes actions and triggers for Ashby and Textkernel Tx that help you connect apps and automate repetitive tasks[1]. A trigger is an event that happens, and an action is a step that performs when the event has occurred.
Ashby triggersTextkernel Tx actions
Ashby modules
- Add a Candidate to a Project Puts a candidate into one of your Ashby projects, by Candidate ID and Project ID.
- Anonymize a Candidate Anonymizes a candidate in Ashby. This cannot be reversed, and every application of the candidate must already be archived or hired.
- Archive an Opening Archives or restores an opening, depending on the Archive switch.
- Create a Candidate Registers a candidate in Ashby from their Name. Add an Email, LinkedIn URL, GitHub URL, Source ID or Location to complete the profile, and Custom Fields for your own data.
- Create a Candidate Note Records a comment on a candidate profile. Use Note to supply the Value in plain Text or HTML. Switch on Send Notifications to inform users subscribed to the candidate.
- Create a Job Opens a new job under a Title, assigned to a Team ID and a Location ID. Use Job Template ID to start from a template, and Default Interview Plan ID for the interview stages.
- Create a Job Opening Creates an opening for one or more Job IDs, due by the Target Hire Date and starting on the Target Start Date. Set the Employment Type, and use Opening State to begin as draft, approved or open.
- Get a Candidate Looks up one candidate, either by Candidate ID or by the External Mapping ID your other system assigned, depending on Retrieve by.
- Get a Job Reads a single job by its ID. Turn on Include Unpublished Job Postings IDs to also see postings that are not published.
- Get a Job Posting Reads a single job posting. Switch on Include Unpublished Job Postings IDs to cover postings not yet published.
- List Candidate Client Info Shows the browser and network details recorded for one candidate, each entry with its IP Address, User Agent and Related Entity Type. Set Limit to see fewer entries.
- List Candidate Notes Fetches the notes written about a candidate, each with its Content and Author. Set Limit to read only the first few.
- List Candidates Pulls every candidate in Ashby with their Primary Email Address, Tags and Company. Use Limit to read just the first batch.
- List Interviews Collects interviews with their Title, Is Debrief flag and Instructions Html. Use Include Archived for archived ones, and Include Non-Shared Interviews to add interviews tied to specific jobs.
- List Job Postings Returns job postings with their Workplace Type, Employment Type and Application Deadline. Use Listed Only to skip unlisted ones, or Department, Location and Job Board ID to focus the list.
- List Jobs Gets jobs narrowed to one Status, or to a date window with Opened After, Opened Before, Closed After and Closed Before.
- List Openings Lists openings together with their Opening State, Opened At time and Closed At time. Use Limit when you only need a sample.
- Make an API Call Calls the Ashby REST API directly with a free-form request under your saved credential.
- Search Candidates Finds people by Email or by Name. Set Limit when only the first few hits matter.
- Search Openings Looks up openings by their Identifier, which is required. Use Limit to keep only the first matches.
- Tag a Candidate Gives a candidate one of your Ashby tags, so recruiters can group and find people by it. Use Tag ID to say which tag.
- Update a Candidate Edits a candidate by changing the Name, Email, Phone Number or Location, or by adding Social Links such as LinkedIn or GitHub. Use Source ID to credit where they came from.
- Update a Job Edits a job: its Title, Team ID, Location ID or Default Interview Plan ID, and its Custom Fields.
- Update a Job Posting Retitles a posting with Title, edits its Description, or changes its Workplace Type. Use Suppress Description Opening or Suppress Description Closing to drop the opening or closing text from the brand.
- Update a Job Status Changes the stage of a job to draft, open, closed or archived, using Status.
- Update an Opening Shifts the Target Hire Date or Target Start Date of an opening, and revises its Employment Type, Identifier or Description. Switch Is Backfill on to mark a replacement hire.
- Update an Opening State Moves an opening to a new stage: draft, approved, open or closed. Add a Close Reason ID when closing it.
- Update the Compensation of a Job Sets the pay ranges for a job through Compensation Tiers. Each tier has a Title and Components, and each component has a Compensation Type, Interval, Minimum Value and Maximum Value.
- Upload a Candidate Resume Saves a resume against a candidate in Ashby, using Resume File.
- Upload a File to a Candidate Stores a document on the profile of a candidate, read from File.
- Watch Events Fires the instant Ashby sends a webhook, handing the event Action and its Data to the workflow.
Textkernel Tx modules
- Add a Document to an Index Stores one document in an index under a Document ID. Use Parsed Document to send the parsed JSON string along with it.
- Add Documents to an Index Sends several documents to an index in a single call. Each document can have a Parsed Document, a Document ID and Custom IDs.
- Check If a Document Exists Checks whether a document with a given Document ID is present in an index.
- Create a Normalization Set Creates a normalization set. Use Content Bytes to upload the Base64 zip content, and Culture to set the locale.
- Create a Skill Set Builds a new skill set for one culture or locale, using its Content.
- Create an Index Sets up a new index under an ID or name of your choice. Use Index Type to make it a Resume index or a Job index.
- Delete a Document from an Index Deletes a single document from the chosen index.
- Delete a Normalization Set Removes a normalization set from Textkernel Tx.
- Delete a Skill Set Skill sets saved in Textkernel Tx can be deleted one at a time here.
- Delete an Index Deletes an index from Textkernel Tx.
- Delete Documents from an Index Removes several documents from an index in one request.
- Format a Resume Builds a formatted resume from a Parsed Document. Use Output Type to get DOCX, PDF, HTML or TEXT, and turn on Hide Top Skills to leave out the top skills.
- Format a Resume from a Template Lays out a Parsed Document in a base64 Template to produce a resume, and passes Custom Data along.
- Geocode a Resume Geocodes an already parsed resume. Use Provider to choose a geocoding service, together with its Provider Key.
- Geocode and Index a Document Geocodes a parsed resume or job and then adds it to an index. Turn on Index If Geocode Fails to index it even if geocoding fails.
- Get a Bimetric Score Scores a source document against target documents as a bimetric match. Turn on Position Titles Ignore Single Word Variations to ignore single word title variations.
- Get a Document Fetches one document that was added to an index earlier.
- Get a Normalization Set Returns one normalization set that was saved in Textkernel Tx.
- Get a Skill Set Reads a stored skill set from Textkernel Tx.
- Get All Indexes Lists your indexes with their Owner ID, Name and Index Type. Use Limit to set the maximum number of results.
- Get an Account Reads the account details for the Textkernel Tx connection you use.
- Get an Index Fetches the information that Textkernel Tx holds on one index.
- Get an Index Document Count Counts how many documents a single index currently holds.
- List Normalization Sets Lists your normalization sets. Use Limit to set the number of results returned.
- List Skill Sets Lists skill sets with their Key, Name and Timestamp. Use Limit to cap the results.
- Make an API Call Runs a free-form request against the Textkernel Tx REST API using your saved credential.
- Match an Indexed Document Matches a document that already sits in an index against other documents. Use Take to set the number of matches.
- Match Documents Matches a Parsed Document against the documents in your indexes. Use Take to set how many matches are returned, and Location Criteria to restrict matches to a place.
- Normalize a Resume Normalizes a resume that was already parsed, applying Normalizer Data when it is provided.
- Parse a Job Order Parses a job order file given as a base64 string. Turn on Output HTML, Output RTF or Output PDF to also get those versions, and Include Geocoding to geocode during parsing.
- Parse a Resume Parses a resume or CV file passed as a base64 string. Turn on Use LLM Parser for the LLM-based parser and Output Candidate Image to also return the candidate image.
- Search Documents Runs a search query over your indexes. Use Skip and Take to page through the results, and Search Expression to enter a boolean search.
- Update a Normalization Set Updates an existing normalization set with new Base64 zip Content Bytes.
- Update a Skill Set Saves new Content to an existing skill set.
- Update Custom Values of a Document Changes the custom value IDs of a document in an index. Use Method to overwrite, add or delete the Custom Values.
- Watch Normalization Sets Checks for normalization sets on a schedule and passes each one on with its Key, Name and Timestamp. Use Limit to cap results per check.
- Watch Skill Sets Checks Textkernel Tx at regular intervals and triggers for every skill set it receives. Use Limit to restrict the number of results.
Explore alternative integrations
There are other apps[9] supported by WEXTL that can be paired with Ashby and Textkernel Tx integrations. Pick any from the list below if the current combination isn't the one you need.
Frequently asked questions
Common questions about connecting Ashby and Textkernel Tx.
References
List of sources used to gather information about the Ashby and Textkernel Tx integration.
- Ashby and Textkernel Tx integration source code, module specs and credentials implementation.
- Our Ashby and Textkernel Tx integration documentation, structured input and output parameters, scopes, and authentication methods.
- Official vendor API documentation for Ashby and Textkernel Tx, used to verify field meanings, authentication flows, and anything our own specs don't fully capture.
- WEXTL® visual workflow builder, anonymized data from our technical support team.
- Ashby integration information
- Textkernel Tx integration information
- WEXTL® Scheduling
- WEXTL® Pricing and Trial
- WEXTL® Apps Library
How we write our apps documentation
Explore how WEXTL® crafted Ashby and Textkernel Tx integration page documentation. Used sources, the role of AI, and how the team validates the result.