Short answer: Drop the "Clearbit → Enrich Company" 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 |
|---|---|---|---|
Domain domain | string | Required | Domain. Example: stripe.com |
{"domain": "e.g. stripe.com"}
{"id": "abc123","name": "Stripe","domain": "stripe.com","metrics": {"raised": 2200000000,"employees": 8000,"annualRevenue": "$1B+"},"category": {"sector": "Technology","industryGroup": "Software"},"location": "San Francisco, CA","description": "Financial infrastructure platform for the internet."}
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.