CharlieHR Integration

Connect CharlieHR when approved leave should appear in Keito Planning. The integration syncs leave into availability so project planning can account for holidays, sick leave, and other configured leave types.

Requirements

  • A Keito Business plan subscription.
  • Keito Planning enabled.
  • Administrator access in Keito.
  • CharlieHR API credentials.

What It Does

The CharlieHR integration can:

  • Validate and store CharlieHR API credentials.
  • Read company, team member, leave type, and leave request data from CharlieHR.
  • Map CharlieHR team members to Keito members.
  • Map CharlieHR leave types to Keito planning availability types.
  • Sync approved leave into Keito Planning.
  • Poll on a schedule and run a manual Sync now when needed.

How It Works

CharlieHR is a workspace-level planning integration. A Keito admin adds CharlieHR API credentials, maps CharlieHR members to Keito members, maps CharlieHR leave types to Keito planning availability types, and chooses which leave types should affect capacity.

Keito reads approved leave inside the configured sync window. It creates or updates planning availability records in Keito so project schedules account for holidays and other leave. CharlieHR remains the source of truth for leave approval; Keito uses the approved leave to keep planning capacity accurate.

Connect CharlieHR

  1. Go to Settings > Integrations > CharlieHR.
  2. Enter the CharlieHR client ID and client secret.
  3. Validate the credentials.
  4. Set the sync window, such as days back and days forward.
  5. Map CharlieHR team members to Keito team members.
  6. Map leave types and choose which ones should sync.
  7. Run Sync now and review planning availability.

Sync Window

Keito syncs leave inside the configured date window. A typical setup imports a small amount of history and a larger amount of future leave, for example 30 days back and 120 days forward.

The sync window keeps planning current without repeatedly scanning unnecessary historical leave.

Member And Leave Type Mapping

Member mappings control who the leave belongs to in Keito. Leave type mappings control how the leave affects planning availability.

For each leave type, review:

  • Whether the type is synced.
  • Whether it deducts capacity.
  • Whether it should be treated as sensitive.
  • Which Keito planning availability type it maps to.

Data And Permissions

Keito reads the CharlieHR data needed to create planning availability records. It stores credentials securely and uses them only for the configured workspace.

Sensitive leave types should be mapped carefully. When a leave type is marked sensitive, use a generic label in Keito planning rather than exposing unnecessary HR detail to project planners.

Disconnect CharlieHR

  1. Go to Settings > Integrations > CharlieHR.
  2. Disable sync if you want to pause polling without removing mappings.
  3. Click Disconnect CharlieHR to remove the credentials.
  4. Confirm the disconnect.

Disconnecting stops future CharlieHR polling and removes Keito’s access to CharlieHR. Existing planning availability created from previous syncs remains available for historical planning context. Review future availability after disconnecting if CharlieHR should no longer drive capacity.

Troubleshooting

Credentials fail validation

Check the CharlieHR client ID and secret, then confirm the credentials have access to the company, team members, leave types, and leave requests.

Leave is missing from planning

Check that the leave request is approved in CharlieHR, falls inside the configured sync window, and has a mapped member and enabled leave type.

A member needs review

Map the CharlieHR team member to the correct Keito member, then run Sync now again.