Log inStart trial

Ashby and Keeping Integration

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

Build hr workflows between Ashby 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.

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

Learn about Ashby and Keeping

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

  • Ashby

    • HR
    • 1 trigger
    • 12 searches
    • 18 actions

    All-in-one recruiting ATS with analytics, scheduling, and candidate CRM. [5]

  • Keeping

    • HR
    • 6 triggers
    • 12 searches
    • 19 actions

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

How to connect Ashby to Keeping

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

  1. STEP 1

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

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

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

Ashby triggersKeeping actions

Ashby modules

  • Add a Candidate to a Project Adds a candidate to an existing project.
  • Anonymize a Candidate Anonymizes a candidate. This action cannot be reversed and requires all of the candidate's applications to be in the archived or hired state.
  • Archive an Opening Archives an opening.
  • Create a Candidate Creates a Candidate.
  • Create a Candidate Note Creates a new note for a candidate.
  • Create a Job Creates a Job.
  • Create a Job Opening Creates a Job Opening.
  • Get a Candidate Retrieves a single candidate by ID.
  • Get a Job Retrieves details for a specific job.
  • Get a Job Posting Retrieves details for a specific job posting.
  • List Candidate Client Info Retrieves a list of client information for a specified candidate.
  • List Candidate Notes Retrieves a list of notes for a candidate.
  • List Candidates Retrieves a list of candidates.
  • List Interviews Retrieves a list of interviews.
  • List Job Postings Retrieves a list of job postings.
  • List Jobs Retrieves a list of jobs.
  • List Openings Retrieves a list of openings.
  • Make an API Call Performs an arbitrary authorized API call.
  • Search Candidates Searches for candidates by name or email.
  • Search Openings Searches for openings matching the given criteria.
  • Tag a Candidate Sets a specified tag to a candidate.
  • Update a Candidate Updates a Candidate with new field values.
  • Update a Job Updates a Job with new field values.
  • Update a Job Posting Updates a Job Posting with new field values.
  • Update a Job Status Updates the status for a specified job.
  • Update an Opening Updates an Opening with new field values.
  • Update an Opening State Updates a state of the opening.
  • Update Job Compensation Updates compensation rates for a specified job.
  • Upload a Candidate Resume Uploads a candidate's resume, parses it, and updates their information.
  • Upload a File to a Candidate Uploads a file to a candidate record.
  • Watch Events Triggers when a specific event occurs.

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

Automate Ashby and Keeping on WEXTL®

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

Cancel anytime.

Frequently asked questions

Common questions about connecting Ashby and Keeping.

How do I connect Ashby and Keeping?

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

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

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

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

Does Ashby integrate with Keeping in real time?

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

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

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

Explore Ashby and Keeping, or get started