Log inStart trial

Aladtec and Keeping Integration

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

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

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

Learn about Aladtec and Keeping

Detailed info you need to know about Aladtec and Keeping 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]

  • Keeping

    • HR
    • 6 triggers
    • 12 searches
    • 19 actions

    Time tracking software for logging hours against clients, projects and tasks. [6]

How to connect Aladtec to Keeping

Set up your Aladtec and Keeping integration in 3 simple steps [2] — no coding required. Up to 10 minutes setup.

  1. STEP 1

    Connect Aladtec and Keeping

    Save credentials in WEXTL once. We store them encrypted and reuse the authorization across every workflow [3]. No coding or API skills required.

  2. STEP 2

    Build a workflow

    Paste selected Aladtec and Keeping nodes onto the canvas [4], or describe what you want and WEXTL wires the flow together with AI Builder.

  3. STEP 3

    Map your data

    Choose which fields need to sync between Aladtec and Keeping. Use filters or leverage a JS custom code step in between — everything is on the canvas.

How does the integration between Aladtec and Keeping work in WEXTL?

WEXTL exposes actions and triggers for Aladtec and Keeping that help you connect apps and automate repetitive tasks [1]. A trigger is an event that happens, an action — a step that performs when the event has occurred.

Aladtec triggersKeeping actions

Aladtec modules

  • Adjust Accrual Bank Balances Adjusts accrual bank balances for accurate financial reporting.
  • Clock in a Member Clocks in a member for attendance or time tracking.
  • Clock Out a Member Clocks out a member.
  • Create a Member Creates a new member in the member database.
  • Get Accrual Bank Balances Gets accrual bank balances for the members.
  • Get Accrual Banks Gets all accrual banks.
  • Get Availability Gets member availability for a date or time range.
  • Get Clocked-In Members Gets members who are currently clocked in.
  • Get Events Gets events for a specified date or time range.
  • Get Extra Hours Gets extra hours for a specified time period.
  • Get Kiosks Retrieves a list of active kiosks.
  • Get Member Custom Attributes Retrieves custom attributes for a specified member.
  • Get Member Employee Types Retrieves employee types assigned to a member.
  • Get Members Retrieves members and their associated member database attributes.
  • Get Members Scheduled Now Retrieves members who are scheduled at the current time.
  • Get Open Time Retrieves time ranges where no member is scheduled.
  • Get Paycodes Retrieves active paycodes from the service.
  • Get Position Qualifications Retrieves unique position qualifications.
  • Get Scheduled Time Gets scheduled time ranges for a specific period.
  • Get Scheduled Time Notes Retrieves scheduled time notes by a calendar date.
  • Get Schedules Retrieves schedule configuration details.
  • Get Shift Labels Gets shift labels for a date range.
  • Get Time Clock Records Gets time clock records for a specified date or time range.
  • Get Time Off Retrieves approved and pending time off ranges.
  • Get Time Types Gets available time types.
  • Get Work Groups Retrieves all work groups from the service.
  • Make an API Call Performs an authorized API call.
  • Run a Payroll Report Runs the payroll report export.
  • Update a Member Updates a member in the member database.
  • Update Accrual Bank Balances Updates accrual bank balances for the specified accounts.
  • Watch Accrual Bank Triggers when a change occurs in the accrual bank.
  • Watch Group Triggers when there are updates or changes in a group.
  • Watch Kiosk Triggers when a new kiosk is added or updated.
  • Watch Members Triggers when a new member is added or changes are made to an existing member.
  • Watch Paycodes Triggers when new paycodes are created or updated.
  • Watch Position Qualifications Triggers when position qualifications are added or changed.
  • Watch Schedules Triggers when a new schedule is created or modified.

Keeping modules

  • Archive a Project Sets a project's state to archived.
  • Archive a Task Sets a task's state to archived.
  • Create a Client Creates a new client.
  • Create a Project Creates a new project.
  • Create a Task Creates a new task.
  • Create an Entry Creates a new time entry.
  • Delete a Client Permanently deletes a client.
  • Delete a Project Permanently deletes a project.
  • Delete a Task Permanently deletes a task.
  • Delete an Entry Permanently deletes a time entry.
  • Get a Client Retrieves a client by ID.
  • Get a Project Retrieves a project by ID.
  • Get a Task Retrieves a task by ID.
  • Get a User Retrieves a single user of the organisation.
  • Get an Entry Retrieves a single time entry.
  • Get Current User Retrieves the organisation user that belongs to the connection in use.
  • List Clients Lists the clients in the organisation.
  • List Organizations Lists all your currently active organisations.
  • List Projects Lists the projects in the organisation.
  • List Tasks Lists the tasks in the organisation.
  • List Timesheet Entries Lists time entries in the organisation.
  • List Users Lists the users in the organisation.
  • Make an API Call Sends a custom authorized request to the Keeping API.
  • Restore a Project Sets an archived project's state back to active.
  • Restore a Task Sets an archived task's state back to active.
  • Resume an Entry Resumes a stopped time entry.
  • Stop an Entry Stops a running time entry.
  • Update a Client Updates a client by ID.
  • Update a Project Updates a project by ID.
  • Update a Task Updates an existing task.
  • Update an Entry Modifies an existing time entry.
  • Watch Clients Triggers when a new client is added to an organisation.
  • Watch Organizations Triggers when a new organisation becomes available.
  • Watch Projects Triggers when a new project is added to an organisation.
  • Watch Tasks Triggers when a new task is added to an organisation.
  • Watch Timesheet Entries Triggers when a new time entry is added to an organisation.
  • Watch Users Triggers when a new user is added to an organisation.

Explore alternative integrations

There are other apps [9] supported by WEXTL that can be paired with Aladtec and Keeping integrations. Pick any from the list below if the current combination isn't the one you need.

Automate Aladtec and Keeping on WEXTL®

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

Cancel anytime.

Frequently asked questions

Common questions about connecting Aladtec and Keeping.

How do I connect Aladtec and Keeping?

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

Example: when Aladtec's "Watch Accrual Bank" fires, WEXTL can "Archive a Project" in Keeping. Aladtec has 7 triggers (including Watch Accrual Bank, Watch Group, and Watch Kiosk); Keeping has 31 actions (including Archive a Project, Archive a Task, and Create a Client). Add filters and transforms between steps when you need them. [1]

Can Aladtec trigger actions in Keeping, and Keeping in Aladtec?

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

Do I need to write code to integrate Aladtec and Keeping?

No. Aladtec-to-Keeping 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 Keeping in real time?

Yes. Trigger-based automations start the moment Aladtec (or Keeping) 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 + Keeping integration?

A first automation typically takes 5–10 minutes: connect each app's credential 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 Keeping?

You can build your Aladtec + Keeping automation on a 3-day trial with every feature unlocked. Cancel anytime. For your protection, a small deposit is charged to your card when your trial starts. It counts toward your first payment and is non-refundable. [8]

References

List of sources used to gather information about the Aladtec and Keeping integration.

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

Explore Aladtec and Keeping, or get started