Clay Icon

Setting Up an Automated Table for SDK and API Documentation Checks

Ā·
Ā·

I'm having trouble setting up tables. What would be the best approach to find the following? I want to set up a table where I can check for SDK presence, and I believe I can do this with the BuiltWith integration. How do I input a query to set this up correctly "Find SDKs used by [Company Website]? I would also like to Identify Public API Documentation, where I believe I can use Clay's Google Search Integration with the query "[Company Name] API documentation and also would like to use LinkedIn Search Integration "Search job postings [company name] for "SDK", "API Engineer", "Developer Relations" Could you give me step by step instructions on how to set up this table to automate as much as possible? Thank you.

  • Avatar of Channeled
    Channeled
    APP
    Ā·
    Ā·

    Here's how to set up your table for the requested automations: 1. For SDK Detection with BuiltWith: ā€¢ Add a new table and select BuiltWith integration ā€¢ This will help you quickly uncover the tech stack of websites or companies 2. For API Documentation Search: ā€¢ Add Google Search integration to your table ā€¢ Use the "Perform Search with Google" action ā€¢ Input your search parameters for "[Company Name] API documentation" 3. For LinkedIn Job Postings: ā€¢ Add the "Find Open Jobs with Google" integration ā€¢ Input the following: ā€¢ Company name ā€¢ Company domain (for better results) ā€¢ Keywords: "SDK", "API Engineer", "Developer Relations" ā€¢ The search will return job listings with details including job titles, descriptions, and types,You can connect these searches in sequence within your table to automate the entire research process. Sources: Integrations | Clay.com Google x Clay integration | Clay.com Find Open Jobs with Google | Clay.com Find Open Jobs with Google

  • Avatar of Channeled
    Channeled
    APP
    Ā·
    Ā·

    Was that helpful?

  • Avatar of Channeled
    Channeled
    APP
    Ā·
    Ā·

    Hi Craig K.! This thread was recently closed by our Support team. If you have a moment, please share your feedback: