Mille B.

Use Bitscale - they offer Hubspot in $349 plan

Clay doesn’t support true rich-text columns yet (like bolding, inline links, or formatting inside a cell). Most columns are treated as plain text or structured data. A common workaround is to use Markdown-style text (links, line breaks, bullets) or store formatted content externally (Notion/Docs) and link to it from Clay.

This usually happens when the API response is returning a large array or long text, which hits Clay’s per-cell data limit. The easiest workaround I’ve used is to limit or chunk the response before sending it to another table for example:

Once the payload is smaller, sending it to another table should work without errors.

From how Clay + HubSpot typically behaves, it won’t blindly create duplicates. If the company gets created on the first run and you rerun the table, Clay will usually match against the existing company (domain / unique identifier) and skip creating it again, assuming the same identifiers are used. Duplicates usually only happen if the identifiers change between runs (e.g., different domains, missing domain on one run, or multiple “create company” steps without a match condition).

As per my past experiences, In most cases, being locked out of a client workspace is tied to permissions, seat changes, or billing status. I’d suggest checking with the workspace owner to re-invite you or verify your access, and also reaching out to Clay support so they can unblock it quickly on their end.

Hi Mike, From what I’ve seen, Clay’s Ocean.io integration is primarily geared toward company-level lookalikes. You typically seed it with a company (or a list of companies), and Ocean returns similar companies based on firmographic and technographic signals. For contact-level lookalikes, Clay usually relies more on workflows like finding people within those similar companies, rather than Ocean directly generating contact lookalikes.