Skip to main content

Integrations for performance

The performance engine can score work that happens outside the HRM: pull requests and code reviews on GitHub, and support tickets in WHMCS. This page covers connecting both, mapping their logins to your employees, and the triage tools built on top.

Everything here lives under Admin → Integrations (/admin/integrations). The whole surface — including background polling — is available only on plans that include the performance feature.

Who can do what

Connection setup (credentials, repos, polling) needs company.settings. Anything that decides whose ledger points land in — linking identities, triaging flagged reviews, voiding scores — needs performance.manage instead. The seeded HR Manager and Super Admin roles hold both.


Slack​

Enterprise plan

Slack and the other connections below, down to the ledgers, are part of the Integrations feature, which comes with the Enterprise plan and the free trial. A workspace on another plan does not see their cards on the Integrations page.

Open Admin → Integrations → Slack (/admin/integrations/connections/slack).

  1. In Slack, add the Incoming Webhooks app to the channel that should receive HR updates and copy the webhook URL it generates.
  2. Paste the URL on the Slack page, optionally note the channel name for your own reference, and press Connect & test. The app posts one line to the channel to prove the URL works; the URL is stored encrypted and shown back only as a mask.
  3. From then on the channel receives one line for each event ticked under Events sent to this integration. Every event is ticked to begin with. Untick the ones you do not want in the channel and press Save.
AreaA line is posted when
Leaveleave is requested, approved, rejected or cancelled
Peoplea team member is added, an employee record is removed, onboarding is completed, offboarding is completed
Payrolla payroll run is approved or locked (on plans that include payroll)
Contractsa contract is signed
Expensesan expense claim is submitted or approved
Performancean appraisal is finalised (on plans that include performance)
Assetsan asset is issued

Each line names the person and what happened, with the dates for leave. It never carries the reason for a leave request or a rejection, an appraisal rating, or what an expense claim was for or how much it was worth. Those stay in the app, where permissions decide who reads them.

The lines are written in the workspace's Default email language (Workspace Settings → Language), whoever caused the event and whatever language they use the app in. A channel is shared, so it gets one language. The Slack page itself, like every other screen, follows the language each admin has chosen.

Choose the channel with care

Everyone in the channel sees who is on leave, whose claim was approved and who is leaving. Point the webhook at a channel whose members may know that, and untick the events that do not belong there.

Slack accepts about one message a second per webhook. In a burst (a bulk import, for example) messages wait for Slack and go out in turn. If Slack keeps turning a message away it is skipped, and the Slack page shows Slack's answer, but the connection stays on.

If Slack refuses three messages in a row because the webhook itself no longer works (it was removed, or the channel was archived), the card on the Integrations page turns to Needs attention and nothing more is sent. Fix the URL (or re-add the webhook in Slack) and press Test connection; deliveries resume once a test succeeds. Disconnect deletes the stored URL and stops the messages.

Slack and the integrations that follow it share one layer, so each new one appears as a card on the Integrations page as soon as this installation offers it.


Microsoft Teams​

Enterprise plan

Like Slack, Teams comes with the Enterprise plan.

Open Admin → Integrations → Microsoft Teams (/admin/integrations/connections/teams). Teams receives the same lines as Slack, from the same list of events, in the workspace's Default email language, with the same care about what a line says and does not say.

  1. In Teams, next to the channel that should receive HR updates, open More options (…) → Workflows and choose the template Send webhook alerts to a channel. Save it, then copy the webhook link Teams shows.
  2. Paste the link on the Teams page, optionally note the channel name for your own reference, and press Connect & test. One line is posted to prove the link works; the link is stored encrypted and shown back only as a mask.
  3. Untick under Events sent to this integration whatever does not belong in the channel, and press Save.

Only the Send webhook alerts to a channel template works: the two "from specific people / from people in an org" templates expect a signed-in caller, which an app is not.

The old Office 365 connector webhooks no longer deliver

Microsoft retired the classic Incoming Webhook connector in May 2026. A link of that kind (…webhook.office.com/webhookb2/…) is refused when you paste it, because Teams would still answer it politely and post nothing. Create a workflow webhook instead.

Two things about workflows worth knowing: a workflow belongs to the person who created it, so add a co-owner in the Workflows app before that person leaves, and Teams may switch off a workflow that has not fired for 90 days. If the card turns to Needs attention with "WorkflowNotFound" or "trigger is not enabled", that is what happened: turn the workflow back on, or create it again and paste the new link.


