Micro1 and Textkernel Tx Integration

Demonstration of how apps are integrated in WEXTL workflow builder[4]

Connect Micro1 and Textkernel Tx to automate hr workflows. Trigger events from one app, run actions in the other and use AI to make smart decisions. Integrate apps in 3 simple steps - no code required.

  • 3-day trial
  • Cancel anytime
  • Up to 10 minutes quick set up
  • GDPR
  • Data Encryption
  • 2FA
  • Local Data Region

Learn about Micro1 and Textkernel Tx

Detailed info you need to know about Micro1 and Textkernel Tx integrations in WEXTL. Explore which modules apps support and how you connect them.

  • Micro1

    • HR
    • 1 trigger
    • 3 searches
    • 5 actions

    AI-powered recruiting platform for sourcing, screening, and evaluating technical candidates.[5]

  • Textkernel Tx

    • HR
    • 2 triggers
    • 11 searches
    • 24 actions

    Resume and job parsing, matching and search powered by the Textkernel Tx Platform.[6]

How to connect Micro1 to Textkernel Tx

Set up your Micro1 and Textkernel Tx integration in 3 simple steps[2]. No coding required. Up to 10 minutes setup.

How does the integration between Micro1 and Textkernel Tx work in WEXTL?

WEXTL exposes actions and triggers for Micro1 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.

Micro1 triggersTextkernel Tx actions

Micro1 modules

  • Create an Interview Creates an AI interview. Add up to five Skills and five Custom Questions, set the Interview Language, and turn on Is Proctoring Required to require proctoring. Output includes the Interview ID and Invite URL.
  • Delete an Interview Removes an interview record from your Micro1 account by its Interview ID.
  • Invite Candidates Invites a list of Candidates, each with a Candidate Name and Candidate Email, to an interview. Search Candidates shows the Status of each invitation.
  • Make an API Call Runs a free-form request against the Micro1 REST API using your saved credential.
  • Search Candidates Finds invited candidates across interviews. Narrow the results by Interview ID, by Candidate ID, or with a Keyword for a full-text match, and each result shows the Status and Candidate Email ID.
  • Search Interviews Looks up interviews by Keyword, or lists them all. Output includes the Invite URL, Skills, Interview Language and whether Is Proctoring Required is on.
  • Search Reports Retrieves interview reports narrowed by Interview ID, Candidate ID or Keyword. Output includes the Report URL, Interview Recording URL, Proctoring Score and the evaluations of technical, soft and coding skills.
  • Update an Interview Edits the Interview Name, Skills, Custom Questions, Interview Language or Selected Coding Language of an interview. Turn on Is Coding Round Required or Is Proctoring Required to add those requirements.
  • Watch Events Starts a workflow the moment Micro1 sends an event to the webhook address of this trigger. It fires instantly instead of checking on a schedule.

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 Micro1 and Textkernel Tx integrations. Pick any from the list below if the current combination isn't the one you need.

Automate Micro1 and Textkernel Tx on WEXTL®

Claim your 3-day trial to build Micro1 with Textkernel Tx integration and access every WEXTL® feature.

Cancel anytime.

Frequently asked questions

Common questions about connecting Micro1 and Textkernel Tx.

How do I connect Micro1 and Textkernel Tx?

Connect your Micro1 and Textkernel Tx accounts once, pick a trigger in one app and an action in the other, then map the fields so data flows automatically between them.[3]

What can I automate between Micro1 and Textkernel Tx?

Example: when the "Watch Events" trigger in Micro1 fires, WEXTL can "Add a Document to an Index" in Textkernel Tx. Micro1 has 1 trigger (including Watch Events). Textkernel Tx has 35 actions (including Add a Document to an Index, Add Documents to an Index, and Check If a Document Exists). Add filters and transforms between steps when you need them.[1]

Can Micro1 trigger actions in Textkernel Tx, and Textkernel Tx in Micro1?

Yes. The integration works in both directions. Use the triggers of each app to start a workflow and the actions of the other app to update it.[2]

Do I need to write code to integrate Micro1 and Textkernel Tx?

No. Micro1-to-Textkernel Tx automations are built visually on the canvas. You can optionally add custom JavaScript with Functions when you need advanced logic.[4]

Does Micro1 integrate with Textkernel Tx in real time?

Yes. Trigger-based automations start the moment Micro1 (or Textkernel Tx) fires a new event. Webhook-backed apps run within seconds, and polling-only apps re-check on a schedule you control.[7]

How long does it take to set up a Micro1 + Textkernel Tx integration?

A first automation typically takes 5–10 minutes: connect the credential of each app once, drop a trigger + action onto the canvas, map the fields, and turn the workflow on.

Do I need a paid plan to connect Micro1 with Textkernel Tx?

You can build your Micro1 + Textkernel Tx automation on a 3-day trial with every feature unlocked. Cancel anytime.[8]

References

List of sources used to gather information about the Micro1 and Textkernel Tx integration.

  1. Micro1 and Textkernel Tx integration source code, module specs and credentials implementation.
  2. Our Micro1 and Textkernel Tx integration documentation, structured input and output parameters, scopes, and authentication methods.
  3. Official vendor API documentation for Micro1 and Textkernel Tx, used to verify field meanings, authentication flows, and anything our own specs don't fully capture.
  4. WEXTL® visual workflow builder, anonymized data from our technical support team.
  5. Micro1 integration information
  6. Textkernel Tx integration information
  7. WEXTL® Scheduling
  8. WEXTL® Pricing and Trial
  9. WEXTL® Apps Library

How we write our apps documentation

Explore how WEXTL® crafted Micro1 and Textkernel Tx integration page documentation. Used sources, the role of AI, and how the team validates the result.

Explore Micro1 and Textkernel Tx, or get started