Clay

Use Clay's HTTP API enrichment to add Homie introduction paths to your table. Each row searches your organization's mapped network for a person or company.

You need Homie API access (Platform, Custom, or an active trial) and access to HTTP API enrichment in Clay.

Set up your account

1. In Homie, open Settings → Integrations. An organization admin can select Homie API → Manage keys → Generate key. Name the key Clay and copy it from the one-time reveal.
2. In your Clay table, select Add enrichment → HTTP API.
3. Under Select header account, choose + Add account. Save a header named Authorization with the value Bearer YOUR_HOMIE_API_KEY, replacing the placeholder with your key. Name the account Homie.
4. Select that saved account for the enrichment. Keep credentials in the account rather than table columns or endpoint URLs.

See Clay's HTTP API guide for the current setup controls.

Find introductions to a person

In the enrichment's Configure tab, choose GET and use this endpoint:

https://app.usehomie.com/api/v1/search/warm-paths

Add these query parameters. For the LinkedIn URL value, select your table's profile URL column using Clay's column picker.

Configure Only run if so the profile URL column is not empty. Set the request limit to 1 per 1000 ms and test one row before running the table.

Equivalent API request:

curl --get 'https://app.usehomie.com/api/v1/search/warm-paths' \-H "Authorization: Bearer $HOMIE_API_KEY" \--data-urlencode 'prospectLinkedinUrl=https://www.linkedin.com/in/jamie-rivera/' \--data-urlencode 'limit=5'

Find introductions to a company

Use the same endpoint, saved account, request limit, and GET method. Replace the person parameter with the company domain column:

Configure Only run if so the company domain column is not empty. Omit prospectRoles to search all mapped employees; when supplied, any matching title term qualifies.

Domains match a company's website host exactly after removing the scheme, leading www, and path. Other subdomains remain distinct. A domain shared by multiple company records returns an ambiguity error. Use a specific company name through prospectCompany or a person's profile URL to narrow the target.

Send one target parameter per enrichment. Do not send a LinkedIn URL and a company domain together.

Add results to columns

Keep the response's data object, then use Clay's result picker to add fields to columns. Array paths below show the first result; expand data.paths to keep all returned paths.

For multi-person paths, use the ordered hops and viaAdvocate when present to identify who asks whom. The connector alone may not be the teammate's first contact. Warmness is Homie's stored score, not a probability of getting an introduction.

found means Homie found a warm path. no_paths means the target is mapped but no warm path was found. target_not_found means the target could not be resolved. incomplete or coverage.capped=true means search bounds may have omitted paths. Check the outcome before treating a returned route as warm.

fallbackConnections, when present, are alternative contacts in your network. They are not paths to the requested target. Keep them separate from introduction columns.

If hasMore is true, another request with the same target and offset=data.nextOffset retrieves the next page. Five paths is the example limit, not the total number of possible introductions.

Troubleshooting

Empty results are valid responses. These lookups use existing mapped network data; running a row does not start LinkedIn discovery or send an introduction request.

To disconnect, revoke the dedicated Clay key in Homie's Manage keys dialog. See the warm-path API reference for the full response and additional filters.