Log inStart trial

BuddyPunch and Keeping Integration

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

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

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

  • BuddyPunch

    • HR
    • 2 triggers
    • 14 searches
    • 13 actions

    Employee time clock and attendance tracking for hourly 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 BuddyPunch to Keeping

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

  1. STEP 1

    Connect BuddyPunch 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 BuddyPunch 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 BuddyPunch and Keeping. Use filters or leverage a JS custom code step in between — everything is on the canvas.

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

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

BuddyPunch triggersKeeping actions

BuddyPunch modules

  • Assign Department Codes Assigns department codes to a location.
  • Assign Employees to a Location Assigns employees to a location.
  • Create a Location Creates a new location.
  • Create a Position Creates a new position.
  • Create a Punch In Records a punch-in time for attendance management.
  • Create an Employee Creates an employee record in the system.
  • Get a Location Retrieves a specific location using the provided criteria.
  • Get a Position Retrieves a specific position.
  • Get a Schedule Retrieves a schedule.
  • Get a Time Card Retrieves a specific time card by ID.
  • Get an Employee Retrieves a specific employee.
  • Get Pay Rates Retrieves pay rates for an employee.
  • List Assigned Employees Retrieves employees assigned to a location.
  • List Employees Retrieves a list of employees.
  • List Locations Retrieves a list of locations.
  • List Pay Periods Retrieves a list of pay periods.
  • List Positions Retrieves a list of positions.
  • List Time by Pay Period Retrieves time entries for a pay period.
  • List Time Cards by Pay Period Retrieves time cards for a pay period.
  • List Time Entries for a Time Card Retrieves time entries for a time card.
  • Make an API Call Performs an arbitrary authorized API request.
  • Record a Punch-Out Time Records a punch-out time for an employee or user.
  • Remove Department Codes Removes department codes from a location.
  • Remove Employees Removes employees from a location.
  • Update a Location Updates an existing location in the system.
  • Update a Position Updates an existing position.
  • Update an Employee Updates an existing employee.
  • Watch Employees Triggers when a new employee is added or an existing employee is updated.
  • Watch Positions Triggers when a new position is available or an existing position is 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 BuddyPunch and Keeping integrations. Pick any from the list below if the current combination isn't the one you need.

Automate BuddyPunch and Keeping on WEXTL®

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

Cancel anytime.

Frequently asked questions

Common questions about connecting BuddyPunch and Keeping.

How do I connect BuddyPunch and Keeping?

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

Example: when BuddyPunch's "Watch Employees" fires, WEXTL can "Archive a Project" in Keeping. BuddyPunch has 2 triggers (including Watch Employees and Watch Positions); 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 BuddyPunch trigger actions in Keeping, and Keeping in BuddyPunch?

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

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

Does BuddyPunch integrate with Keeping in real time?

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

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

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

Explore BuddyPunch and Keeping, or get started