Skip to main content
Recipe prompt
Use a work email to suggest company details during signup or fill gaps in a CRM record. Treat the result as a suggestion: let people confirm or replace it. Brand describes the company; People describes a person.

Look up the company

Use a server-side key from the Quickstart. Send the work email to Brand.

Fill blanks and preserve edits

Map brand.title, brand.domain, brand.description, and a suitable logo into your application. Keep the raw response and retrieval time separately from confirmed fields. For a form, apply a response only if it belongs to the current email and tenant. Fill blank fields without overwriting edits made while the request was running. Let signup continue after an empty or failed lookup. For a CRM worker, key jobs by tenant, normalized email, and lookup version. Use a durable queue, save successful fields, and skip duplicate events. Maintain separate matched, unmatched, partial, and retryable_error states; an API error must not become an empty successful profile.

Keep workspace branding editable

Store automatic suggestions separately from saved choices. An explicit logo removal must survive a later enrichment:
workspace-theme.ts
Use the accent for decoration until you have checked contrast for text and controls. Save choices against the tenant ID and reapply them after refreshing the Brand snapshot. Branded content shows theme validation and rendering.

Add person data and research when needed

Send identity clues to People when the workflow needs a person’s profile:
People enrichment request body
A match score is evidence to review, not proof of employment or identity. Keep the person and company records separate. For account research, use Answers and retain the source URLs with each claim; missing evidence should remain unknown. If you know the company identifier ahead of time, prefetch can prepare a later lookup. The later Brand response determines whether the profile is ready.