Mattermost​

Enterprise plan

Like Slack, Mattermost comes with the Enterprise plan.

Open Admin → Integrations → Mattermost (/admin/integrations/connections/mattermost). Mattermost receives the same lines as Slack, from the same list of events, in the workspace's Default email language, with the same care about what a line says and does not say.

  1. In Mattermost, open the main menu → Integrations → Incoming Webhooks → Add Incoming Webhook, pick the channel that should receive HR updates, save, and copy the URL it shows. It looks like https://your-mattermost.example.com/hooks/…; a system admin may need to switch incoming webhooks on first (System Console → Integrations → Integration Management).
  2. Paste the URL on the Mattermost page, optionally note the channel name for your own reference, and press Connect & test. One line is posted to prove the webhook works; the URL is stored encrypted and shown back only as a mask.
  3. Untick under Events sent to this integration whatever does not belong in the channel, and press Save.

Because Mattermost runs on your own server, the webhook URL has your server's address in it, so the app only checks its shape (https://, then /hooks/ and the key); the test post is what proves it. Names and codes in the lines are written so that Mattermost reads them as plain text: a person whose name contains @channel does not page the channel. If the card turns to Needs attention with "Invalid or expired webhook", the webhook was deleted on the Mattermost side: create a new one and paste its URL.


Google Chat​

Like Slack, Google Chat comes with the Enterprise plan.

Open Admin → Integrations → Google Chat (/admin/integrations/connections/google_chat). Google Chat receives the same lines as Slack, from the same list of events, in the workspace's Default email language.

  1. In Google Chat, open the space that should receive HR updates, click its name → Apps & integrations → Webhooks → Add webhooks, give it a name, save, and copy the URL. It starts with https://chat.googleapis.com/v1/spaces/. Webhooks are set up in a browser, not in the mobile app, and your Google Workspace administrator has to allow them.
  2. Paste the URL on the Google Chat page, optionally note the space's name for your own reference, and press Connect & test. One line is posted to prove the webhook works; the URL is stored encrypted and shown back only as a mask.
  3. Untick the events that do not belong in that space, and save.

The URL carries its own key and token, so treat it as a password: anyone who has it can post to the space. The app accepts only a URL on Google's own address and refuses anything else. Names and codes in the lines are written so that Google Chat reads them as plain text: a name cannot mention the whole space or pose as a link. If the card turns to Needs attention with "Requested entity was not found", the webhook was removed on the Google side: add a new one and paste its URL.


Google Calendar and Outlook Calendar​

Enterprise plan

Both calendars come with the Enterprise plan, and work once the operator has registered the Google or Microsoft app for this installation (the card says Available until then).

Approved leave on a calendar the team already looks at. Open Admin → Integrations → Google Calendar (/admin/integrations/connections/google_calendar) or Outlook Calendar (/admin/integrations/connections/outlook_calendar) and press Connect.

  1. Sign in with the account that should hold the calendar: a shared HR account is a better choice than a personal one, because the calendar lives in that account. Google asks for permission to create calendars of the app's own; Microsoft asks for calendar access. Leave both ticked.
  2. The app creates a calendar named Team leave: your workspace in that account, right away. It never reads or writes any other calendar there.
  3. Share that calendar with whoever should see it. In Google Calendar: open the calendar's Settings and sharing, then Share with specific people or groups, or Access permissions for events → Make available for your organisation. In Outlook on the web: Share on the calendar's toolbar, choose the calendar, add people, and pick Can view all details.

From then on, approving a leave request adds an all-day entry for its dates, and cancelling the leave removes it. Requests that are still pending are not shown. Half days are marked. The entry blocks nobody's time (it shows as free), so the people it is shared with keep their own availability.

What an entry shows is a setting on the page. Name only (the default) writes "Sara Khan: on leave" and nothing more; Name and leave type writes "Sara Khan: Annual leave". Anyone the calendar is shared with can read its entries, so the default keeps sick leave and the like out of them. The entries are written in the workspace's Default email language.

The Activity list at the foot of the page shows each entry made or removed, when, and any entry that could not be made, with the reason and a Try again button; an entry that failed for a passing reason (the calendar service was down) is tried again on its own, for up to a day.

