ClickTime and Keeping Integration

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

Build hr workflows between ClickTime and Keeping 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 ClickTime and Keeping

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

  • ClickTime

    • HR
    • 4 triggers
    • 23 searches
    • 24 actions

    Time tracking and workforce timesheet software for projects, billing, and attendance. [5]

  • Keeping

    • HR
    • 6 triggers
    • 12 searches
    • 19 actions

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

How to connect ClickTime to Keeping

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

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

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

ClickTime triggersKeeping actions

ClickTime modules

  • Add Expected Work Hours Adds expected work hours for a user.
  • Create a Client Creates a new client.
  • Create a Job Creates a job with the specified parameters.
  • Create a Task Creates a new task in the system.
  • Create a Time Entry Creates a time entry for a specific user.
  • Create a Time Off Entry Creates a time off entry for a specified user.
  • Create a User Creates a new user in the system.
  • Create an Alternative Time Off Entry Creates an alternative time off entry in the system.
  • Delete a Client Deletes a client from the database.
  • Delete a Job Removes a job from the system.
  • Delete a Task Deletes a task from the service.
  • Delete a Time Entry Deletes a time entry for a specific user.
  • Delete a Time Off Entry Deletes a time off entry from the system.
  • Delete a User Deletes a user from the database or system.
  • Delete an Alternative Time Off Entry Deletes an alternative time off entry from the system.
  • Get a Client Retrieves the details of a specific client by ID.
  • Get a Custom Message Retrieves a custom message based on specified criteria.
  • Get a Job Retrieves details about a specific job.
  • Get a Task Retrieves a specific task by its ID.
  • Get a Time Entry Retrieves a time entry for a specific user.
  • Get a Time Off Entry Retrieves a time off entry for a specified user.
  • Get a Time Report Retrieves time report data.
  • Get a Timesheet Completion Report Gets timesheet completion information.
  • Get a User Retrieves information about a specific user.
  • Get Allocation Summaries Gets allocation summaries grouped by job or user.
  • Get Alternative Time Off Entries Retrieves alternative time off entries from the service.
  • Get an Alternative Time Off Entry Retrieves an alternative time off entry from the service.
  • Get Clients Retrieves a list of clients from the service.
  • Get Custom Messages Retrieves custom messages based on specified criteria.
  • Get Daily Time Summary Retrieves a summary of time entries for a specific day.
  • Get Expected Work Hours Gets the expected work hours for a user.
  • Get Expected Work Hours by ID Gets expected work hours for a specific ID.
  • Get Jobs Retrieves information about jobs from the service.
  • Get Tasks Retrieves a list of tasks from the service.
  • Get Time Entries Retrieves time entries from the service.
  • Get Time Off Entries Retrieves time off entries from the service.
  • Get Users Retrieves a list of users from the service.
  • Get Weekly Time Summary Retrieves a summary of time entries for the week.
  • Make an API Call Makes an API call to a specified endpoint.
  • Update a Client Updates a client record with new information.
  • Update a Job Updates a job with new information or changes existing details.
  • Update a Managed User Updates a managed user in a specific system.
  • Update a Task Updates a task with new information.
  • Update a Time Entry Updates a time entry for a specific user.
  • Update a Time Off Entry Updates a time off entry for a specific user.
  • Update a User Updates a user's information in the system.
  • Update an Alternative Time Off Entry Updates an alternative time off entry for a specific user.
  • Watch Alternative Time Off Triggers when alternative time off is available or updated.
  • Watch Jobs Triggers when a new job is created or updated.
  • Watch Time Entries Triggers when a new time 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 ClickTime and Keeping integrations. Pick any from the list below if the current combination isn't the one you need.

Automate ClickTime and Keeping on WEXTL®

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

Cancel anytime.

Frequently asked questions

Common questions about connecting ClickTime and Keeping.

How do I connect ClickTime and Keeping?

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

Example: when ClickTime's "Watch Alternative Time Off" fires, WEXTL can "Archive a Project" in Keeping. ClickTime has 4 triggers (including Watch Alternative Time Off, Watch Jobs, and Watch Time Entries); 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 ClickTime trigger actions in Keeping, and Keeping in ClickTime?

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

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

Does ClickTime integrate with Keeping in real time?

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

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

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

Explore ClickTime and Keeping, or get started