ClockIt and Keeping Integration

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

Keep ClockIt and Keeping in sync by integrating their events and actions. When hr events happen in ClockIt, update the Keeping 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 ClockIt and Keeping

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

  • ClockIt

    • HR
    • 1 trigger
    • 8 searches
    • 2 actions

    Employee time tracking and attendance management platform with clock-in/out, leave management, and scheduling. [5]

  • Keeping

    • HR
    • 6 triggers
    • 12 searches
    • 19 actions

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

How to connect ClockIt to Keeping

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

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

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

ClockIt triggersKeeping actions

ClockIt modules

  • Clock In or Out User Clocks a specified user in or out, recording the attendance event with a timestamp.
  • List Attendance Report Returns employee attendance records filtered by a specified date range.
  • List Checking Logs Returns a list of employee check-in and check-out log entries for a given date range.
  • List Holidays Returns all configured holidays that fall within a specified date range.
  • List Leave Balance Returns the remaining leave balance for each leave type assigned to a specific user.
  • List Leave Requests Returns employee leave requests submitted within a specified date range.
  • List Mobile Geofence Restrictions Returns the mobile geofence restriction zones configured for a specific user.
  • List Time Logs Returns time log entries for employees within a specified date range.
  • List Web IP Restrictions Returns the web IP address restrictions configured for a specific user.
  • Make An API Call Executes an authenticated request to any ClockIt API endpoint.
  • Watch Time Logs Triggers when a new time log entry is created or updated.

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

Automate ClockIt and Keeping on WEXTL®

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

Cancel anytime.

Frequently asked questions

Common questions about connecting ClockIt and Keeping.

How do I connect ClockIt and Keeping?

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

Example: when ClockIt's "Watch Time Logs" fires, WEXTL can "Archive a Project" in Keeping. ClockIt has 1 trigger (including Watch Time Logs); 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 ClockIt trigger actions in Keeping, and Keeping in ClockIt?

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 ClockIt and Keeping?

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

Does ClockIt integrate with Keeping in real time?

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

You can build your ClockIt + 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 ClockIt and Keeping integration.

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

Explore ClockIt and Keeping, or get started