ACTION_ID: company_tech_stack_floqer NAME: Floqer: Company Technographics CATEGORY: scrape CREDITS: 1 Enrich company data with technographics, categorized by department (sales, marketing, HR, DevOps, etc.). Naming caveat — despite the `_floqer` suffix and "Floqer:" name prefix, this action is NOT Floqer's own crawler. It's a wrapper over a third-party technographic provider that ships pre-bucketed- by-department output. The trade-off vs the other two tech-stack actions in the catalog: lower raw coverage than BuiltWith (broader, inferred from crawl signal) and than TheirStack (solid + job-posting-derived), but you get departmental bucketing for free without writing the categorization yourself. INDEX: 1. Inputs 2. Outputs 3. How to configure 4. Key notes 5. Where it fits in a workflow 6. When to use 7. When not to use ================================================================================ 1. INPUTS ================================================================================ company_name (type: string, optional) — Company Name Name of the company to enrich. company_domain (type: url, optional) — Company Domain Company domain or website (e.g. "acme.com"). company_linkedin_url (type: url, optional) — Company LinkedIn URL Company LinkedIn page URL (e.g. "https://www.linkedin.com/company/acme"). ================================================================================ 2. OUTPUTS ================================================================================ full_tech_stack (type: raw_array) — Full Tech Stack Full flat list of technologies detected at the company. testing_qa (type: raw_array) — Testing & QA Testing and QA technologies. sales (type: raw_array) — Sales Sales technologies. programming_languages_frameworks (type: raw_array) — Programming Languages & Frameworks Programming languages and frameworks. productivity_operations (type: raw_array) — Productivity & Operations Productivity and operations technologies. product_design (type: raw_array) — Product & Design Product and design technologies. platform_storage (type: raw_array) — Platform & Storage Platform and storage technologies. operations_software (type: raw_array) — Operations Software Operations software technologies. operations_management (type: raw_array) — Operations Management Operations management technologies. marketing (type: raw_array) — Marketing Marketing technologies. it_security (type: raw_array) — IT Security IT security technologies. it_management (type: raw_array) — IT Management IT management technologies. hr (type: raw_array) — HR HR technologies. health_tech (type: raw_array) — Health Tech Health-tech technologies. finance_accounting (type: raw_array) — Finance & Accounting Finance and accounting technologies. ecommerce (type: raw_array) — Ecommerce Ecommerce technologies. customer_management (type: raw_array) — Customer Management Customer-management technologies. computer_networks (type: raw_array) — Computer Networks Computer-networks technologies. collaboration (type: raw_array) — Collaboration Collaboration technologies. bi_analytics (type: raw_array) — BI & Analytics Business intelligence and analytics technologies. ================================================================================ 3. HOW TO CONFIGURE ================================================================================ Configure Action body: { "inputs": { "company_domain": "{{input.company_domain}}", "company_linkedin_url": "{{input.company_linkedin_url}}" } } Pass at least one of `company_name`, `company_domain`, or `company_linkedin_url`. All three are optional individually but the action needs at least one to identify the company. Identifier preference: prefer `company_domain` or `company_linkedin_url` when available. `company_name` works but is more likely to resolve to the wrong record for common / generic / similarly-named companies (e.g. "Acme" could match many distinct companies). Domain and LinkedIn URL are unique identifiers and produce deterministic matches; fall back to `company_name` only when neither is available. ================================================================================ 4. KEY NOTES ================================================================================ - Each department field is a `raw_array` of technologies. Filter with `format_data_using_js_expression` (e.g. `sales.includes(...)`) or pass the relevant array into `llm_models` for per-row insights. - `full_tech_stack` is the flat list. Department-specific arrays (sales / marketing / hr / etc.) are subsets of the same set. - Department buckets can be empty (e.g. `health_tech` is often empty for non-healthcare companies). Reference them defensively in downstream JS (`(arr || []).includes(...)`) — Floqer surfaces empty fields as `""` not `[]`, so an `Array.isArray` guard helps. - Coverage is lower than BuiltWith and TheirStack. A smoke test on stripe.com returned 356 technologies (vs ~840 from BuiltWith, 577 from TheirStack). For newer / smaller / privately-marketed companies the action can return `"No data found for company"` outright — a real failure mode this provider has more often than the other two. Pair with `continue_workflow_if_action_fails: true` if you want the row to keep flowing on a miss. - The selling point is the pre-bucketed-by-department output. If you don't need that, BuiltWith (more coverage) or TheirStack (more precise + job-posting signal) are usually better choices. ================================================================================ 5. WHERE IT FITS IN A WORKFLOW ================================================================================ Pattern (departmental tech-stack ICP filter): score or filter companies on whether they use specific technologies in a particular department — useful when your product targets a specific function (e.g. "uses Salesforce in sales", "uses HubSpot in marketing", "runs a specific Java framework in product"). input (company name / domain / LinkedIn URL) -> company_tech_stack_floqer (returns full_tech_stack plus per-department arrays: sales, marketing, hr, it_security, programming_languages_frameworks, etc.) -> filter / score on the relevant department array (e.g. sales contains "Salesforce") -> outreach. Pattern (technographic insights): use the per-department breakdown as context for a downstream LLM step that generates per-prospect talking points or scores fit by stack. input (company name / domain / LinkedIn URL) -> company_tech_stack_floqer -> llm_models (prompt: read the per-department arrays and call out integrations, modernization signals, or competitive overlap) -> outreach. ================================================================================ 6. WHEN TO USE ================================================================================ Use company_tech_stack_floqer when you need a departmental tech-stack breakdown — i.e. you care not just whether a technology is used, but where in the org it sits (sales, marketing, HR, IT security, programming languages, etc.). Pair it with filtering / scoring for ICP targeting, or with an LLM step for per-company technographic insights and personalized outreach. ================================================================================ 7. WHEN NOT TO USE ================================================================================ Need the broadest possible coverage (e.g. catalog every tech the site has ever touched), or historical FirstDetected/LastDetected dates. Floqer native doesn't surface either — BuiltWith does. -> company_tech_stack_enrichment_from_builtwith (https://floqer.com/docs/action-detail/company_tech_stack_enrichment_from_builtwith.txt) Need more precise technographic signal, or want hiring-derived detections (a job posting requiring a tech is hard evidence the company actually runs it in production). Floqer native doesn't include job-posting signal; TheirStack does. -> company_tech_stack_enrichment_using_their_stack (https://floqer.com/docs/action-detail/company_tech_stack_enrichment_using_their_stack.txt) The company isn't in this provider's data (action returned "No data found for company"). Try BuiltWith — it has the broadest coverage of small / newer / privately-marketed companies. -> company_tech_stack_enrichment_from_builtwith ================================================================================ This file is maintained manually. Last updated: 2026-05-14. Full interactive reference: https://floqer.com/docs/reference Action catalog: https://floqer.com/docs/action-catalog.txt