Skill UI

This guide details the complete setup process for integrating with the Clay data enrichment platform. It covers obtaining the Enterprise API key, configuring webhook endpoints for data ingestion, and connecting third-party data providers (like Apollo or Clearbit). Use this when onboarding, setting up automated data pipelines, or maximizing credit savings through programmatic integration.

This skill provides comprehensive strategies for managing API rate limits and webhooks within the Clay platform. It addresses webhook throttling, plan-level rate limits (hourly/per-second), and webhook submission exhaustion (50K limit). Use this when integrating with Clay to ensure reliable, optimized data throughput and handle 429 errors gracefully with backoff strategies.

This guide provides production-ready patterns for building robust integrations with the Clay platform. It covers interacting with Clay via webhooks (inbound data), HTTP API enrichment columns (outbound data), and the Enterprise API. Implementation examples are provided in TypeScript and Python, ensuring reliable, reusable, and scalable data pipeline construction.

This guide details security best practices for integrating with Clay. It covers securing API keys, validating webhook signatures, isolating provider credentials, and redacting sensitive PII data. Essential for maintaining compliance and data integrity in production environments.

A comprehensive guide and implementation framework for managing real-time data flow using Clay's event-driven architecture. This skill covers both inbound webhooks (POSTing data into Clay tables) and outbound HTTP API callbacks (receiving enriched data from Clay). It provides production-ready TypeScript code for setup, signature verification, and idempotent processing, enabling robust, event-driven integrations.

A comprehensive guide demonstrating how to implement robust authentication using Clerk across various modern web environments, including Next.js Server Components, Client Components, API routes, and Server Actions. Learn best practices for securing endpoints, managing session data, and handling authenticated requests from end-to-end.

This comprehensive guide outlines essential, production-grade security best practices for implementing Clerk authentication. It covers securing environment variables, hardening middleware with crucial security headers (like CSP, X-Frame-Options), protecting API routes with granular authorization checks, and verifying webhooks using signature validation (svix). Use this when deploying or auditing an application to ensure maximum security posture.

A comprehensive guide for designing production-grade lead enrichment pipelines in Clay. Covers three integration patterns (Webhook, API), detailed table schema design, advanced data waterfall logic, implementing complex ICP scoring formulas, and setting up robust CRM synchronization flows for go-to-market data operations.

Specializing in building high-performance, cloud-native applications using C# and the latest .NET 8+ framework. This skill covers end-to-end development, including building robust RESTful APIs (Minimal/Controller), implementing data access with Entity Framework Core, structuring code using CQRS/MediatR, and scaffolding Blazor components. Focuses on modern best practices like async/await, DTO mapping, and proper error handling.

This comprehensive guide details essential security best practices for integrating with Customer.io. It covers secure credential storage using secrets managers, sanitizing Personally Identifiable Information (PII) via hashing, verifying webhook signatures (HMAC-SHA256) to ensure data integrity, and establishing procedures for API key rotation to maintain compliance with GDPR/CCPA regulations.

A comprehensive guide for diagnosing and fixing common Deepgram API errors. Covers HTTP error codes, WebSocket issues, optimal audio preparation using ffmpeg, and implementing robust retry patterns for reliable Speech-to-Text integration.

Controls headful browsers via a CLI that runs sandboxed JavaScript, keeping page state persistent while navigating, form-filling, screenshots, scraping, or web testing flows.