Limerine and Clay
The layer supplies Clay workflows with your own account history and signals, and writes their results back to your CRM under rules you set.
What stays in Clay
Clay stays your enrichment and workflow tool. Its data providers and tables keep doing what they do well. We supply the proprietary inputs and the governance around the outputs.
Data flow
Data flow diagram, objects, and sync cadence not published yet
This appears here once Developer Relations approves the record. We do not publish a placeholder in its place.
Setup time and prerequisites
Setup time not published yet
This appears here once Developer Relations approves the record. We do not publish a placeholder in its place.
Permissions
We connect to Clay through a scoped service account on credentials you own. Read access covers a diagnostic. Write access is granted per module during a build, with your approval, and you can revoke either at any moment.
How the two fit together
- Running Clay today
What Clay already does well, and where the layer adds to it.
Start with a fixed-price diagnostic
Five questions, then a booking. You leave the diagnostic with a ranked plan you can run with us or without us.