Integrations
Clay
Push prospect signals from Clay into the Brain — OAuth connect, fail-closed on writes.
Clay is a context integration: Clay can push prospect signals into the Brain. Connection is OAuth-only. Clay remains the system of record for its tables and workflows — HiveBase does not replace Clay as a GTM product.
Connect ≠ watch ≠ Brain ≠ writeback. Ingesting a signal does not imply outbound messages or CRM mutations from HiveBase unless you run a separate governed action.
How it works
| Direction | Path | What you get |
|---|---|---|
| Clay → HiveBase | HTTP push webhook after OAuth | Prospect signals as Brain context |
Connect Clay
Open Integrations
In HiveBase, go to Settings → Integrations and find Clay.
Complete OAuth
Connect Clay via OAuth only — there is no shared-password path.
Copy the webhook URL
Paste the generated webhook URL into Clay as an HTTP push destination for the tables or workflows that should feed the Brain.
Clay → HiveBase
Once connected, prospect signals sent to the webhook are ingested into the Brain so agents and operators see current account context without manual copy-paste. Treat this as signal capture — typed claims still carry provenance and can be corrected when sources disagree.
Field sync
Field-level sync contracts (which fields move between HiveBase and Clay, and in which direction) are configured per entity and field in the integration settings panel. Toggle contracts deliberately — do not assume every Clay column is mirrored into the Brain.
What we do not claim
- No silent two-way real-time sync of every Clay table and every Brain claim.
- No replacement of Clay as your GTM / enrichment product of record.
- No outbound email or CRM write just because Clay is connected.
Disconnecting
From Settings → Integrations, disconnect Clay to revoke OAuth and stop webhook acceptance for that connection. Existing Brain claims keep history subject to workspace retention; remove Clay-side HTTP destinations if you want pushes to fail closed there too.