Floqer Use Case Catalog

End-to-end Floqer workflows for common GTM problems. Use this catalog to find
the closest match for a user's requirement, then read its detail file (linked
under LOCATION on each entry) in full before designing a workflow.

For action-level details (not workflows), see https://floqer.com/docs/action-catalog.txt.

INDEX:
  1. Outbound prospecting
  2. Inbound enrichment and routing
  3. Intent-driven outreach
  4. CRM hygiene
  5. Account research and scoring
  6. Data operations

================================================================================
1. OUTBOUND PROSPECTING
================================================================================

Cold workflows from ICP definition through to sequenced outreach.

NAME: ICP-based outbound prospecting
LOCATION: https://floqer.com/docs/use-case-detail/icp_outbound_prospecting.txt
Problem: User has an ICP (firmographics + target role) and wants a list of verified contacts pushed into an outreach sequence, starting from zero.
Trigger keywords: outbound, prospect, ICP, find leads, build a list, sequence
Inputs: ICP firmographic filters, target role(s), connected sequencing tool, optional exclusion list
Outputs: verified contact list pushed into the chosen sequencer + Floqer table snapshot

NAME: Find people at a list of target companies
LOCATION: https://floqer.com/docs/use-case-detail/find_people_at_target_companies.txt
Problem: User already has a company list they sourced (CSV, saved search, CRM export) and just wants the right people inside each one as a usable contact list — no ICP discovery, no firmographic filtering, no scoring or tiering. The most common "find people" request, and the one most often built wrong: the employee finder is unintuitive, so agentic builds ship a full persona title into the contains-any-term job_title filter (recall collapses to near-zero), skip the array→rows fan-out before email enrichment, leave the per-employee count uncapped, or read row status instead of cell status on "No employees found".
Trigger keywords: find people, find contacts, people at companies, company list to contacts, who works at, employees at company, list of companies I have, no ICP, no scoring, just find the people, decision makers at these accounts, account list to people, find employees, get_employees, fan out to rows
Inputs: company list (one per row, with domain or LinkedIn URL), a loose people selector (function(s) + seniority you'll accept), optional per-company cap, country filter, and outreach/CRM destination
Outputs: one-row-per-person Floqer sheet (full name, LinkedIn, title, company, usually a verified work email); optionally pushed to a sequencer or CRM

NAME: Still-at-company gate before outbound (multi-role aware)
LOCATION: https://floqer.com/docs/use-case-detail/still_at_company_outbound_gate.txt
Problem: An existing outbound chain scrapes each prospect's LinkedIn, then spends on email / phone / CRM / sequencer steps. User wants to silently drop, mid-chain before that spend, anyone who has left the company they were sourced for. Keys on the experiences array's current roles (every stint with no end date), NOT the single current_company_name — so people who hold multiple concurrent roles (founder + advisor + NED) aren't wrongly dropped when LinkedIn flags a different role as primary. This is an inline gate, not a verdict report (for the report variant, see CRM contact change detection).
Trigger keywords: still at company, moved on, job change gate, suppress movers, stale prospect, drop before outreach, pre-send check, experiences current roles, multi-role, founder advisor, outbound hygiene, before sequencer
Inputs: existing outbound sheet with company_name per row + an enrich_person_linkedin_profile scrape upstream; optional clean-company LLM step to use as the match reference
Outputs: movers (confident "no") halted before the first paid step via a filter; everyone else (matches + ambiguous/missing-data, keep-on-doubt) continues to outreach unchanged

================================================================================
2. INBOUND ENRICHMENT AND ROUTING
================================================================================

Workflows triggered by an inbound signal (form fill, signup, demo request)
that enrich, score, and route the lead.

(none yet)

================================================================================
3. INTENT-DRIVEN OUTREACH
================================================================================

Workflows triggered by external intent signals — hiring posts, social
activity, web visits, tech-stack changes.

NAME: Hiring-signal-triggered outbound
LOCATION: https://floqer.com/docs/use-case-detail/hiring_signal_outbound.txt
Problem: User has a list builder pushing job postings into Floqer as they're discovered; wants each company-with-hiring-signal to surface the right ICP decision maker and enroll them in outreach automatically. Same company hiring multiple roles = one intent signal (company-level dedupe), not N.
Trigger keywords: hiring signal, job postings, intent signal, list builder webhook, jobs feed, role posting, hiring intent, talent signal, dedupe by company, jobs to contacts, recruiting (variant)
Inputs: list-builder webhook delivering job postings (job_title + company_name + company_domain + ~70 metadata fields), user's ICP role definition (titles + seniority), connected sequencer, optional Floqer-side filters on top of list-builder criteria
Outputs: deduped per-company hiring signal log on the Jobs Feed sheet, fan-out enriched ICP contacts with verified work email, contacts enrolled in the user's connected sequencer (default) or pushed to a review sheet (variation)

================================================================================
4. CRM HYGIENE
================================================================================

Dedupe, fill missing fields, sync between CRMs, normalize data.

NAME: CRM contact change detection (still at company + title change)
LOCATION: https://floqer.com/docs/use-case-detail/crm_contact_change_detection.txt
Problem: User has a CRM-sourced contact list and wants to detect, by re-scraping each contact's LinkedIn, whether the person is still at the company on record and whether their title has changed. Output is a 4-value verdict (yes / no / unknown / scrape_failed) per contact, plus an independent title-change check, so downstream consumers can route on "moved on", "promoted internally", "couldn't verify", or "still in place".
Trigger keywords: contact monitoring, job change detection, still at company, role change, promotion detection, CRM hygiene, LinkedIn scrape, contact churn, mover detection, congrats sequencer, CRM enrichment refresh
Inputs: per-row CRM contact data — LinkedIn URL (flagship form, required), Company Name (required), Domain (optional), Known Job Title (optional; enables the title-change check)
Outputs: Changed Company verdict (yes / no / unknown / scrape_failed), Title Changed verdict (yes / no / unknown / skipped), human-readable Title Change Message string

NAME: CRM pull, enrich, and update in place (multi-source)
LOCATION: https://floqer.com/docs/use-case-detail/crm_pull_enrich_update.txt
Problem: User wants to pull a slice of CRM records (a list, view, or filter expression), run an enrichment / scoring / writing step per row, and write the result back to the SAME source records — record IDs never leave the source system. HubSpot is verified end-to-end via the `hubspot_contact_added` source + `hubspot_update_object` action; Salesforce and Pipedrive sections are scaffolded but not yet documented.
Trigger keywords: enrich in place, write back, update CRM property, refresh contacts, score and push, HubSpot enrichment, hubspot_contact_added source, hubspot_update_object, sync source, field_mapping, enrich loop, CRM annotation
Inputs: connected CRM (HubSpot today), record selection criteria (list ID or property filter), target property to write to, enrichment expression (JS / LLM / web research chain), one-time vs scheduled pull, row cap (default 3–5 on first build)
Outputs: chosen CRM property updated on each pulled record (HubSpot's response echoes the new property value), one Floqer row per CRM record with per-cell enrichment + writeback status

================================================================================
5. ACCOUNT RESEARCH AND SCORING
================================================================================

Qualify or rank accounts and contacts using firmographic, technographic, or
AI-derived signals.

NAME: Account research and scoring
LOCATION: https://floqer.com/docs/use-case-detail/account_research_and_scoring.txt
Problem: User has a list of target accounts and wants to qualify, score, and tier them based on time-windowed pressure signals (funding, leadership changes, product launches, geo expansion, hiring patterns, tech stack), with AI-generated outreach briefs on top-tier accounts.
Trigger keywords: score, tier, qualify, account scoring, prioritize accounts, GTM pressure, intent signals, account list, rubric
Inputs: target account list (company name + domain), ICP definition, signal definitions and time windows, tier thresholds
Outputs: per-account score (0-100), tier (T1/T2/T3), per-signal CONFIRMED/NOT FOUND/UNCERTAIN with evidence, AI brief on top-tier rows

NAME: Account scoring with cooldown Slack digest
LOCATION: https://floqer.com/docs/use-case-detail/account_scoring_with_cooldown_digest.txt
Problem: User runs an account list through a scoring chain on a recurring schedule and wants a Slack digest of new high-tier accounts only — same accounts should not be re-notified within a 30-day (or configurable) cooldown window. Multi-recipient supported via one row per recipient on the digest sheet.
Trigger keywords: account monitoring, recurring digest, Slack alert, watch list, top accounts, daily digest, weekly digest, do not re-notify, cooldown, exclusion list, suppression, mention log, per-rep digest, account owner ping
Inputs: target account list (account_id + name + domain + vertical, optional account_owner), signal definitions / research actions, tier thresholds, cooldown window, recipient roster (one row per pinged person — slack_target + optional account_owner filter)
Outputs: per-account score + tier on master sheet, recurring per-recipient Slack digests of new T1 accounts (cooldown-filtered, optionally owner-scoped), Mentioned Accounts log for audit + future cooldown lookups

================================================================================
6. DATA OPERATIONS
================================================================================

Utility flows — bulk transforms, list joins, CSV pipelines, lookups — that
feed other use cases.

NAME: Cross-table lookup via HTTP API Call
LOCATION: https://floqer.com/docs/use-case-detail/cross_floqer_table_lookup.txt
Problem: User needs to read rows from another Floqer sheet or workflow, filtering by an action-output column (not just inputs), aggregating across all rows, or reading multi-column data per match — beyond what lookup_another_floqer_workflow_row supports today.
Trigger keywords: cross-sheet lookup, read another floq, fetch rows, digest, aggregate, http_api_call, filter by output, exclusion list, cooldown
Inputs: target workflow + sheet id, Floqer API key, filter predicates (applied client-side in JS), optional target action_instance_ids for output-column filtering
Outputs: filtered/projected JSON array of rows ready for downstream actions (fan-out, digest, CRM write, set-difference)

NAME: Extract data from CRM (multi-source)
LOCATION: https://floqer.com/docs/use-case-detail/extract_data_from_crm.txt
Problem: User wants a point-in-time snapshot of records (contacts, companies / accounts) from one or more CRMs (Salesforce, HubSpot — Pipedrive pending) into a Floqer sub-sheet. Handles per-CRM filter semantics (HubSpot is exact-match only; Salesforce supports contains via exact_match=false), normalises the structured_array outputs into a unified schema via the responseId pattern, and fans out via push_data_to_sheet.
Trigger keywords: extract from CRM, pull contacts, pull accounts, export Salesforce contacts, export HubSpot contacts, multi-CRM, CRM snapshot, lookup → sub-sheet, raw to structured, responseId pattern
Inputs: connected CRM(s) (HubSpot and/or Salesforce), object type (contacts | companies | Contact | Account), filter properties + values, optional row caps
Outputs: Floqer sub-sheet with N rows (default schema: source, id, first_name, last_name, email, phone, title, company); per-CRM raw structured_arrays preserved on the main sheet for downstream consumers

================================================================================