ACTION_ID: person_enrich_by_floqer NAME: Floqer: Person contact enrich CATEGORY: scrape CREDITS: 1 Find phone numbers and emails for an individual prospect using Floqer's bundled person-enrichment provider. Given any combination of identifying signals (LinkedIn URL, an existing email or phone, full name, current company), the action returns a primary professional email and phone number plus any additional emails and phone numbers that match the same person — useful as a one-shot contact-data step before email verification or outreach. 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 ================================================================================ person_linkedin_url (url, optional) — Person LinkedIn URL. person_email (email, optional) — Person Email. person_phone_number (string, optional) — Person Phone Number. person_full_name (string, optional) — Person Full Name. company_name (string, optional) — Company Name. ================================================================================ 2. OUTPUTS ================================================================================ professional_email (type: email) — Professional Email. phone_number (type: string) — Phone Number. other_emails (type: raw_array) — Other Emails. other_phone_numbers (type: raw_array) — Other Phone Numbers. ================================================================================ 3. HOW TO CONFIGURE ================================================================================ Configure Action body: { "inputs": { "person_linkedin_url": "{{input.linkedin_url}}", "person_full_name": "{{input.full_name}}", "company_name": "{{input.company_name}}" } } Note: every individual input is marked optional, but the action will not run without enough signal to identify a person. At least one of the following identifying combinations must be passed: - `person_full_name` AND `company_name` (together) - `person_email` (alone) - `person_linkedin_url` (alone) Any of these is sufficient on its own; passing more than one only helps the provider disambiguate. Calling the action with no identifying input — or with only `person_full_name` on its own without a company — will not return a match. ================================================================================ 4. KEY NOTES ================================================================================ - One-shot lookup: the action returns the primary `professional_email` and `phone_number` plus any additional hits in `other_emails` / `other_phone_numbers`. It does NOT return profile attributes (location, title, employment history) — use `person_enrich_using_apollo` or `person_enrich_using_people_data_labs` if you need those. - Pair with an email-verification action (`person_work_email_verification_by_*`) before sending outreach. ================================================================================ 5. WHERE IT FITS IN A WORKFLOW ================================================================================ Pattern: linkedin_url ingest -> person_enrich_by_floqer -> person_work_email_verification_by_zerobounce (or another verifier) -> outreach. ================================================================================ 6. WHEN TO USE ================================================================================ Use person_enrich_by_floqer for Floqer-native person contact data. ================================================================================ 7. WHEN NOT TO USE ================================================================================ This action only returns the person's emails and phone numbers. It does not return any other person attributes — no location (city / state / country), no social profiles (Facebook, Twitter, GitHub, personal LinkedIn beyond what was passed in), no current/historical company name, no title, no headline, no employment history. If you need any of that, use a richer person-enrichment provider instead: -> person_enrich_using_apollo (Apollo: Person Enrich) (https://floqer.com/docs/action-detail/person_enrich_using_apollo.txt) -> person_enrich_using_people_data_labs (People Data Labs) (https://floqer.com/docs/action-detail/person_enrich_using_people_data_labs.txt) ================================================================================ This file is maintained manually. Last updated: 2026-04-30. Full interactive reference: https://floqer.com/docs/reference Action catalog: https://floqer.com/docs/action-catalog.txt