Integration

n8n Integration

---

Connect FindMyClient.org with n8n using the built-in HTTP Request node.

This integration is lightweight, flexible, and does not require a custom n8n community node. Since the FindMyClient API is REST-based, n8n can interact with it directly using standard HTTP requests.

Workflow Overview

0.0.6

The workflow:

1. Accepts a search query.
2. Starts a FindMyClient search job.
3. Retrieves the generated job_id.
4. Polls the API until the search is completed.
5. Extracts discovered emails.
6. Splits emails into individual records.
7. Optionally:
8. Save results to Google Sheets
9. Send emails via Gmail

Community Workflows

Browse the community-maintained collection of FindMyClient workflows, templates, and examples.

📂 Explore Community Workflows

Discover, download, contribute, or share your own automation workflows with the community.

Prerequisites

0.0.6

Before using this workflow:

• n8n installed
• FindMyClient API token
• Optional Google Sheets credentials
• Optional Gmail credentials

Configure Search Query

0.0.6

Add a Edit Fields (Set) node and input the search keyword.

Start Search Job

0.0.6

Add a HTTP Requests node and set the parameters.

Method

POST

URL

https://findmyclient.org/api/search

Headers

Name

{
  "token"
}

Value

{
  "YOUR-API-TOKEN"
}

Name

{
  "content-type"
}

Value

{
  "application/json"
}

Body Parameters

Name

{
  "query"
}

Value

{
  "{{ $json.query }}"
}

Store Job ID

0.0.6

Add a Edit Fields (Set) to store job_id.

This ID is used for polling search progress.

Poll Search Status

0.0.6

Add a HTTP Requests node and set the parameters.

Method

GET

URL

https://findmyclient.org/api/result/{{$json["job_id"]}}

Returned responses:

Processing

{
  "status": "processing"
}

Completed

{
  "status": "completed",
  "result": {
    "output": {
      "emails": [
        "info@example.com",
        "sales@example.com"
      ]
    }
  }
}

Wait and Retry

0.0.6

use Wait node and set the parameters.

If the status is not:

completed

The workflow:

1. Waits 30 seconds
2. Reuses the existing job_id
3. Checks the API again

This creates a polling loop until the search finishes.

Extract Results

0.0.6

When completed:

{
  "result": {
    "output": {
      "emails": [
        "info@example.com",
        "sales@example.com",
        "contact@example.com"
      ]
    }
  }
}

The workflow stores:

{
  "result.output.emails": [...]
}

Split Emails

0.0.6

The Split Emails node converts:

[
  "info@example.com",
  "sales@example.com",
  "contact@example.com"
]

Into:

{
  "email": "info@example.com"
}

{
  "email": "sales@example.com"
}

{
  "email": "contact@example.com"
}

This allows downstream processing of each email individually.

Optional: Save to Google Sheets

---

The workflow includes a disabled Google Sheets node.

Example spreadsheet:

Email
info@example.com
sales@example.com
contact@example.com

Enable the node and configure your spreadsheet credentials.

Optional: Send Email Notifications

---

The workflow includes a disabled Gmail node.

Possible use cases:

• Notify sales teams
• Send discovered leads
• Trigger CRM imports
• Alert automation systems

Enable the Gmail node and configure OAuth credentials.

API Endpoints Used

0.0.6

Start Search

POST /api/search

Request:

{
  "query": "italy winery"
}

Response:

{
  "job_id": "abc123"
}

0.0.6

Get Results

GET /api/result/{job_id}

Response:

{
  "status": "completed",
  "result": {
    "output": {
      "emails": []
    }
  }
}

0.0.6

Customization Ideas

Dynamic Queries

Replace the Set node with:

• Webhook Trigger
• Form Submission
• Google Sheets Input
• Airtable Input

Example:

{
  "query": "singapore cafe"
}

---

CRM Integration

After Split Emails, connect to:

• HubSpot
• Salesforce
• Pipedrive
• Zoho CRM

---

Lead Enrichment

After collecting emails, enrich contacts using:

• Apollo
• Clearbit
• Clay
• Custom APIs

---

Error Handling

Common scenarios:

Scenario	Action
Search still processing	Wait and retry
Empty result set	End workflow
Invalid API token	Update credentials
API timeout	Retry request
Network failure	Use n8n retry logic

0.0.6

Example End-to-End Flow

Input:

{
  "query": "italy winery"
}

Output:

[
  "info@winery1.com",
  "sales@winery2.com",
  "contact@winery3.com"
]

The workflow automatically handles:

• Job creation
• Polling
• Status checking
• Email extraction
• Record splitting
• Export and notification steps

making it suitable for automated lead generation pipelines.