# Between Make sessions

The Optimal Flow · Learn · Version 1.0 · 2026-10-13

Three Tally → HubSpot variations: trace a field, check an empty entry and review an update by email.

Three optional 10–15 minute tasks between the four sessions of the eight-hour reference edition. Materials are included and a brief recap is agreed within those eight hours. They are not attendance requirements or an additional diploma condition. They do not add individual review outside sessions; existing support retains its limits.

The programme remains Tally → preparation and filter → HubSpot. CSV files are local classroom data, not a new application or importable blueprint. They contain no credentials or API calls. Use only authorised practice copies and connections; do not contact real people or activate sending.

## How to use the tasks

Extract the ZIP and open README.md. Choose the task between its two sessions. Recall before consulting the answer, try with the included data, check the result and keep one reflection or question. Stop at the end of the suggested time. No out-of-class submission is required.

### M1 · Trace fields before executing

After session 1 → before 2.

Without opening the answer, draw the Tally source and HubSpot contact and recall which value identifies the enquiry.

- Read inputs/M1-mapping.csv and the fictional enquiry. Two logical destinations are swapped: identify them and prepare the correct mapping on paper.
- If you already have an authorised classroom copy, compare the labels with the agreed contact properties. Do not create properties, connections or real contacts for this task.
- Record one form field, its value and where it should appear on the contact. Do not claim it reached the CRM if you only reviewed mapping.

Data in inputs/M1-mapping.csv.

The CSV and M1-data.md include all values. Draw the mapping on paper or in Markdown and mark “not executed in Make/HubSpot”. This does not establish a connection or access.

### M2 · Test an email containing only spaces

After session 2 → before 3.

Recall the order: prepare the email before checking that it contains a value.

- Read the three fictional entries in inputs/M2-requests.csv. For each, write the email after trimming leading/trailing spaces and converting to lowercase.
- Decide which entries would pass Email present and which would stop before the CRM, then compare with the answer.
- Only if the test environment is already authorised, run the agreed entries in the classroom copy and record observations. Do not send messages or activate operational scenarios.

Data in inputs/M2-requests.csv.

Use the CSV or M2-data.md and calculate values/decisions on paper. Record “prediction; not executed”; this is not equivalent to reading real scenario history.

### M3 · Check what changed on the existing contact

After session 3 → before 4.

Recall why repeating the same prepared email must be compared with the existing classroom contact.

- Read inputs/M3-existing-contact.csv, M3-request.csv and M3-fictional-trace.csv. The fictional trace retains the ID but the company contains a person’s name.
- Compare expected and fictionally observed values. Identify the incorrectly mapped field and write the correction without changing the email key.
- Describe a controlled repeat with a new practice response and the same email: which ID, email and company you would check. Run it only in an authorised copy, without contacting real people.

Data in inputs/M3-fictional-trace.csv.

All states are in CSV and M3-data.md. Complete a comparison table on paper/Markdown and mark “fictional trace; not executed”. This does not demonstrate a real update.

## If blocked

- If you cannot open the workspace, use a feature or confirm an authorised environment, stop execution; do not share passwords or change operational permissions.
- Use the paper/Markdown data and record “not executed in the tool”; this alternative supports reasoning but does not establish access or practice in the application.
- Keep one question and the blocker for the next session’s brief recap. Do not repeat actions on real contacts or treat access as resolved.

## Record and recap

practice-log.csv starts empty. You may record the task, mode, expected and observed or predicted result, blocker and one question. Attempt/review dates and real evidence are completed only when they happen. A brief recap is agreed within the existing eight hours; no individual out-of-session review or unlimited support is added. These tasks do not condition the diploma.

[Download the ZIP pack](make-en-v1.zip)