Build automations with Make
Learn to build visual scenarios in Make to connect applications, transform information and check how the workflow responds to different input data.
Find your starting point
A good fit when you want to build Make scenarios and learn to follow, transform and check data as it moves through their modules.
- Hours and sessions
- 8 hours live · 4 sessions of 2 h.
- Group size
- Up to 12 participants per trainer as a reference, adjusted to the practice and feedback.
What you will learn
- 01
Design a scenario with connected modules for a focused process.
- 02
Map fields, transform information and use filters to control the path of data.
- 03
Check an execution with valid and incomplete data and locate the step causing an unexpected result.
A proposed programme
You will build a familiar sales automation: taking form details into the CRM. Using practice Tally and HubSpot accounts, you will connect the steps, prepare the fields and check what happens with a new contact, an existing contact and an incomplete entry.
We adapt the selection and depth of the modules to the group's starting point and goals.
01Design the scenario
Process, triggers and modules for connecting the information each step needs.
You will work on
- Define what starts the sales process and which details must reach the CRM.
- Connect the Tally form and HubSpot action in a practice scenario.
- Follow the input and output of an initial run.
- Practice
- Submit a fictional enquiry through the form and relate its fields to the contact created in HubSpot.
- How you will check it
- A workflow the participant can explain: what starts it, where each value comes from and where to check the result.
02Transform and route data
Mapping, functions and filters using examples adapted to the agreed applications.
You will work on
- Map name, company and email between the two tools.
- Remove spaces and normalise the email using text functions.
- Add a filter that stops entries without an email before the CRM.
- Practice
- Compare a complete enquiry with one without an email and check which data the filter allows through.
- How you will check it
- Fields reach the correct properties and the incomplete entry stops at the intended condition; the participant explains the difference.
03Check the workflow
Test executions, reading results and initial guidance for handling exceptions.
You will work on
- Test a new contact and repeat its email with an agreed change to check the update.
- Read inputs, outputs and errors in the run history.
- Document how to review the scenario and when to correct the data or configuration.
- Practice
- Locate an incorrectly mapped field, correct it and submit a new practice response; compare the results and the contact ID.
- How you will check it
- An annotated check showing input, expected result, observed result and correction; the participant distinguishes a filtered entry from a module error.
From sales form to CRM
Teaching example
Suggested practice: follow a request between two practice tools, map its fields and locate the step where a value is missing. We compare executions and leave instructions for reviewing the scenario; applications and difficulty are agreed beforehand.
Fictional classroom case. A sales team receives enquiries and copies their details into the CRM by hand. We build the workflow using a Tally form and practice HubSpot contacts.
- Starting point
- The same details are entered twice, and a new enquiry may come from someone already in the CRM.
- First attempt
- The first version of the exercise connects the form and contact, but sends the email as received and does not check whether that value is missing.
- What we review
- The trainer asks participants to normalise the email, add a condition before the CRM and use the action that creates or updates by email. They then compare a valid entry, an incomplete entry and a controlled repeat.
- Result
- The valid entry creates or updates the contact by its normalised email. The incomplete entry stops before the CRM: we review the missing value and submit a new practice response.
The workflow we will build
- Tally
New enquiry
A form response starts the scenario.
- Prepare data
Map and normalise
Match the fields and clean the email.
- Condition
Email present
Stop the entry if the required value is missing.
- HubSpot
Create or update
Use the email to create or update the contact.
Follow the data from form to contact: source, preparation, condition and result.
What happens to each input
Complete entry
- Name
- Ana Martín
- Email received
- ANA@EXAMPLE.COM
- Fictional company
- Norte Demo
Expected result: contact created or updated with ana@example.com.
Follow the normalised email and check the contact fields in HubSpot.
Incomplete entry
- Name
- Ana Martín
- Email received
- Empty
- Fictional company
- Norte Demo
Expected result: the entry stops before the CRM.
Locate the condition that is not met. To repeat the test, submit a new response with an email.
Before calling it complete
- The form fields match the agreed contact properties.
- An entry without an email stops at the filter, and we can locate the condition it does not meet.
- When repeating that email with a changed company, we check that the same contact is updated.
A short task between sessions.
Three optional 10–15 minute tasks to recall the work, try a variation and check the result. A brief review stays within the 8 live reference hours.
Four sessions to put it into practice.
Reference edition · 8 h live
Reference edition: 8 live hours across 4 sessions of 2 hours. The order and examples are adapted to the group. Practice takes place during the sessions; any preparation or additional work is agreed before the programme starts.
- Session 12 h
From form to first contact
Define the case, review authorised connections and build the first workflow between Tally and HubSpot.
By the endA practice contact whose details can be traced to the source form.
- Session 22 h
Prepare and filter the data
Map the fields, normalise the email and compare complete and incomplete entries.
By the endA filter that stops the entry without an email and a mapping checked in the CRM.
- Session 32 h
Create, update and check
Test a new and an existing email, read the history and correct an incorrectly mapped field.
By the endA test table recording what was expected, what happened and the correction.
- Session 42 h
Complete a variation and leave instructions
Adapt one field in the case, review the workflow with the trainer and document how to check it.
By the endA reviewed classroom scenario and instructions that another person can follow.
If your team needs to go further
- Adding a team notification or a follow-up task can be covered as an extension, with the applications and time agreed beforehand.
- Two-way synchronisation, custom webhooks, code and production deployment require a separate scope; they are not included in this introductory edition.
Learn with someone who works with Make.
Borja Martínez
Make certified consultant
Over two years of experience developing projects for companies across industries and sizes.
Borja is the planned trainer for this programme. Dates, language and his availability are confirmed when the edition is agreed.
With guidance, practice and support.
Each delivery includes working materials, feedback on practical work and assessment against the agreed objectives.
Materials you can keep
Downloadable, versioned guides, exercises and review criteria for internal use.
To prepare and complete the delivery
A short recommendation, an editable communications kit and a group learning report.
TOF’s own certificate
A certificate of achievement after the agreed assessment. It is not a vendor certification.
A month of email support
On the content covered, up to two accumulated hours for the whole group.
Your team carries out the practice. Implementation services are agreed separately. See the scope →
Make Partner
As a Make Partner, we bring practical experience with scenarios that connect tools, transform data and handle errors.
Our partner profile ↗The partnership belongs to The Optimal Flow. Learn’s certificate is issued by TOF; it is not a vendor certification.