You will be able to clean and reformat data inside a workflow so each app receives what it expects.
Add a small formatting step inside your flow wherever data passes from one app to the next, so that dates, times, phone numbers and text arrive in the shape the next app expects. Data changes shape as it moves between apps, and the receiving app rarely complains, because it accepts whatever it gets.
Say a parent books a trial class for 7 March (an example date), and the confirmation email says 3 July. The parent turns up four months late or, more likely, doesn't turn up at all. Nobody typed anything wrong. The form recorded the date one way, the email template read it another way, and the flow passed it along without checking. Every fix below is a small step you add inside the flow to stop this kind of change.
Singapore writes dates day first, so 07/03 means 7 March. Many apps and tools read dates month first, especially those built in the United States, so the same 07/03 becomes 3 July. If the day is 13 or higher, a month-first reading is impossible, and the tool either shows an error or guesses. For most dates in the first twelve days of a month, the tool silently picks the wrong reading. So a flow can look fine when you test it on the 20th and then go wrong on the 5th.
Never pass a date around as loose text. Every automation tool has a date formatting option. Some have a dedicated formatter step, and others have a function you use inside a field. Use it at each hand-off to state the format explicitly.
Two habits cover most cases. For anything a machine reads, such as a sheet column used for sorting or a calendar entry, use year-month-day format, for example 2025-03-07, which no app misreads. For anything a person reads, such as a confirmation email, spell the month out, because a written-out month can't be swapped: 7 March 2025, or Friday 7 March (both example dates).
Many automation tools run on servers elsewhere and default to a time zone other than Singapore's. Leaving the default causes two problems. First, scheduled triggers fire at the wrong local time, so an 8am daily summary arrives in the middle of the night or in the afternoon. Second, timestamps written to the sheet are off by hours, so a 10pm enquiry looks as if it came in the next morning.
Find the time zone in the account or flow settings and set it to Singapore time, which is usually listed as Asia/Singapore. Then check the apps at each end of the flow, because a spreadsheet has its own time zone setting, and so does a calendar. After changing anything, submit a test entry and compare the time in the sheet with a wall clock.
Parents type phone numbers in many formats: 9123 4567, 91234567, +65 9123 4567, 6591234567, and sometimes with a dash in the middle. A person reading the sheet understands all of them. A messaging app or SMS step often does not, and it may reject the number or send to the wrong one.
Pick one standard and convert every number to it inside the flow. A sensible phone number standard for Singapore mobiles is the country code +65 followed by the eight-digit number, with no spaces, for example +6591234567 (a made-up number). The conversion runs in this order:
Strip out spaces, dashes and brackets. If the result is eight digits, add +65 in front. If it starts with 65 and is ten digits long, add the plus sign. Send anything that still doesn't fit, such as an overseas number or a typo, to a person, and don't force it into shape.
Most tools can do this with a text formatter step or a simple formula, the same kind you would write in a spreadsheet. You can also reduce the problem before it reaches the flow. If your form tool supports a phone field with validation, turn it on so fewer bad numbers arrive.
Text needs less work than dates and phone numbers, but it still needs some. Trim spaces from the start and end of every text field. To a person, "Tan " with a trailing space and "Tan" without one look identical, but a duplicate check treats them as two different entries.
Fix the capitalisation of names that appear in emails, because some people type in all capitals or all lower case. Most tools have a "capitalise words" option. Check how it handles multi-part names such as Nur Aisyah binti Rahman and hyphenated surnames, and leave the name as it was typed if the result looks wrong.
Blank fields need a decision, so don't just pass them through. A blank name produces a broken greeting such as "Dear ,", so set a clear default such as "Dear parent". A blank child's level leaves the branch from lesson 2.1, Triggers, actions and the steps between them, with nothing to route on, so send that record down a path for a person to check. A blank caught at the first step is easy to deal with, while one passed silently through five steps is much harder to find.
None of these fixes work unless you know what format the receiving app wants, and each destination has its own expectations. A sheet column needs a date it can sort. An email needs words a parent can read. A calendar needs a start time with a time zone. A messaging step needs a full international number.
For the activity, take the mapping table you drew in lesson 2.2, Data mapping: passing fields from one step to the next, and go through every field in your own workflow. For each field, mark where the data changes shape between apps, note any date, time zone, phone number, text or blank-field fix it needs, and write the exact format the destination app expects next to it.
List every field in your workflow that needs reformatting and write the exact format each destination app expects.
Junxiong-WFG Organisation is an authorised representative of AIA Financial Advisers Private Limited (Reg. No. 201715016G).