Fix Ugly Forms: Auto-Clean Job Notes with AI
Transform messy form submissions into polished job notes using ChatGPT and Zapier. Streamline your documentation process and save time.
What This Automation Does (And Why It Matters)
The Problem:
Most forms submitted in ServiceTitan are stored as PDFsβhard to read, not searchable, and often ignored.
The Solution:
We'll use Zapier + ChatGPT to:
- Trigger automation from a submitted ServiceTitan form
- Clean up spelling and formatting
- Convert the form data into a structured job note
- Upload it directly into the job for quick reference
Why it matters:
Clear notes save time, prevent miscommunication, and eliminate the need to dig through PDFs.
π οΈ Tools You'll Need: ServiceTitan, Zapier, OpenAI
Let's get our toolbox ready. Here's what you need to build this automation:
- A Zapier account
- Access to ServiceTitan's API through Zapier
- An OpenAI account (we'll use GPT-4o Mini for speed and accuracy)
We'll show you how to connect each piece and offer recommendations on the best setup for reliability and performance.
Understanding ServiceTitan Form Limitations
Important Limitation You Need to Know:
ServiceTitan does not send blank form fields through Zapier. That means:
- β’If a field was left unanswered, it won't appear in your Zap data
- β’Conditional fields that didn't trigger won't be visible
What You Should Do:
When preparing your test form, make sure every field is answered, including all conditionals. This step is crucial so your AI formatting step has all the info it needs.
Choosing the Right Form for This
Not all forms are created equal. For this automation to be useful, the form should:
- Contain structured information (not long open-ended essays)
- Be consistently used in your workflow
- Include relevant tech or job data (e.g., install details, checklists, or summaries)
Best Use Cases:
- β’ Install checklists
- β’ Post-job summaries
- β’ Service evaluations
Forms used by technicians in the field tend to be the best candidates.
How to Submit a Fully Completed Test Form
Why a Complete Sample Matters
Zapier only pulls in data from fields that were filled out. That's why you need a complete form to use during setup.
Steps to Follow:
- Choose a job in ServiceTitan
- Open the form you want to use
- Fill in every field β even conditional ones
- Submit the form
- Save the Job ID to use in Zapier testing
This will ensure all data fields are available when building your automation.
Why You Must Fill In Every Field (Including Conditionals)
No Placeholders? No Problem β If You Plan Ahead
ServiceTitan only sends what's visible and filled. That means:
- β’ Blank fields are dropped
- β’ Hidden conditional fields are ignored
The Fix:
Make sure you answer every single field when submitting your test form β yes, even the ones that normally stay hidden unless triggered.
This ensures your Zap sees the full structure of your form data and allows you to design a complete, reliable automation.
β‘ Setting the Trigger: New Form Submission in ServiceTitan
Time to Build the Zap!
Start by setting the trigger that kicks everything off: a new form submission in ServiceTitan.
Steps:
- In Zapier, choose ServiceTitan as the app
- Select New Form Submission as the trigger event
- Connect your ServiceTitan account
- Choose the form you want to automate
- Use the test form you submitted earlier to pull in sample data
This is the foundation of your automation. Without the sample data, the rest of the steps won't work.
Pulling in Form Data (and Why You Need a Complete Sample)
Verify Your Sample Data
Once your test form is pulled in, take a close look at the data fields Zapier shows.
Key Tip:
If a question or answer is missing, it likely means it wasn't filled out or visible in your original test.
Double Check:
- Do all expected units (questions/answers) show up?
- Are the field labels and responses what you expect?
If not, go back and submit a more complete form. You can't build a reliable automation on partial data.
Structuring the Data for AI (Units Name + Value Format)
Make the Data Easy for AI to Read
To get the best results from ChatGPT, you need to organize the form data into a consistent, readable format.
Recommended Layout:
Unit 0 Name Unit 0 Value Unit 1 Name Unit 1 Value Unit 2 Name Unit 2 Value ...
How to Build This:
Use a Formatter > Text step in Zapier or write your own structure in a Code or Text step. Keep line breaks clean and avoid adding extra punctuation.
This structure is what you'll feed into ChatGPT in the next step.
Setting Up the ChatGPT Step in Zapier
Now We Add the AI!
In this step, you'll send your structured form data to ChatGPT using Zapier.
Steps:
- Add a new OpenAI (ChatGPT) action step
- Choose the Conversation or Send Prompt action
- Use the structured form text you created in the last lesson as the input
- Choose a reliable model β we recommend GPT-4o (Mini)
You're now telling the AI: "Here's the data. Make it clean, clear, and readable."
Writing the Prompt to Format Notes, Fix Grammar, and Add Highlights
This Is Where the Magic Happens
The prompt you write here is what tells ChatGPT how to handle your form data.
Recommended Prompt Starter:
Take the following form responses and:
- - Fix any spelling or grammar mistakes
- - Format into bullet points
- - Bold any dollar amounts
- - Highlight technician action items as β Action Item (in green if possible)
Test and tweak until you get output that looks the way you want. This is the "secret sauce" that turns your automation into a true upgrade.
Creating the Job or Project Note
Where the Magic Lands
Now that your form data has been cleaned and formatted by ChatGPT, it's time to send it back into ServiceTitan.
Steps:
- Add a new ServiceTitan action in Zapier
- Choose Create Job Note or Create Project Note (depending on your workflow)
- Map the formatted output from ChatGPT into the note body
- Use the Job ID from the original trigger to ensure it's linked to the right job
You'll now have a clear, readable note directly inside the job, automatically.
Mapping the Formatted Output Back into ServiceTitan
Keep It Clean and Clear
This step ensures that your beautifully formatted note makes it into ServiceTitan the way you intended.
Tips:
- Preserve line breaks and bullet points
- Wrap currency values in
<b>$amount</b>if you want bold formatting - Make sure the job ID or project ID is correctly mapped
- If using a rich text field, test formatting behavior (bold, bullets, checkmarks)
Preview your note in a test job before going live to make sure everything looks perfect.
Testing the Workflow from End to End
Time to See It in Action
Before turning this automation on, run a complete test to verify every piece is working.
Test Steps:
- Submit a real form in ServiceTitan
- Watch it trigger your Zap
- Review the AI's formatted output
- Confirm the note is added to the correct job or project
Final Check:
- β Does the note look clean?
- β Is everything spelled correctly?
- β Are action items clearly marked?
Once it all looks good β you're ready to go live.
Making Notes Easy to Scan and Search
Write Notes Your Team Will Actually Read
The whole goal of this automation is to make job notes faster to read and easier to understand. Use formatting intentionally.
Formatting Tips:
- Bullet points make scanning faster
- Bold important keywords or amounts
- Use β or other visual markers for action items
- Keep paragraphs short and clean
Bonus:
Clean formatting makes it easier to search in ServiceTitan when reviewing job history.
Troubleshooting Common Issues
Running Into Problems? Here's What to Check
If your automation isn't working as expected, don't panic. Start by checking these areas:
Checklist:
- β’Is your test form fully filled out?
- β’Are the form fields showing up in Zapier?
- β’Does your AI output look as expected?
- β’Is the note posting to the right job or project?
- β’Are line breaks or special formatting being lost?
99% of issues come down to sample data, prompt structure, or field mapping.
Pro Tips for Expanding This Automation to Other Forms
Scale Your Automation Across the Business
Once you've built one of these automations, it's easy to duplicate and adjust it for other forms in your workflow.
Ideas for Expansion:
- Create versions for service checklists, install reports, or feedback forms
- Adjust the AI prompt to match the tone of each form type
- Use job tags or form names to trigger different formatting logic
You've built the engine β now apply it anywhere consistent, clean notes are needed.
