Aladtec and Textkernel Tx Integration

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

Keep Aladtec and Textkernel Tx matched by integrating their events and actions. When hr events happen in Aladtec, update the Textkernel Tx automatically - without any line of code in visual workflow builder.

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

Learn about Aladtec and Textkernel Tx

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

  • Aladtec

    • HR
    • 7 triggers
    • 23 searches
    • 7 actions

    Workforce scheduling and timekeeping for public safety and healthcare teams.[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 Aladtec to Textkernel Tx

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

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

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

Aladtec triggersTextkernel Tx actions

Aladtec modules

  • Adjust Accrual Bank Balances Changes the hours in a member accrual bank by a relative amount. Use a positive Adjustment Hours figure to add time and a negative one to remove it, and Note to log the reason.
  • Clock In a Member Starts a time clock entry for a member on a kiosk, beginning at the Clock In DateTime. Use Paycode ID to attach a pay category. The response returns the Member ID, Kiosk ID and Clock in datetime.
  • Clock Out a Member Ends the open entry of a member on the time clock, finishing at the Clock Out Date and Time. The response echoes the Member ID, Kiosk ID and Clock out datetime.
  • Create a Member Adds a person to Aladtec as a member with a First Name, Last Name, Login, Primary Email and Work Group ID. Use Date Hired, Employee Type ID, Schedule IDs or Custom Attributes for a fuller profile.
  • Get Accrual Bank Balances Reads the hours currently held in accrual banks. Use Member IDs and Accrual Bank IDs to say whose balances in which banks, and each result lists the Member ID, Accrual bank ID and Hours.
  • Get Accrual Banks Lists the accrual banks of your Aladtec system, each as its own bundle with an Accrual bank ID and Name. Set a Limit when only the first few are wanted.
  • Get Availability Reports when members are available from Range Start to Range Stop. Each result is a Member ID with an availability Type and its start and stop as datetime and timestamp.
  • Get Clocked-In Members Finds members whose time clock entry is still open. Results include the Member ID along with the Paycode label and In note from clock-in.
  • Get Events Fetches calendar events from Range Start through Range Stop, grouped by day. Use Daily Split Time to move the hour at which one day ends and the next begins.
  • Get Extra Hours Retrieves extra hours records starting at Range Start and ending at Range Stop. Use Statuses to keep requests such as approved, and Member IDs, Schedule IDs, Time Type IDs or Position Qualification IDs to narrow whose time is fetched.
  • Get Kiosks Lists the time clock kiosks set up in Aladtec, with the Is enabled flag of each. Use Limit to trim how long the list is.
  • Get Member Custom Attributes Reads the groups of custom attributes defined for the member database. Each group lists its Attribute group ID, Name and Attributes.
  • Get Member Employee Types Lists the employee types that members can be assigned. Create a Member and Update a Member both use these in Employee Type ID.
  • Get Members Retrieves member profiles including name, Login, Primary email, Work group ID and Date hired. Turn on Include Inactive to also get inactive members, or use Member IDs to fetch only certain people.
  • Get Members Scheduled Now Shows who is working at this moment, organised by schedule and the Positions they fill. Use Schedule IDs to look at only some of your schedules.
  • Get Open Time Ranges Finds shift time nobody has filled, grouped by day, from Range Start to Range Stop. Search particular positions with Position IDs. Turn on Include Only Shift Time to limit ranges to the shift boundaries.
  • Get Paycodes Lists the pay categories configured on the Aladtec time clock. Clock In a Member accepts a Paycode ID from this list.
  • Get Position Qualifications Reads the qualifications a member can hold for positions. Use Limit to ask for up to 500 of them.
  • Get Scheduled Shifts Pulls scheduled shifts running from Range Start to Range Stop, split into days. Narrow by Schedule IDs, Member IDs or Time Type IDs, and use Include Time Types to add type names.
  • Get Scheduled Time Notes Collects the schedule notes written between Start Date and Stop Date, one result for each day. Use Schedule IDs to read the notes of selected schedules only.
  • Get Schedules Lists your schedules, each with a Schedule ID, Name and Order, plus the Positions it contains. Turn on Include Archived to add schedules that were archived.
  • Get Shift Labels Looks up the labels attached to shifts from Start Date to Stop Date, one result per date. Use Limit to restrict the count, with a maximum of 500.
  • Get Time Clock Records Returns time clock entries from Range Start through Range Stop. Every entry has a Member ID and a Paycode label, along with its In note and Out note.
  • Get Time Off Records Lists time off records that overlap Range Start to Range Stop, divided by day. Use Statuses to keep only requests with a status such as approved.
  • Get Time Types Reads the time types of your account. Each has a Time type ID, and a flag for Is default and one for Is active.
  • Get Work Groups Fetches the work groups defined in Aladtec. Create a Member needs a Work Group ID, and this list holds the options with their Work group ID.
  • Make an API Call Makes an authorized free-form request to the Aladtec REST API with your saved credential.
  • Run a Payroll Report Generates payroll data for the period that runs from Range Start to Range Stop. Use Member IDs or Time Categories to filter it, and Next Token to fetch the following page of a long report.
  • Update a Member Edits a member record by changing its First Name, Last Name, Login, Mobile Phone, Primary Email, Work Group ID or Custom Attributes. Turn off Is Active to deactivate the member.
  • Update Accrual Bank Balances Overwrites the accrual bank balance of a member with an absolute figure from Hours, which may be positive or negative. Use Note to log why it was set.
  • Watch Accrual Banks Polls Aladtec on a timer and triggers the workflow for each accrual bank, delivering its Accrual bank ID.
  • Watch Kiosks Checks the time clock kiosks every polling interval and runs once for each, reporting whether the kiosk Is enabled.
  • Watch Members Polls Aladtec on a schedule for one member and starts the workflow with the profile, including Primary email and Work group ID. Use Member ID to say which member to follow.
  • Watch Paycodes Reviews the time clock paycodes at each poll and starts a workflow for each paycode, with its Paycode ID attached.
  • Watch Position Qualifications Regularly polls position qualifications and kicks off the workflow for each. Use Limit to set how many are handled in one execution.
  • Watch Schedules Reads your schedules at each interval and runs the workflow for every one, showing Is archived and Positions. Use Limit to cap how many each run handles.
  • Watch Work Groups Polls work groups at your chosen interval and triggers a run for every group found, with its Work group ID.

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

Automate Aladtec and Textkernel Tx on WEXTL®

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

Cancel anytime.

Frequently asked questions

Common questions about connecting Aladtec and Textkernel Tx.

How do I connect Aladtec and Textkernel Tx?

Connect your Aladtec 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 Aladtec and Textkernel Tx?

Example: when the "Watch Accrual Banks" trigger in Aladtec fires, WEXTL can "Add a Document to an Index" in Textkernel Tx. Aladtec has 7 triggers (including Watch Accrual Banks, Watch Kiosks, and Watch Members). 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 Aladtec trigger actions in Textkernel Tx, and Textkernel Tx in Aladtec?

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 Aladtec and Textkernel Tx?

No. Aladtec-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 Aladtec integrate with Textkernel Tx in real time?

Yes. Trigger-based automations start the moment Aladtec (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 Aladtec + 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 Aladtec with Textkernel Tx?

You can build your Aladtec + 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 Aladtec and Textkernel Tx integration.

  1. Aladtec and Textkernel Tx integration source code, module specs and credentials implementation.
  2. Our Aladtec and Textkernel Tx integration documentation, structured input and output parameters, scopes, and authentication methods.
  3. Official vendor API documentation for Aladtec 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. Aladtec 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 Aladtec and Textkernel Tx integration page documentation. Used sources, the role of AI, and how the team validates the result.

Explore Aladtec and Textkernel Tx, or get started