# What connections add

The blocks and behaviours that arrive with a CubeConnect connection, and how to spot them.

For: Workspace owners and admins

## People from CubeHR

The Meet the team block can fill itself from CubeHR when a connection exists: names, roles and photos stay in step with the HR system, and a change there appears on the site at the next publish. Nobody retypes a team list.

The block shows its source in the inspector. Content that arrives this way is not edited on the site; the record in CubeHR is the one that matters.

Walkthrough: A team section filled from CubeHR (A team section filled from CubeHR)

1. **Names and roles, in step**: The Meet the team block fills from CubeHR when a connection exists, and stays in step with changes there.
2. **The source shows**: The inspector says where the content comes from. There is nothing to retype.
3. **The record is the truth**: Edits happen in CubeHR, where the record lives, and arrive on the site at the next publish.

1. Add a Meet the team section.
2. Open the inspector and choose the CubeHR source.
3. Check the names and photos, then publish.

## Enquiries that become tasks

With CubeFlow connected, an enquiry from any form can become a task there, and the message carries a CubeFlow reference so the two records point at each other. The reply side works too: a task completed in CubeFlow is visible from the enquiry.

This is switched on per site in the form settings, so a general contact form can stay a general contact form while a quote request becomes work.

Walkthrough: Enquiries that become tasks (A team section filled from CubeHR)

1. **Send to CubeFlow**: Switched on per form: a quote request becomes work, with the message carrying the reference.
2. **Through CubeConnect**: Everything connected arrives through the one connection, which is why it appears only when connected.

Note: The task lives in CubeFlow with its own owner and dates. CubeSites keeps the message and the reference.

## Products from CubeERP and the client portal

Two blocks go further: Products from CubeERP arrives with a connected CubeERP, and Client portal with a connected support tool. Until the matching connection exists they are listed honestly, marked as needing a Cube app, rather than hidden or half-working.

The website's own shop is different: Basket, Products, Product spotlight, Shop categories and Product search come with the shop and catalogue on Pro, with no connection needed. The same rule holds for connected blocks everywhere: nothing connected appears before it is connected.

Walkthrough: Blocks that wait for a connection (A team section filled from CubeHR)

1. **Listed honestly**: Products from CubeERP and Client portal are shown as needing a Cube app rather than hidden or half-working.
2. **Nothing appears early**: The one rule holds everywhere: no connected feature shows up before it is connected.

- [ ] Every connected block checked after any change in the other product
- [ ] Names and photos published after they change in CubeHR
- [ ] The CubeFlow reference checked on a test enquiry

## Can I edit a name that came from CubeHR?

Not on the site. Change it in CubeHR, where the record lives, and it arrives at the next publish.

## What happens if the connection is lost?

Connected blocks stop updating and say so in the editor. The last published content stays on the site, so nothing breaks in front of visitors.

## Related guides

- [Connect CubeConnect](/help/integrations/connect-cubeconnect)
- [Build a contact form](/help/forms-and-enquiries/build-a-contact-form)
---

CubeSites is a trading name of Cube Systems Limited, part of Crushed Ice Group. Registered in England and Wales, company number 17220899. Registered office: Unit 11, Olney Business Park, Osier Way, Olney, Buckinghamshire, MK46 5FP. ICO registration number ZC216972.

Contact: hello@cubesites.co.uk | 01234 672 617 | https://cubesites.co.uk/contact