Facebook Url To Id avatar

Facebook Url To Id

Pricing

from $1.99 / 1,000 results

Go to Apify Store
Facebook Url To Id

Facebook Url To Id

🔗 Convert Facebook URLs to accurate IDs in seconds! 🚀 Save time, boost workflow efficiency, and streamline data management for marketers, analysts, and developers. ✅ Fast, reliable, and easy to use. Try it now!

Pricing

from $1.99 / 1,000 results

Rating

0.0

(0)

Developer

SolidScraper

SolidScraper

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

6 days ago

Last modified

Share

Fcebook Url to Id 🔍

Fcebook Url to Id is an Apify actor that scrapes data from Facebook Pages, Groups, and Posts, resolving them to internal IDs. If you have a list of facebook url to id links (including facebook page url to id, facebook group url to id, and facebook post url to id), this actor helps you convert those URLs into usable ID-based records—saving you hours of manual lookup work for lead research and data enrichment at scale.

Whether you're a marketer, data analyst, or researcher, this actor is designed to help you turn messy URL lists (including facebook profile url to id and facebook vanity url to id) into structured outputs you can immediately analyze and combine with your own systems.


Why choose Fcebook Url to Id?

FeatureBenefit
Page, group, and post URL supportResolve facebook url to id links into IDs and related metadata in one run
Redirect-aware URL normalizationHandles share-style URLs so the actor works with the final landing page URL
Built-in reliability (fallbacks + retries)Includes retries and fallbacks for more resilient scraping runs
Structured dataset outputProduces consistent fields for facebook page id from url, facebook group url to id, and post IDs
Scales with batch inputsProcess multiple URLs by providing them in fbUrls
Apify proxy supportHelps with reliable fetching when targets are intermittently blocking requests

Key features

  • 🌐 Facebook URL support (pages, groups, posts): Accepts URLs you want to convert—covering facebook page url to id, facebook group url to id, and facebook post url to id
  • 🆔 ID resolution in structured form: Returns internal ID fields such as facebookId, and post identity fields like facebookId for posts
  • 🧾 Rich metadata extraction: Includes user/page and group/post context fields like user_name, group_name, actor_name, and message_text where available
  • 🛡️ Resilient scraping behavior: Uses retries and fallback logic to improve success rates on public web data
  • 🔄 URL type detection: Detects whether the input looks like a page, group, group post, or post and extracts accordingly (useful for find facebook id from url workflows)
  • 💾 Dataset-ready output: Pushes each result to the dataset with extracted_at timestamps so you can track freshness
  • Runs in batches: Submit a list of URLs and get back a table-friendly dataset you can export to JSON/CSV

Input

Provide input via an input.json file. Example structure:

{
"fbUrls": [
{
"url": "https://www.facebook.com/share/p/1WsVQCnCRM/"
}
]
}

Input Fields

FieldRequiredDescription
fbUrlsYesList of Facebook URLs (Pages, Groups, or Posts) you want the actor to resolve to IDs and metadata. You can provide plain URL strings or objects containing a url field.

Output

The actor saves each result item in JSON format to the dataset. Each URL produces either a resolved record (with type) or an error record (with failed set to true).

Example resolved output:

{
"type": "page",
"user_name": "Example Page Name",
"facebookId": "1234567890",
"description": "Example description text",
"directory_string": "example-directory",
"profile_picture": "https://example.com/profile.jpg",
"main_column_tiles": null,
"delegate_page_id": null,
"extracted_at": "2026-06-02T12:34:56.789012",
"source_url": "https://www.facebook.com/..."
}

Example post output:

{
"type": "post",
"actor_name": "Example Author",
"post_url": "https://www.facebook.com/1234567890",
"facebookId": "1234567890",
"message_text": "Post message text",
"reaction_count": 123,
"comment_count": 45,
"share_count": 7,
"creation_time": "2026-01-01T00:00:00",
"owning_profile_id": "0987654321",
"seo_title": "Example title",
"extracted_at": "2026-06-02T12:34:56.789012",
"source_url": "https://www.facebook.com/..."
}

Example error output:

{
"url": "https://www.facebook.com/...",
"error": "Error message text",
"failed": true
}

Output Fields

FieldTypeDescription
typestringOutput type: "page", "group", or "post"
facebookIdstringResolved Facebook ID associated with the URL (for pages, groups, and posts)
user_namestringUser or page name (for type: "page")
group_namestringGroup name (for type: "group")
actor_namestringPost author name (for type: "post")
source_urlstringThe original (or normalized) URL the actor processed
descriptionstringBest description text (for type: "page")
member_countstringGroup member count as formatted text (for type: "group")
reaction_countnumberReaction count for posts (for type: "post")
extracted_atstringISO timestamp for when the actor extracted data
errorstringError message text when a URL fails
failedbooleantrue when extraction failed for that URL
post_urlstringPost URL; in some cases it is normalized to https://www.facebook.com/{facebookId} for posts
message_textstringPost message text (for type: "post")

Note: the dataset view in this actor is configured with these fields: type, facebookId, user_name, group_name, actor_name, source_url, description, member_count, reaction_count, extracted_at.


How to use Fcebook Url to Id (via Apify Console)

  1. Open Apify Console
    Log in at https://console.apify.com and open the Actors page.

  2. Find Fcebook Url to Id
    Search for the actor titled Fcebook Url to Id and open its details page.

  3. Go to the INPUT tab
    Paste your JSON input into the input editor.

  4. Provide your URL list
    Add your Facebook links in fbUrls. Use page, group, or post URLs—this is the core step for facebook url to id and fb url to id lookup workflows.

  5. Run the actor
    Click Run. During execution, watch the logs to see which URL is being processed and whether any failures occur.

  6. Review results in the OUTPUT tab
    Open the dataset view named Facebook ID Data (the resolved identities table).

  7. Export your data
    Export the dataset to JSON/CSV (exact export options depend on Apify Console), then join it with your CRM or analysis pipeline.

