enrich-records-after-a-sync

Use it when

• New or changed records lack fields that public data can fill: company details, a work email, a phone number, or a check that an email or phone is valid.
• Records arrive at more than about 100 per hour, or in imports of 1,000 or more; below that, a per-record run (react-to-each-record-change) is enough.
• A delay of a few minutes before the fields appear is acceptable.

Why this design

Advantages:

• Built-in steps need no connection or account: enrich a company or person, find an email or a phone, validate an email, validate a phone.
• The queue batches changes, so a 2,000-record import starts 2 runs at a batch size of 1,000.
• The write back goes through the app's own step, so the sync carries it to the other side.