When Hudu pulls in data from external platforms, it uses a concept called a card to store and move that information, "stacking" data from multiple sources under a single, readable asset. Cards are stored within customizable asset layouts (categories) inside each client space.
A card can contain data from manual input, a .csv import, or an external source (API and integrations) — but a single card holds data from only one source (manually entered and imported information are both treated as "custom"). Multiple cards that match by company and asset name are stacked under a single asset. If a mismatch occurs, you can move an integration card to another asset.
Visit Understanding Integrations, Connected Fields, and Asset Layouts for additional information on integrations, mapping data into custom fields, and building layouts.
Guides
Advantages of the card
If you're coming from other documentation tools, cards provide the following benefits:
- Consolidation of your documentation. Information about a single asset is no longer split across different pages, which means fewer manual relationships to create and fewer clicks.
- Consolidation across services. Information from multiple sites and services is merged onto a single asset page for better organization and simpler workflows.
- Custom documentation. Add information your integrations may not collect — create custom fields, add comments and passwords, attach photos and files, and more — all displayed on the same page as your integration data.
How cards are added
Cards are added to Hudu in two ways: as custom cards or as integration cards.
Information added to an asset — either imported into a custom asset layout or entered manually into asset layout fields — goes into a custom card. The custom card is always the first card on an asset page, and it's the only card whose details are editable from inside Hudu.
The fields on a custom card come from the asset layout (Hudu admin → Asset Layouts). Adding or removing fields adds or removes the ability to populate those fields across all client spaces.
Visit Asset Layouts to learn more about custom fields and asset layouts.
When you set up an integration, you choose which asset layout its information goes into — for example, sending Office 365 users into a "People" or "Contacts" layout.
Incoming cards first look for a matching asset. Hudu's matching algorithm considers several factors, but company name and asset name are the priority elements. If it finds a suitable asset, the card is placed under it; if not, a new asset is created.
Once an asset and card are paired, they stay paired. An admin or super admin can rematch an integration card to a different asset using Move (see the Move Card tool below).
Tools
The sections below introduce tools related to cards. Expand each for an overview.
Native integrations automatically re-sync every 3 hours. You can bypass that timing directly on a card: within an asset, click re-sync at the top of any integration card to kick off a new sync for that card only — no other cards from the same integration are affected.
Because cards are matched primarily on company and asset name, an integration card can occasionally land under the wrong asset. A Move button at the top of every integration card (next to re-sync) lets you change the asset layout an integration card belongs to.
For example, "John's Desktop" (pulled in from Syncro) may have landed in a "Printers" layout when it belongs in "Workstations." Click Move, select the target layout (Workstations), and choose to either:
- Create a new asset there to hold the card, or
- Merge it with an existing asset (e.g. "Johns_Desktop").
FAQ
No. Each card holds data from a single source. Manual input and .csv imports are both treated as "custom," while each integration contributes its own card. Cards from different sources stack together under one asset.
The custom card — always the first card on an asset. Integration cards reflect the data synced from their source system.
Yes. With Connected Fields, you can bind a custom field to a data point from an integration so it populates automatically and updates on each sync — putting integration data directly into your custom fields (and list views/search) rather than only on the integration card.
Visit Connected Fields for additional information.
Native integrations automatically re-sync every 3 hours. You can also re-sync manually at the integration level or on an individual card at any time.
Troubleshooting
Use Move at the top of the integration card to rematch it. Select the correct asset layout, then either create a new asset there or merge the card with an existing asset. Moving requires the admin or super admin role.