On a workspace with the Scheduling plan feature the connection also keeps a second calendar, Team schedule: your workspace, created the first time a roster is published. Every published shift is a timed entry there ("Sara Khan: Night", 22:00–06:00 in Sara's branch timezone, the planner's note underneath), one per person per day; a day taken off the roster removes its entry, a change rewrites it. Share this calendar separately from the leave one — a team lead may need the schedule without everyone's leave. Draft days and standing shifts that the roster has not published are not written.

If the calendar is deleted in Google or Outlook, the next approved leave (or published roster) creates a fresh one; share it again. Disconnecting stops the entries and forgets the account, but leaves the calendar and its entries where they are, for you to delete by hand. Reconnecting with the same account picks the existing calendar up again.


QuickBooks Online, Xero and Zoho Books​

Enterprise plan

The ledgers come with the Enterprise plan, and need a plan that includes payroll, as Enterprise does. A card says Available until the operator has registered that ledger's app for this installation.

One journal per locked payroll run, in your own books. Open Admin → Integrations → QuickBooks Online (/admin/integrations/connections/quickbooks), Xero (/admin/integrations/connections/xero) or Zoho Books (/admin/integrations/connections/zoho_books), press Connect, and choose the company (QuickBooks) or organisation (Xero) to post to. For Xero, connect as an adviser or a standard user with reporting rights; a user without them may not create manual journals. Zoho Books connects the Zoho account as a whole: an account with one organisation has it chosen for you; with several, choose the one to post to under Organisation on the connection page and press Save — the account lists below stay empty until you do.

Zoho organisations that allow sign-in from listed IP addresses only

If your Zoho organisation restricts sign-in to listed addresses (Zoho Directory → Admin Panel → Security → Security Policies → Allowed IPs), Connect ends with "The provider refused to issue access": Zoho will not issue the token to the app's own address. Ask your platform operator for the app's outbound IP addresses, add them to the policy and connect again. Keep them there — the hourly token refresh and every journal go out from the same addresses.

Then map the journal's lines to accounts in that ledger's chart of accounts and press Save. Each list is grouped by the kind of account; a sub-account appears under its parent, indented in Zoho Books and by its full name (Payroll:Wages) in QuickBooks. Three accounts are required and the rest are optional refinements that fall back on them:

AccountTakes
Wages expensethe pay employees earned (debit)
Net paywhat employees are paid (credit): a wages-payable or payroll-clearing account, which the payment from your bank then clears
Deductionseverything withheld from pay, unless a more specific account below is chosen (credit)
Employer contributions expensethe employer's own contributions; otherwise wages expense
Expense reimbursementsexpense claims repaid through payroll; otherwise wages expense
Income tax payableincome tax withheld; otherwise deductions
Contributions payableemployee and employer contributions owed to funds; otherwise deductions
Employee loansloan instalments withheld; otherwise deductions

When a payroll run is locked, one balanced journal is posted, dated on the last day of the payroll month: wages, employer contributions and reimbursements on the debit side; tax, contributions, loans, other deductions and net pay on the credit side. It is a summary of the run: the ledger never receives a line per person. Days docked for absence or unpaid leave are not a cost and do not appear. Where the workspace's rounding makes earned pay less what was withheld differ from net pay by a few cents, the difference is posted as a Rounding difference line rather than hidden in another figure. QuickBooks and Zoho Books show the journal with the reference PAY-2026-10; Xero shows a narration that names the month and the number of employees.

For Xero and Zoho Books, Post journals as chooses between a Draft (the default), which waits in the ledger for someone to review and post or publish it, and Posted (Xero) or Published (Zoho Books), which goes straight to the ledger.

The Activity list at the foot of the page shows each run's journal: when it was posted, a link to open it in the ledger, or why it was not posted. Three reasons are the app's own, and are explained on the row:

  • the accounts above are not chosen yet: the journal waits and is posted the moment they are saved;
  • the workspace pays in one currency and the ledger keeps its books in another: nothing is posted, because the amounts would be read in the wrong currency;
  • the run's figures do not add up to its net pay: nothing is posted, and the row asks you to enter that journal by hand. This is deliberate: a journal that looks right and is not is worse than none.

Anything else comes from the ledger in its own words (an archived account, a locked period). Fix the cause and press Try again. A journal that failed for a passing reason (the ledger was down) is tried again on its own, for up to a day. A journal that went through is never posted twice, whatever happens afterwards; runs that were locked before the ledger was connected are not posted at all.

