The thread is only as good as what feeds it
TeamPulse reads from the tools your teams already work in. Delivery status, identity, the employee record and the ledger arrive on their own, which is the only reason the analytics on top of them can be trusted.
- Maintained connectors
- 200+
- Maintained connectors
- REST API coverage
- Full
- REST API coverage
- Warehouse sync
- Nightly
- Warehouse sync
- Provisioning
- SCIM
- Provisioning
Connections
The signal is only as good as what feeds it
TeamPulse reads from the tools your team already works in, so nobody has to enter the same thing twice for the analytics to be worth trusting.
Maintained connectors
200+ integrations we build, monitor, and repair when a vendor changes their API.
REST API & webhooks
Every object readable and writable, with event subscriptions for anything you build yourself.
Reverse ETL
Push scored people data into Snowflake, BigQuery, or your warehouse of choice on a schedule.
By category
Where each connection earns its place
Every integration exists to remove a re-key. If a connector does not stop somebody typing the same thing twice, we do not build it.
Delivery
Read project status from where teams already work, so the portfolio layer is current without anyone updating it twice.
- Jira
- Asana
- Linear
- MS Project
- Monday.com
- Trello
HRIS & payroll
Two-way sync on the employee record, or run TeamPulse as the system of record and push outward.
- Workday
- BambooHR
- Rippling
- Gusto
- ADP
- Personio
Identity
Single sign-on and automated provisioning, so leavers lose access the day they leave.
- Okta
- Entra ID
- Google Workspace
- OneLogin
- JumpCloud
- Auth0
Communication
Check-ins, approvals and alerts where people already are, with metadata only and never message contents.
- Slack
- Microsoft Teams
- Zoom
- Google Meet
- Outlook
- Gmail
Finance & ERP
Post journals, map cost centres to projects, and reconcile portfolio spend against the ledger.
- NetSuite
- Business Central
- SAP
- Xero
- QuickBooks
- Sage
Recruiting
Bring candidates in and hand accepted offers straight to onboarding on the same record.
- Greenhouse
- Lever
- Workable
- SmartRecruiters
- Ashby
Four ways in
However your stack is put together
Maintained connectors
We build them, monitor them, and fix them when a vendor changes their API without telling anyone.
REST API
Every object readable and writable, with the same permission model the interface uses.
Webhooks
Subscribe to the events you care about rather than polling for changes on a timer.
Warehouse sync
Push the scored dataset to Snowflake, BigQuery or Redshift for the rest of your modelling.
Getting there
The order that causes least disruption
Connect identity first
SSO and provisioning, so everything after it inherits the right access model.
Bring in delivery
Point your project tool at the portfolio layer and let status flow in automatically.
Sync the people record
Two-way with your HRIS, or make TeamPulse the source and push outward.
Extend where needed
API and webhooks for the systems that are specific to you, which every organisation has.
What changes
What connected teams report
A connector that does not remove a re-key does not ship.
We fix them when the vendor changes the API.
SCIM deprovisioning on the leaver record.
PMO, HR and finance reading the same numbers.
Connect one tool and see the difference
Point your project tracker at TeamPulse and watch the portfolio layer populate itself, with each project asking which objective it serves.