Skip to main content

Connected systems

Connected systems provide data and actions that do not come directly from HubSpot. Connections are chosen per card, while any credentials are owned by the organization.

Open the dialog

Choose Connected systems in the designer toolbar. The dialog shows:
  • systems and operations already added to the card;
  • available operations that can be connected;
  • a summary of the HubSpot and association data the card uses automatically.
The HubSpot record’s fields and associated records are not managed manually here. They are added when you pick them where they are used.

Add a system

Choose an operation under Connect. It immediately becomes available in dynamic field pickers, tables, charts, repeaters, and relevant actions. The current product version registers demo operations for:
  • Dinero (demo) — open invoices and create note;
  • Inventory (demo) — stock status.
Demo data is deterministic and never sends anything to a real external system. A production environment can register live adapters with the same data contract, so a card can switch backends without changing its bindings.

Rename and format fields

Choose Rename fields on a connection. For each known field you can change:
  • Shown as — the label users see in field pickers and on the card;
  • Format — automatic, text, number, currency, date, date and time, percent, or status chip.
The mapping only applies to the current card. It does not change the field’s name in the source system.

Remove a connection

Choose Remove. First check whether any building blocks or actions use its fields. A binding to a removed source makes the card invalid and blocks publishing.

Data errors

A connector can be configured to show an error state or hide data on failure. The current designer does not expose this choice; new connector sources use the connector’s default behavior. If data is missing:
  1. check that the operation is still listed as connected;
  2. check that the building block uses the right list or field;
  3. check that the required input data exists on the record;
  4. check the organization connection if the environment uses a live adapter;
  5. reload data with a button action if the source may be cached.
See Data and display errors for more things to check.