Runs locked before you chose the accounts

A run locked while the accounts were still empty shows as Waiting for you on the Activity list and goes out when you save them. A run locked before the ledger was connected is not on the list; post that one by hand.


GitHub​

Open Admin → Integrations → GitHub (/admin/integrations/github).

  1. Paste a personal access token with read access to the repositories you want tracked. The token is encrypted at rest and never shown again — the page displays a masked value.
  2. Pick the repositories to track from the list the token can reach.
  3. Optionally mark a subset as AI-graded: for those repos the reviewer's written comments (never the code) are also sent for a text-quality grade — catching rubber-stamp approvals and claims that don't match the changed files.
  4. Test the connection, then leave polling to the hourly cron or press Poll now.

What gets scored per repository:

SignalPoints behavior
Merged pull requestAuthor credit, scaled by a difficulty estimate from the change size (lockfiles and vendored files excluded).
Code reviewTimeliness against the review SLA × a depth factor. A requested review that misses its SLA entirely records a penalty — reversed if the review eventually lands.
Voluntary reviewReviewing without being asked never scores below half credit and can never go negative, no matter how old the PR is.
Rescue review / mergeStepping in for an unresponsive assigned reviewer earns bonus credit.
Issues worked / closed / commentedNever scored — surfaced only as attachable evidence for daily reports.
Ignored review requests are still caught

A PR nobody touches never updates, so it would normally fall out of the polling window. The poller separately re-scans every open PR that still has outstanding review requests, so a request that is simply ignored earns its no-show penalty once the SLA lapses.

WHMCS​

Open Admin → Integrations → WHMCS (/admin/integrations/whmcs).

  1. Enter the API URL of the install (its base address). It must be a public https:// address — local hostnames, raw IPs, and internal domains are rejected, because the server calls this URL on a schedule.
  2. Enter the API identifier and secret (and the optional access key, if your install requires one). All three are encrypted at rest.
  3. Set the WHMCS timezone — see below.
  4. Optionally enable AI grading: the replying agent's own messages (never the customer's) are graded for reply quality.

The scored signal is the first staff reply on each ticket: response speed against the WHMCS SLA, times the AI quality grade when enabled. Later replies surface as attachable daily-report evidence but are not scored.

The WHMCS timezone setting​

WHMCS reports timestamps in whatever time zone its PHP configuration uses — not UTC, and not necessarily your workspace's time zone. This field tells the HRM how to read them.

To find the right value: open any recent ticket in the WHMCS admin and check a reply's displayed time. If it shows the actual local wall-clock time the reply happened, enter that zone (e.g. Asia/Karachi). If it shows a time offset from local reality, the install is writing a different zone — enter that one. If WHMCS is genuinely writing UTC, leave the field empty: empty means "read as UTC."

Why it matters

With the wrong value, response-time windows shift and replies get grouped under the wrong day — evening tickets can show up on the next day's report suggestions, and the incremental poll can miss tickets entirely for installs behind UTC.

Linking identities to employees​

Open Admin → Integrations → Identities (/admin/integrations/identities). Every GitHub login and WHMCS agent username the polls encounter appears here, initially unlinked. Nothing is scored for an unlinked identity — its events wait, parked.

Link an identity to an employee and the backlog of parked events is scored immediately and attributed to them. Matching is case-insensitive, so login-case differences can't strand events. Only active (non-deleted) employees can be linked; unlinking stops future attribution but never rewrites history already on the ledger.

Flagged reviews and the void​

When AI grading is on for a repo, reviews the AI judged as rubber_stamp, unsubstantiated, or inconsistent queue up under Admin → Integrations → Flagged reviews (/admin/integrations/github/flagged-reviews) for a human decision.

Each row shows the review, the AI's note, documented test cases, and the points earned. If you agree the review didn't merit its score, Void score appends a reversing ledger entry (after a confirmation — the ledger is append-only, so a void is itself a visible record, not an erasure). Rows already voided are labelled.

This is the same appeal principle as the daily-report verdict override: the AI proposes, a person decides, and every correction leaves a trail.

Polling and reliability​

Both integrations poll hourly (plus the manual Poll now buttons). Requests time out rather than hang, a rate-limited GitHub token pauses the run instead of hammering the API, and one broken repository doesn't stop the others. Connection pages show the last poll time and the last error, if any.