Part of Task Hub Cross-App Links
One customer record across CRM, Booking Hub, Contacts and Vehicle Hub
A card can hold a typed reference to a record in another KIMISUITE app — a CRM lead, a Booking Hub reservation, a Contact, a Vehicle Hub vehicle. Clicking the chip opens the source record in a new tab.
More importantly, automation rules can listen to cross-app triggers. A lead winning in CRM, a reservation being confirmed in Booking Hub, a payment landing on a linked invoice — any of these can drive Task Hub state changes without anyone typing into Task Hub. When the source app is briefly unavailable, the chip stays usable thanks to the cached display name; only the click-through pauses until the source is back.
Key Benefits
Four supported source apps today: CRM (leads), Booking Hub (reservations), Contacts (people), Vehicle Hub (vehicles). More on the roadmap.
Search the source app from inside Task Hub — the picker proxies the query to that app so you don't need to switch tabs.
Chips cache the display name and source-record ID — if the source app is down, the chip still renders.
Three cross-app automation triggers: lead status changes, reservation confirmed, payment received.
Use Cases
Sales follow-up
A card "Follow up with Acme Corp" links to the CRM lead. When the lead's status flips to Won, an automation rule moves the card to Done and posts a comment. Your sales team works in CRM; your operations team sees the result in Task Hub.
Hotel operations
A card "Prepare welcome basket" links to a Booking Hub reservation. When the reservation is confirmed, the rule auto-creates the prep card with a due date 24 hours before arrival. Reception drives operations without manual hand-offs.
Vehicle prep
A card "Photograph and list BMW 3-series" links to the vehicle in Vehicle Hub. Open the chip to see the live vehicle record — current photos, current price, current status. Update once in Vehicle Hub, see the update on the card.