Clean and format raw form data for database syncs
Creates exact formatting, casing, and normalization rules to prevent corrupted contact records and messy syncs.
Prompt
Act as a revenue operations data architect. Review the pasted form submission fields and provide complete data cleaning and transformation rules to prepare the data for database ingestion.
Rules:
- Define strict normalization rules for casing, phone numbers, website URLs, and empty fields.
- Provide fallback values for missing optional fields so sync operations never fail on null values.
- Detail validation checks that flag invalid emails or junk entries before writing to the database.
Output format:
Provide a markdown table with these exact columns: Field Name, Input Example, Transformation Rule, Cleaned Output Example, and Fallback Value.
Conclude with a short bullet list of three critical rejection criteria for junk submissions.
Here are the form fields and raw sample data:Example output
Paste your list of form fields and sample raw inputs directly below the prompt in ChatGPT, Claude, or Gemini. If you use a specific tool like Zapier or Make, ask the model to provide the exact formatting formulas next.
Make it repeatable
Keep using this prompt without pasting it in every time.
Prompt details
- By
- Prompts-GPT editors
- Published
Did this prompt work?
Keep exploring
More like this
Define minimal required CRM fields by sales stage
Streamline CRM data entry to ensure data integrity without slowing down sales teams. Establishes the exact required fields needed at every deal milestone.
Audit CRM fields to remove manual entry bottlenecks
Review your CRM field list to identify redundant, unpopulated, and high-friction inputs so your sales team spends less time on data entry.
Architect an automated lead routing and enrichment workflow
Design a complete end-to-end specification for inbound lead qualification, third-party data enrichment, and team routing. Use it to eliminate manual lead handling.
Map record fields to prevent duplicates across systems
Design an upsert mapping table with match keys and fallback logic to stop sync duplicates between your tools.
Build automated stale deal cleanup and archive rules
Establish clear pipeline stages, inactivity triggers, automated warning alerts, and archiving criteria to keep sales forecasts accurate.
Build a pre-send data check for recurring reports
Create an automated pre-flight checklist to stop recurring reports from sending broken data. Use this to catch expired tokens, schema shifts, and null records.