Documentation & Resources
Get Started
Learn how to connect Directus with Clay using HTTP API templates and webhooks.
HTTP API Templates
Learn how to use Clay's pre-built HTTP API templates to connect with Directus. Configure authentication, select templates for common operations (create, update, get items), map your data fields, and test your enrichment workflows.
Directus Webhooks
Learn how to set up Directus Flows to automatically send data to Clay webhooks. Configure event hook triggers to send data when items are created, updated, or deleted, enabling real-time data synchronization between platforms.
Advanced Data Operations
Advanced guide for working with Directus data in Clay. Learn how to use filter operators, select specific fields, implement pagination, and optimize data operations. Includes common use cases like product enrichment, content workflows, and lead management.
Overview
The Directus Clay integration provides two configuration methods for connecting your platforms:
Clay HTTP API Templates allow you to interact with your Directus data directly from Clay enrichment columns. After setting up authentication with your Directus API token, you can use pre-built templates for common operations like creating items, updating records, retrieving data, and fetching relational information. These templates require manual configuration including your Directus URL, collection names, field mappings, and query parameters. This method is ideal for on-demand data operations and enrichment workflows where you're actively working in Clay.
Directus Webhooks via Flows enable automatic real-time data synchronization from Directus to Clay. You configure Directus Flows with event hook triggers that activate when items are created, updated, or deleted in your collections. These flows send data automatically to Clay webhook URLs, enabling real-time sync without manual intervention. This method is perfect for automated workflows like sending new content for enrichment, triggering processes when content is published, or syncing form submissions.
Both methods require setup in their respective platforms and support advanced features like filtering, field selection, pagination, and custom data mapping. The integration is ideal for use cases including e-commerce product enrichment, content publication workflows, lead enrichment systems, and form submission processing.