# GitLab Profile Phone Number Scraper (`neuro-scraper/gitlab-profile-phone-number-scraper`) Actor

GitLab Profile Phone Number Scraper SD - GitLab Profile Phone Number Scraper is a lead generation tool that extracts leads with public contact emails, bio, follower counts and profile URLs from GitLab profile URLs or usernames - GitLab profile scraper for creator outreach.

- **URL**: https://apify.com/neuro-scraper/gitlab-profile-phone-number-scraper.md
- **Developed by:** [Neuro Scraper](https://apify.com/neuro-scraper) (community)
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $2.99 / 1,000 results

This Actor is paid per event and usage. You are charged both the fixed price for specific events and for Apify platform usage.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

### GitLab Profile Phone Number Scraper

**GitLab Profile Phone Number Scraper** turns a keyword into a contact sheet of phone numbers published on GitLab. Give it search terms and it returns the accounts that publish a way to reach them, with the account name, handle and profile URL beside each contact.

It reads only what GitLab and Google already show a signed-out visitor. No login, no cookies, no private or partner API, no browser and no JavaScript rendering.

**Read this before your first run.** GitLab profiles expose a name, bio and avatar rather than follower statistics.

***

### What the GitLab Profile Phone Number Scraper does

The GitLab Profile Phone Number Scraper searches Google with a contact dork rather than a plain keyword: `site:gitlab.com developer whatsapp "+44"`. That asks for the pages which already publish a phone number, instead of every page matching a word.

Each result block yields the account and the phone number together, in one request. Google no longer prints the target URL on most layouts, so the handle comes from what it does print: the "GitLab - handle" site label, the breadcrumb, or a `Name (@handle)` title.

Every row is written to the dataset the moment it is found and logged as it is written, so a run is readable while it is still going.

Phone numbers are validated by libphonenumber against the real numbering plan of the country you searched, so order numbers, dates and follower counts cannot reach the dataset. Each number is returned in E.164 form and in the national format its country uses.

***

### Input reference for the GitLab Profile Phone Number Scraper

| Field | Type | Default | Meaning |
|---|---|---|---|
| `keywords` | array | `developer, maintainer` | Search terms - a niche, job title or industry. |
| `location` | string | `""` | Added to every query, e.g. `New York`. |
| `countries` | array | US, UK, India | Which countries' numbers to look for. Name, ISO code or dial code. Each one multiplies the searches. |
| `maxEmails` | integer 1-10000 | `20` | Stop once this many unique contacts are found. |
| `expandQueries` | boolean | `true` | Search each keyword in several phrasings. |
| `queryModifiers` | array | per platform | Extra words combined with each keyword. |
| `maxPagesPerQuery` | integer 1-50 | `30` | Google result pages per query. |
| `maxConcurrency` | integer 1-20 | `5` | Queries run in parallel. |
| `countryCode` | string | `""` | Two-letter country for the search proxy. |

### Output

Every row the GitLab Profile Phone Number Scraper writes:

| Field | Meaning |
|---|---|
| `network` | Platform name |
| `keyword` | The keyword that found this row |
| `query` | The exact Google query used |
| `phone` | The number in E.164 form, e.g. `+447590574946` |
| `phoneNational` | The same number as its country writes it |
| `phoneCountry` | ISO country the number belongs to |
| `accountName` | Account label as the platform shows it |
| `fullName` | Display name where published |
| `username` | Handle |
| `profileUrl` | Canonical profile URL |
| `url` | The page the result pointed at |
| `description` | The result snippet, cleaned |
| `foundAt` | ISO 8601 UTC timestamp |

```json
{
  "network": "GitLab",
  "keyword": "developer",
  "accountName": "examplestudio",
  "fullName": "Example Studio",
  "username": "examplestudio",
  "profileUrl": "https://gitlab.com/examplestudio",
  "phone": "+447590574946",
  "phoneNational": "07590 574946",
  "phoneCountry": "GB"
}
```

### How to use the GitLab Profile Phone Number Scraper

1. Put your search terms in **Keywords** - the niche, job title or industry you sell to.
2. Add a **Location** if the list should be local.
3. Pick the **Countries** whose numbers you want. Every number is validated against that country's numbering plan.
4. Set **Max results** to cap the run, then start it.
5. Export the dataset as CSV, JSON or Excel, or pull it through the Apify API.

### Use cases

**Lead generation.** Build a list of GitLab accounts in one niche that publish a phone number, with the handle and profile URL for context before you write.

**Recruiting.** Find people describing themselves with a role keyword and reach them on the contact they chose to publish.

**Agency prospecting.** Search a niche and a city, and get a prospect sheet with the account and the contact side by side.

**CRM enrichment.** Feed `profileUrl` and `phone` straight into your CRM; the `keyword` and `query` columns record where each row came from.

### Limitations, stated plainly

- Only contacts already published in public GitLab pages indexed by Google. Nothing hidden from a signed-out visitor is reachable, and none is guessed from a name.
- GitLab profiles expose a name, bio and avatar rather than follower statistics.
- Coverage depends on what Google has indexed, so a narrow niche returns fewer rows than a broad one. Raising **Max pages per query** and adding keywords helps.
- The free Apify plan caps a run at 20 results.
- A number written without its country code can only be validated against the country you searched, so search the countries you actually sell to.

### Pricing

Pay per result: you are charged for each row written to the dataset, and nothing for a run that finds nothing. Platform and proxy costs are included in that price.

### GitLab Profile Phone Number Scraper vs manual research

Done by hand, one qualified contact takes two to four minutes: find the account, open it, read
the page, copy the phone number, paste it into a sheet.

The GitLab Profile Phone Number Scraper does the same work continuously, with no tab switching
and no transcription errors. A hundred records is minutes rather than an afternoon.

It also captures what manual research usually skips. The account name, the profile URL and the
exact keyword that surfaced the row all land in the same record.

That context turns a raw list into a prioritised one. The GitLab Profile Phone Number Scraper
lets you sort and filter before a single message is written.

### Using the GitLab Profile Phone Number Scraper in a workflow

Most teams run the GitLab Profile Phone Number Scraper on a schedule and treat the dataset as a
feed rather than a one-off export.

Point a webhook at your own endpoint and each finished run pushes its rows straight into your
CRM, with no manual download step.

The stable output schema matters here. Because every row from the GitLab Profile Phone Number
Scraper has identical keys, your integration never needs to handle a missing field.

A common pattern is a nightly keyword run feeding a dedupe step. Another is enrichment: widen
the keyword list and let the GitLab Profile Phone Number Scraper fill the gaps in an existing
sheet.

#### Troubleshooting the GitLab Profile Phone Number Scraper

**Few or no rows.** The keyword is probably too broad or too narrow. Ten specific keywords beat
one generic one, and adding a location raises the hit rate.

**Rows without contacts.** That is normal - most accounts publish none. The GitLab Profile
Phone Number Scraper reports only what is genuinely on the page.

**The run is slow to start.** Lower the concurrency. The GitLab Profile Phone Number Scraper is
querying faster than the proxy pool is comfortable with.

**Fewer results than requested.** Google caps one query at roughly 300 results. Query expansion
is what reaches past that ceiling, so leave it on.

#### How the GitLab Profile Phone Number Scraper handles export and integration

Export the GitLab Profile Phone Number Scraper dataset as CSV, JSON, Excel or XML from the
Apify console, or pull it through the API.

Every field is flat - no nested objects - so the CSV opens cleanly in Excel or Google Sheets
without a parsing step.

### Related Actors

| Actor | What it collects |
|---|---|
| [GitLab Profile Email Scraper](https://apify.com/neuro-scraper/gitlab-profile-email-scraper) | Emails plus bio and follower counts from GitLab profiles |
| [GitLab Profile Email and Phone Number Scraper](https://apify.com/neuro-scraper/gitlab-profile-email-and-phone-number-scraper) | Emails, phone numbers and profile details from GitLab |
| [Behance Profile Email Scraper](https://apify.com/leads-scraper/behance-profile-email-scraper) | Emails plus bio and follower counts from Behance profiles |
| [Bluesky Profile Email Scraper](https://apify.com/leads-scraper/bluesky-profile-email-scraper) | Emails plus bio and follower counts from Bluesky profiles |
| [Buy Me a Coffee Profile Email Scraper](https://apify.com/neuro-scraper/buy-me-a-coffee-profile-email-scraper) | Emails plus bio and follower counts from Buy Me a Coffee profiles |
| [DEV Community Profile Email Scraper](https://apify.com/neuro-scraper/dev-to-profile-email-scraper) | Emails plus bio and follower counts from DEV Community profiles |
| [DeviantArt Profile Email Scraper](https://apify.com/leads-scraper/deviantart-profile-email-scraper) | Emails plus bio and follower counts from DeviantArt profiles |
| [Dribbble Profile Email Scraper](https://apify.com/leads-scraper/dribbble-profile-email-scraper) | Emails plus bio and follower counts from Dribbble profiles |
| [Facebook Profile Email Scraper](https://apify.com/leads-scraper/facebook-profile-email-scraper) | Emails plus bio and follower counts from Facebook profiles |
| [Flipboard Profile Email Scraper](https://apify.com/neuro-scraper/flipboard-profile-email-scraper) | Emails plus bio and follower counts from Flipboard profiles |
| [GitHub Profile Email Scraper](https://apify.com/leads-scraper/github-profile-email-scraper) | Emails plus bio and follower counts from GitHub profiles |
| [Gumroad Profile Email Scraper](https://apify.com/leads-scraper/gumroad-profile-email-scraper) | Emails plus bio and follower counts from Gumroad profiles |
| [Hashnode Profile Email Scraper](https://apify.com/neuro-scraper/hashnode-profile-email-scraper) | Emails plus bio and follower counts from Hashnode profiles |
| [Hugging Face Profile Email Scraper](https://apify.com/neuro-scraper/hugging-face-profile-email-scraper) | Emails plus bio and follower counts from Hugging Face profiles |
| [Instagram Profile Email Scraper](https://apify.com/leads-scraper/instagram-profile-email-scraper) | Emails plus bio and follower counts from Instagram profiles |
| [Kick Profile Email Scraper](https://apify.com/leads-scraper/kick-profile-email-scraper) | Emails plus bio and follower counts from Kick profiles |
| [Linktree Profile Email Scraper](https://apify.com/leads-scraper/linktree-profile-email-scraper) | Emails plus bio and follower counts from Linktree profiles |
| [Mastodon Profile Email Scraper](https://apify.com/leads-scraper/mastodon-profile-email-scraper) | Emails plus bio and follower counts from Mastodon profiles |
| [Mixcloud Profile Email Scraper](https://apify.com/leads-scraper/mixcloud-profile-email-scraper) | Emails plus bio and follower counts from Mixcloud profiles |
| [Patreon Profile Email Scraper](https://apify.com/leads-scraper/patreon-profile-email-scraper) | Emails plus bio and follower counts from Patreon profiles |
| [Pinterest Profile Email Scraper](https://apify.com/leads-scraper/pinterest-profile-email-scraper) | Emails plus bio and follower counts from Pinterest profiles |
| [Snapchat Profile Email Scraper](https://apify.com/leads-scraper/snapchat-profile-email-scraper) | Emails plus bio and follower counts from Snapchat profiles |
| [SoundCloud Profile Email Scraper](https://apify.com/leads-scraper/soundcloud-profile-email-scraper) | Emails plus bio and follower counts from SoundCloud profiles |
| [Substack Profile Email Scraper](https://apify.com/leads-scraper/substack-profile-email-scraper) | Emails plus bio and follower counts from Substack profiles |
| [Telegram Profile Email Scraper](https://apify.com/leads-scraper/telegram-profile-email-scraper) | Emails plus bio and follower counts from Telegram profiles |
| [Threads Profile Email Scraper](https://apify.com/leads-scraper/threads-profile-email-scraper) | Emails plus bio and follower counts from Threads profiles |
| [TikTok Profile Email Scraper](https://apify.com/leads-scraper/tiktok-profile-email-scraper) | Emails plus bio and follower counts from TikTok profiles |
| [Tumblr Profile Email Scraper](https://apify.com/leads-scraper/tumblr-profile-email-scraper) | Emails plus bio and follower counts from Tumblr profiles |
| [Twitch Profile Email Scraper](https://apify.com/leads-scraper/twitch-profile-email-scraper) | Emails plus bio and follower counts from Twitch profiles |
| [X Profile Email Scraper](https://apify.com/leads-scraper/x-profile-email-scraper) | Emails plus bio and follower counts from X profiles |
| [YouTube Profile Email Scraper](https://apify.com/leads-scraper/youtube-profile-email-scraper) | Emails plus bio and follower counts from YouTube profiles |
| [Behance Profile Email and Phone Number Scraper](https://apify.com/leads-scraper/behance-profile-email-and-phone-number-scraper) | Emails, phone numbers and profile details from Behance |
| [Bluesky Profile Email and Phone Number Scraper](https://apify.com/leads-scraper/bluesky-profile-email-and-phone-number-scraper) | Emails, phone numbers and profile details from Bluesky |
| [Buy Me a Coffee Profile Email and Phone Number Scraper](https://apify.com/neuro-scraper/buy-me-a-coffee-profile-email-and-phone-number-scraper) | Emails, phone numbers and profile details from Buy Me a Coffee |
| [DEV Community Profile Email and Phone Number Scraper](https://apify.com/neuro-scraper/dev-to-profile-email-and-phone-number-scraper) | Emails, phone numbers and profile details from DEV Community |
| [DeviantArt Profile Email and Phone Number Scraper](https://apify.com/leads-scraper/deviantart-profile-email-and-phone-number-scraper) | Emails, phone numbers and profile details from DeviantArt |
| [Dribbble Profile Email and Phone Number Scraper](https://apify.com/leads-scraper/dribbble-profile-email-and-phone-number-scraper) | Emails, phone numbers and profile details from Dribbble |
| [Facebook Profile Email and Phone Number Scraper](https://apify.com/leads-scraper/facebook-profile-email-and-phone-number-scraper) | Emails, phone numbers and profile details from Facebook |
| [Flipboard Profile Email and Phone Number Scraper](https://apify.com/neuro-scraper/flipboard-profile-email-and-phone-number-scraper) | Emails, phone numbers and profile details from Flipboard |
| [GitHub Profile Email and Phone Number Scraper](https://apify.com/leads-scraper/github-profile-email-and-phone-number-scraper) | Emails, phone numbers and profile details from GitHub |
| [Gumroad Profile Email and Phone Number Scraper](https://apify.com/leads-scraper/gumroad-profile-email-and-phone-number-scraper) | Emails, phone numbers and profile details from Gumroad |
| [Hashnode Profile Email and Phone Number Scraper](https://apify.com/neuro-scraper/hashnode-profile-email-and-phone-number-scraper) | Emails, phone numbers and profile details from Hashnode |

### FAQ

#### Does the GitLab Profile Phone Number Scraper need a login or cookies?

No. It reads public search results and public GitLab pages only.

#### Where do the phone numbers come from?

From the public page the search result points at - the same text any visitor can read.

#### Are the numbers real?

Every number is checked against its country's numbering plan before it is written, so invalid strings are dropped rather than shipped.

#### Can I run it on a schedule?

Yes, with Apify Schedules. Progress is saved, so a migrated run continues instead of starting over.

**Something is missing or wrong.**\
Email <neurodata.apify@gmail.com>.

### More about the GitLab Profile Phone Number Scraper

Because the GitLab Profile Phone Number Scraper reads only pages Google has already indexed, it
never needs a login, a cookie jar or an API key from the platform it reads.

Run the GitLab Profile Phone Number Scraper with a narrow keyword set first. A short test run
shows the yield of a niche before a large run is paid for.

Output from the GitLab Profile Phone Number Scraper is flat - no nested objects - so a CSV
export opens cleanly in Excel or Google Sheets with no parsing step.

Pair the GitLab Profile Phone Number Scraper with Apify Schedules to rebuild a prospect list
weekly and catch accounts that published contact details since the last run.

Proxy and platform costs are already inside the per-result price of the GitLab Profile Phone
Number Scraper, so the figure quoted on the Store page is the figure you pay.

Every field the GitLab Profile Phone Number Scraper returns is documented in the output table
above, and the schema does not change between runs or between platforms.

#### GitLab Profile Phone Number Scraper at a glance

Teams that outgrow manual prospecting usually reach for the GitLab Profile Phone Number Scraper
first, because it needs no setup beyond a keyword list and a result cap.

Concurrency on the GitLab Profile Phone Number Scraper is adjustable, so a run can be tuned for
speed on a quiet network or for reliability on a busy one.

If a run of the GitLab Profile Phone Number Scraper is interrupted, Apify migrates it and
progress resumes rather than restarting from the first query.

Agencies commonly schedule the GitLab Profile Phone Number Scraper weekly, then diff each
dataset against the last to surface only newly published contacts.

Nothing in the GitLab Profile Phone Number Scraper guesses a contact from a name pattern. A
value is written only when it appears on the page itself.

Because the GitLab Profile Phone Number Scraper shares its output schema with every other
scraper in this catalogue, a pipeline built once works across all of them.

### Leave a review

If the GitLab Profile Phone Number Scraper saved you time, please leave a star rating and a
short review on the GitLab Profile Phone Number Scraper page.

Reviews are how other buyers judge whether a tool works, and they tell us which features to
build next.

If something did not work, email <neurodata.apify@gmail.com>
instead - bugs get fixed faster than they get complained about.

### Support

Questions, bugs or a custom build: <neurodata.apify@gmail.com>.

# Actor input Schema

## `keywords` (type: `array`):

Search terms - a niche, job title or industry. The Actor finds GitLab accounts matching each term, then scrapes every account it finds. Use this when you do not already have a list of accounts. You can combine keywords with the profile URLs below.

## `location` (type: `string`):

Added to every keyword search, e.g. `New York`. Leave empty to search everywhere. Only applies to keyword search.

## `profileUrls` (type: `array`):

Full GitLab profile URLs, e.g. `https://gitlab.com/username`. Bare usernames also work. Use this when you already know which accounts you want.

## `usernames` (type: `array`):

GitLab handles without the URL. Combined with the list above.

## `customDomains` (type: `array`):

Domains the keyword search asks Google for, e.g. `@gmail.com`. Also filters results to these domains. Leave EMPTY (recommended) to search the 12 biggest free-mail providers - Gmail, Yahoo, Outlook, Hotmail, iCloud, AOL, Proton, Live, GMX, Mail.com, Yandex and Zoho - and keep every address found, including company domains. Listing domains here narrows the search to only those.

## `onlyWithEmail` (type: `boolean`):

Skip profiles whose public bio contains no contact address.

## `maxProfiles` (type: `integer`):

Stop after this many profiles have been saved.

## `maxPagesPerKeyword` (type: `integer`):

How many Google results pages to read per search query. Raise it to find more accounts. Keyword search only.

## `expandQueries` (type: `boolean`):

Search each keyword in several phrasings (keyword + "email", + "contact", ...) to reach accounts a single query misses. Keyword search only.

## `queryModifiers` (type: `array`):

Extra words combined with each keyword when query expansion is on. Leave empty to use the defaults for this platform.

## `maxConcurrency` (type: `integer`):

How many profiles are fetched in parallel, and how many Google searches run at once. Raise it for speed, lower it if you see blocked rows.

## `proxyGroup` (type: `string`):

RESIDENTIAL is recommended. Profile pages block datacenter IPs.

## `countryCode` (type: `string`):

Two-letter country code for the proxy (e.g. US, GB, DE). Empty for any.

## Actor input object example

```json
{
  "keywords": [
    "developer",
    "maintainer"
  ],
  "location": "",
  "profileUrls": [],
  "usernames": [],
  "customDomains": [],
  "onlyWithEmail": false,
  "maxProfiles": 100,
  "maxPagesPerKeyword": 5,
  "expandQueries": true,
  "queryModifiers": [
    "email",
    "contact",
    "maintainer",
    "author",
    "support"
  ],
  "maxConcurrency": 10,
  "proxyGroup": "RESIDENTIAL",
  "countryCode": ""
}
```

# Actor output Schema

## `results` (type: `string`):

Records produced by GitLab Profile Phone Number Scraper, stored in the run's default dataset.

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "keywords": [
        "developer",
        "maintainer"
    ],
    "location": "",
    "countryCode": ""
};

// Run the Actor and wait for it to finish
const run = await client.actor("neuro-scraper/gitlab-profile-phone-number-scraper").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {
    "keywords": [
        "developer",
        "maintainer",
    ],
    "location": "",
    "countryCode": "",
}

# Run the Actor and wait for it to finish
run = client.actor("neuro-scraper/gitlab-profile-phone-number-scraper").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "keywords": [
    "developer",
    "maintainer"
  ],
  "location": "",
  "countryCode": ""
}' |
apify call neuro-scraper/gitlab-profile-phone-number-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,neuro-scraper/gitlab-profile-phone-number-scraper"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/S8yd4dcqzfXoSJVEq/builds/IpwGgiG5IK8otI8P7/openapi.json