Use Clay tables as a database

Clay tables can be more than a workspace view. For developer workflows, they can act as a GTM database that your services, dashboards, and apps query directly. Use table queries when you already know which Clay table contains the data you need and you want to search, filter, select fields, order records, or page through results.

​

What you can build

• Dashboards for pipeline health, enrichment coverage, routing QA, and account scoring.
• Internal tools that inspect, filter, or review Clay-enriched records.
• Interactive apps that let users search and browse GTM data stored in Clay tables.
• Sync jobs that push selected Clay fields into a CRM, warehouse, or product database.
• Monitoring jobs that alert when records match a specific GTM condition.

​

Why build on tables

Clay tables often become the place where GTM data is cleaned, enriched, scored, and reviewed. Querying those tables lets you reuse that work instead of rebuilding a separate database or duplicating Clay logic in another system.

​

How it works

The Tables endpoint accepts a structured query against a known table. You choose fields, filters, ordering, and pagination settings, then Clay returns records with field metadata. The current public API does not include a list-tables endpoint. Your integration needs to know which table it should query.