Skip to main content

​
What It Does

  • Fetches real customers of a company using PredictLeads.
  • Works with static domains or dynamic (@Insert Input) template variables.
  • Automatically handles pagination and limits.
  • Enriches workflows with customer-domain relationships.
  • Preserves original input columns when running in batch mode.

​
🏁 Getting Started

Get Company Customers config screenshot
1

Add the Node

Drag Get Company Customers into your flow.
2

Enter the Company Domain

Enter a static domain or use dynamic values like {{company_domain}} via @Insert Input.
3

Set Your Limit

Choose how many customers to fetch for each company (0–10,000).
4

Run the Flow

The node fetches customers and outputs enriched rows containing customer details and original columns.

​
Inputs

​
🛠️ Required Fields

  • Company Domain (✅)
    Accepts static text or template variables like {{domain}}.
    Why it matters: Defines which company’s customers to fetch.
  • Limit (✅)
    Number of customers to return (0–10,000).
    Why it matters: Controls output size and credit usage.
Template variables must match real column names in your input table.

​
Output

Outputs the following fields for each customer:
  • customer_name
  • customer_domain
  • source_url
  • first_seen_at
  • last_seen_at
  • All original input columns
Conflicting column names are auto-suffixed (e.g., _1, _2).

​
How It Works

  1. You enter a domain (static or dynamic).
  2. The node resolves template variables.
  3. Up to your limit, customers are collected.
  4. Enriched rows are output.
  5. Original columns are preserved.

​
🚀 Example Use Cases & Prompts

Use CaseSetup Example
Map competitive ecosystemscompany_domain = microsoft.com
Build customer graphsRun on a CRM list of domains
Analyze SaaS dependency chainsFilter by industry → run node
Enrich company profilesAdd customer footprint as a column

​
✨ Pro Tips

Use template variables like {{primary_domain}} to enrich hundreds of companies at once.
Reduce the limit to save credits when a company has many customers.
Use a Filter Rows node afterward to isolate relevant customers.

​
⚠️ Important Considerations

Credits are charged per page of data fetched (1 page = up to 100 customers).
Missing template variables cause validation to fail before running.
Invalid or empty domains cause skipped rows or errors.

​
🛠 Troubleshooting & Gotchas

SymptomLikely CauseQuick Fix
Empty outputInvalid domain or no customersCheck the domain / widen the limit
High credit usageLarge limit → many pagesLower the limit
Unexpected columnsName conflictLook for suffixes like _1

​
📝 FAQ

Yes — enter a static domain like microsoft.com.
Yes, if the column exists in your input.
The node will skip or error depending on the case.
No — it logs the error and continues.

​
💰 Pricing

ActionCredit Cost
Per page fetched (up to 100 customers)2 credits
No customers found = no credits charged.

Fetch real customer ecosystems — perfect for enrichment, mapping, and GTM insights. 🔍