No coding required—get accurate results in minutes with Fcebook Url to Id 🚀.


Advanced features & SEO optimization

  • 🔍 Engineered for “facebook url to id” workflows: Works directly with Facebook Pages, Groups, and Posts so you can quickly run facebook url to id lookup at scale
  • 🔁 Reliability improvements for public web data: Includes retries and fallbacks to reduce failures when targets temporarily block requests
  • 🧭 URL normalization for share-style links: Helps resolve share URLs into usable final URLs, improving success for inputs like facebook user id from url
  • 🧾 Consistent dataset structure: Returns fields like type, facebookId, group_name, actor_name, and extracted_at to keep downstream processing simple
  • 📊 Post metrics included: For post URLs, you also get reaction_count, comment_count, and share_count to enrich your analysis

Best use cases

  • 📈 Lead generation teams: Convert facebook page url to id links into ID-based records you can connect to outreach systems
  • 🧠 Market researchers: Resolve facebook group url to id inputs so you can analyze communities consistently across sources
  • 🗂️ Social media analysts: Turn facebook post url to id links into structured post-level metrics like reactions and comments
  • 🧑‍💼 Recruiters and sourcing: Speed up facebook profile url to id mapping when researching public profiles for talent pipelines
  • 💻 Developer data pipelines: Feed resolved IDs into downstream enrichment jobs and automate “find facebook id from url” steps
  • 🧾 CRM data hygiene: Normalize incoming URLs into stable IDs to reduce duplicates and improve entity matching
  • 🌍 Batch enrichment at scale: Process many URLs in one run using the fbUrls array, then export to JSON/CSV for analysis

Technical specifications

  • Supported Input Formats

    • fbUrls as an array of Facebook URLs (Pages, Groups, or Posts)
    • ✅ Items can be objects with a url field (e.g., { "url": "https://www.facebook.com/..." })
  • Proxy Support

    • ✅ Apify proxy support is used via proxy configuration during the run
  • Retry Mechanism

    • ✅ Uses retries (up to 3 attempts per request)
  • Dataset Structure

    • ✅ Saves results to the actor’s dataset with fields configured for the Facebook ID Data table view
  • Rate Limits & Performance

    • ✅ Performance depends on target responsiveness and proxy latency; batch processing is supported through fbUrls
  • Limitations

    • ❌ If extraction fails for a URL, the actor pushes an error object with failed: true
    • ❌ Missing/empty metadata fields can occur depending on what public data is available for the specific URL

FAQ

Can I use Fcebook Url to Id to convert a Facebook group URL to an ID?

✅ Yes. Provide your group link in fbUrls, and the actor will detect the URL type and return a resolved record including type: "group" and facebookId, along with fields like group_name and member_count when available. This covers use cases like facebook group url to id and facebook user id from url.

What Facebook URL types does it support?

✅ It supports Facebook Pages, Groups, and Posts. The actor detects the input URL type and extracts relevant fields for each kind of link, making it suitable for facebook page url to id, facebook group url to id, and facebook post url to id workflows.

Does it normalize share-style URLs?

✅ Yes. If your input contains a share-style URL, the actor attempts to follow it and use the final resolved URL before extracting IDs and metadata—helpful for robust facebook url to id lookups.

What happens if a URL fails to scrape?

❌ If a URL cannot be scraped or parsed successfully, the actor pushes an error record containing url, error, and failed: true to the dataset. You can filter these out during export and re-run failed URLs later.

What does the dataset include for posts?

✅ For type: "post", the actor returns post-related fields such as actor_name, message_text, reaction_count, comment_count, and share_count, along with facebookId, creation_time, owning_profile_id (when available), and extracted_at.

Can I export results to JSON or CSV?

✅ Yes. The actor stores results in a dataset view, and Apify Console lets you export dataset data (including JSON/CSV depending on the UI options available to you).

Do I need any authentication to run this actor?

✅ No special authentication input is defined in the actor schema. The actor works with publicly available sources based on the Facebook URLs you provide.

✅ While this actor focuses on URL-to-ID resolution and extraction of metadata from public sources, it is designed for practical facebook url to id conversion flows. If you specifically need Facebook Graph API behavior, you’d typically use dedicated API workflows—but this actor can still help standardize IDs from URLs.


Support & feature requests

Want to improve Fcebook Url to Id for your facebook url to id pipeline? Tell us what would make it more useful for your use case.

  • 💡 Feature Requests: Examples include CSV-friendly field selection, additional post metrics, or enhanced handling for specific URL variations like facebook profile id from url and facebook vanity url to id.
  • 📧 Contact: Email dataforleads@gmail.com

Your feedback helps shape the roadmap for future improvements to this Fcebook Url to Id actor.


If you’re looking for the most straightforward way to turn Facebook URLs into stable IDs, Fcebook Url to Id is built to get you there—fast and dataset-ready.
Most comprehensive, SEO-optimized, and ready for batch enrichment workflows.


Disclaimer

This tool accesses publicly accessible sources. It does not access private profiles, authenticated data, or password-protected pages.

You are responsible for complying with applicable laws and requirements (for example, GDPR/CCPA), as well as the platform’s terms of service and any relevant anti-spam or data-handling rules. Always use extracted data responsibly and ethically for legitimate purposes.

For data removal requests, contact dataforleads@gmail.com.