Avoiding duplicate records in automated workflows
Why automations create duplicates, and the search-before-create, idempotency and unique key patterns that prevent them.
Guide by the Otomatzia editorial team · checked against official sources on
Why duplicates happen
Triggers can fire more than once, users resubmit forms, and retries repeat steps that already succeeded. Each of these creates a second record unless the workflow checks first.
Patterns
- Search before create, by a normalized key such as lowercase email
- Carry a stable ID from the source and store it on the record
- Prefer upsert operations where the destination offers them
- Use a destination with real unique constraints when it matters
Limits
Search then create is not atomic. Spreadsheets have no unique constraint. Keep the destination system duplicate tools as a backstop and review them periodically.
Sources to check next
- HubSpot Knowledge Base: deduplication of records
- Google Sheets API overview
- Airtable Web API documentation
Vendor features and prices change. Confirm details on the linked official pages before you rely on them.
What to read next
- Recipe: form submissions to CRM without duplicate contacts
- Google Sheets as an automation data store: uses and limits
- HubSpot: CRM records, workflows and deduplication basics