Skip to main content

Facebook Lead Ads

Fancified

Facebook Lead Ads for fancy-flow — as four imported, versioned packages, one per runtime. Not vendored source: a copy cannot be upgraded, and third-party APIs change.

Runtime Package Install
Authoring surface (every host) @particle-academy/facebook-lead-ads-ui npm install @particle-academy/facebook-lead-ads-ui
Node @particle-academy/facebook-lead-ads-js npm install @particle-academy/facebook-lead-ads-js
PHP 8.4+ particle-academy/facebook-lead-ads-php composer require particle-academy/facebook-lead-ads-php
Python 3.11+ fancy-facebook-lead-ads pip install fancy-facebook-lead-ads

The ui package is the editor surface and is React on every host — a PHP or Python project installs it and its own runtime package, and never the js one.

What it costs you

One dependency: @particle-academy/fancy-connector-core (or particle-academy/fancy-connector-core on Composer), which the js and php packages pull in themselves. The Python package has zero runtime dependencies.

No Facebook Lead Ads SDK. Plain HTTP, deliberately: a vendor SDK is third-party code subject to the kit's full approval bar, and one per provider is hundreds of dependencies nobody is tracking.

Setting it up

Everything below is generated from provider/manifest.json, so it cannot disagree with what the packages do.

Credentials

A Facebook Lead Ads connection holds 4 values.

Two kinds of value, and mixing them up matters. A provider credential is ONE value for the whole installation — an OAuth app's client secret serves every connected account. An account credential is one per connected account. A host that stores the second where it stores the first lets one account's credentials reach another's.

Field Scope Secret Where it comes from
App ID per installation not secret From the Meta app dashboard. ONE value for the whole installation.
App secret (OAuth) per installation secret The same app's client secret, used to exchange the authorization code.
App secret (proof and webhook signature) per installation secret TWO roles, one value. It keys the appsecret_proof HMAC on outgoing calls, and it is also what Meta signs INCOMING webhook deliveries with -- there is no per-endpoint webhook secret in the Graph API the way there is in Stripe. It is never sent in either direction. For a standard Meta app this is the same value as the OAuth client secret; it is declared separately because they are different roles, and an app that rotates one without the other should not silently break the other.
Page access token per connected account secret PER PAGE, not per user. Leads belong to a Page's forms, and Meta requires the token to be held by somebody who can advertise on the ad account. A long-lived page token lasts about 60 days and is re-authorised rather than refreshed.

Authorising

Facebook Lead Ads uses OAuth2 (authorization_code). The package DECLARES the exchange; the HOST performs it — a consent screen needs a browser, a redirect URI and somewhere to persist the result, and all three belong to the host.

This flow issues NO refresh token. A connection is RE-AUTHORISED rather than refreshed when the access token expires — checked, not assumed.

The estate

Facebook Lead Ads has no test estate, and somebody checked. Everything this connector does is real. Use the faker to build against it.

Facebook Lead Ads has no sandbox. Meta's Lead Ads Testing Tool creates a test lead on the REAL form, which fires the real webhook and appears alongside real leads until somebody deletes it. Anything this reads is real customer data belonging to a real advertiser.

What it can do

Actions

lead_get — Facebook lead

Read one lead's answers by id. Pair this with the leadgen trigger, whose delivery carries only the id.

GET /{leadId} · reads only — safe to replay

Input Required What it is
leadId yes From the leadgen_id on a leadgen delivery. It is not the form id and not the ad id -- both are also numeric, and passing one of those returns THAT object rather than an error.

Triggers

leadgen — Facebook lead

Start when somebody submits a Facebook lead form. The delivery carries only IDS -- pair this with the lead_get action to read the answers.

Delivered by webhook, and the signature is verified before anything runs.

You have to set this up with the provider first:

In the Meta app dashboard, add a Webhooks product, subscribe to the PAGE object and tick the leadgen field, and point the callback URL at the route your host mounts for this trigger. Meta first sends a GET carrying hub.mode=subscribe, hub.verify_token and hub.challenge -- the host must echo hub.challenge back as the body and check hub.verify_token against the value set in the dashboard, or the subscription is never activated. Then subscribe the app to each Page (POST /{pageId}/subscribed_apps with subscribed_fields=leadgen), which is a SEPARATE step: a webhook configured but not subscribed per Page delivers nothing and reports nothing.

Run it before you have credentials

Every operation ships a faker, whether or not Facebook Lead Ads has a sandbox. Set a node's mode to fake and it returns the shape Facebook Lead Ads actually publishes — the same field names, deterministically — so you can wire the downstream nodes before touching an account, a key, or a network.

This repository is generated

provider/ is the source. Everything under packages/ is emitted from it and must not be hand-edited — CI regenerates and diffs on every push, and the next protocol sync destroys anything it finds. See AGENTS.md.

Two namespaces, which do not match on purpose

The repo is github.com/Fancy-Friends/facebook-lead-ads; the packages publish under particle-academy. Nothing derives one from the other — the names come from weaver's friends.json and nowhere else.

Licence

MIT.

Metadata

Release files for fancy-facebook-lead-ads 0.2.1

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for fancy-facebook-lead-ads 0.2.1
File Size Uploaded Provenance Actions
fancy_facebook_lead_ads-0.2.1.tar.gz 24.2 kB Without provenance Details for fancy_facebook_lead_ads-0.2.1.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for fancy-facebook-lead-ads 0.2.1
File Interpreter ABI Platform Actions
fancy_facebook_lead_ads-0.2.1-py3-none-any.whl Python 3 none any Details for fancy_facebook_lead_ads-0.2.1-py3-none-any.whl

Total release size: 48.6 kB

Release files / fancy_facebook_lead_ads-0.2.1.tar.gz

Download URL fancy_facebook_lead_ads-0.2.1.tar.gz
Size 24.2 kB
Tags Source
SHA-256 checksum
How to use checksums
cc43f9f9cfff22e08c86109f89fab7a5ee7726255134856133147d99050aea92
BLAKE2b-256 checksum
How to use checksums
75d7052578ac86c0ab10600310325977dad050f32bdb70e42fb065a7fe15b568
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/7.0.0 CPython/3.13.18

Release files / fancy_facebook_lead_ads-0.2.1-py3-none-any.whl

Download URL fancy_facebook_lead_ads-0.2.1-py3-none-any.whl
Size 24.5 kB
Tags Python 3
SHA-256 checksum
How to use checksums
883db8d7f2a9957293979d09892d02252253c2dd214e43d0e0e4c1ddd58ef950
BLAKE2b-256 checksum
How to use checksums
966989dc6a8cbab81a3a96beea8015bb1cac86a4c98e7e9c4554082bfd9c126d
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/7.0.0 CPython/3.13.18

Security for fancy-facebook-lead-ads 0.2.1

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

No provenance found

None of the files in this release were uploaded with provenance metadata.

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page