EnrichmentCan make changes
Ingest Clay Workflow Result
Ingest asynchronous Clay workflow results into StackOS enrichment records.
Clay enrichment and workflow provider contract.
Connection facts
What the Clay connector actually exposes.
These details come from the current StackOS provider manifest and action catalog. They describe the available connection—not a promise that every workflow will use every action.
- Connection method
- webhook
- Setup
- Create a Clay table webhook, then store its URL and optional authentication token in a dedicated StackOS connection profile.
- Capability groups
- Enrichment
- Action boundaries
- 1 write action1 cost-bearing action
Action catalog
Actions listed for Clay.
Actions listed for this integration. Individual descriptions note availability limits. A workflow still decides which actions belong in the job and where approval is required.
2 matching actions
EnrichmentUses a paid service
Submit Clay Table Webhook
Submit explicit rows to a Clay table webhook contract for asynchronous enrichment.
Direct answer
How does the Clay integration work?
People continue using Clay as their tool. StackOS adds it to a visible workflow, keeps the work in order, and passes only the approved action to the integration when that stage is ready.
- 01Your requestStart in your AI
- 02StackOS planExpands the steps
- 03ClayDoes its bounded part
- 04Checked resultKeeps the proof
More from GTM And RevOps
Related integrations.
GTM And RevOps
Apollo
Apollo provider contract for people search and endpoint-specific enrichment.
EnrichmentLead Management
GTM And RevOps
Clearbit By HubSpot
Clearbit by HubSpot enrichment provider contract.
Enrichment
GTM And RevOps
Custom GTM Tool
Placeholder for project-local GTM or RevOps tooling. Install a project plugin with concrete HTTP connector config before execution.
EnrichmentLead Management+2
Common questions
Clay and StackOS.
What can the Clay integration do in StackOS?
The current catalog includes 2 Clay actions across Enrichment. The exact actions used depend on the workflow and approval rules.
Does StackOS replace Clay?
No. Clay remains the tool that performs its part of the job. StackOS organizes the workflow, keeps status and dependencies visible, and calls the tool only when the plan reaches the right approved action.