Short answer: Drop the "Clearbit → Enrich Person" action anywhere in your workflow, map the inputs from upstream nodes, and publish.
Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.
| Field | Type | Required | Description |
|---|---|---|---|
Email email | string | Required | Email. Example: john@stripe.com |
{"email": "e.g. john@stripe.com"}
{"id": "abc123","email": "john@stripe.com","title": "Co-founder & President","twitter": {"handle": "collision"},"fullName": "John Collison","linkedin": {"handle": "in/johncollison"},"location": "San Francisco, CA","employment": {"name": "Stripe","role": "leadership","title": "Co-founder & President","seniority": "executive"}}
Use these fields in downstream nodes for routing, logging, or error handling.
Any of these apps can fire this action as part of a workflow.
Triggered by anything in the catalog. Free tier available. No credit card.