Across every block
The short, true list.
A connector named on a marketing page is a commitment a buyer quotes back at you, so here is the whole list.
What you get
Everything below ships today.
- A v1 REST APIPeople, tasks, processes, result areas, KPIs, KPI readings and recognitions, with an OpenAPI document you can generate a client from.
- CSV inImport into a table from a spreadsheet, which is how most teams move the data they actually care about.
- CSV outExports for activity, compliance, people, reviews and the whole of your own data.
- Email that worksInvitations, reminders and cycle notifications reach a mailbox. That is a delivery path, not an integration.
- Why the list is shortMost connectors exist to keep two products in step. Eight blocks on one data model is the other answer to that problem, and it is the one this product took.
- Connectors are demand drivenWe build one when customers ask for the same one. None ships today, so none is named here, on the comparison table, or in a sales call.
Questions
Straight answers.
Do you connect to my chat, my identity provider or my accounting product?
No. Nothing connects to a third party product today.
Can I build the connection myself?
Yes, against the v1 API. It is the same data model the product uses.
Is there a rate limit I should design for?
Yes: 120 requests a minute and 50,000 a day per key, counted in fixed calendar minute and day buckets, and adjustable per key.