@koda-sl/baker-cli 0.234.0 → 0.235.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +10 -0
- package/dist/cli.js +580 -401
- package/dist/cli.js.map +1 -1
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -796,6 +796,13 @@ baker ads meta activities --account-id act_123 --days 7
|
|
|
796
796
|
# "Which Page should this ad run from?"
|
|
797
797
|
baker ads meta pages # Facebook Pages the user manages (tasks shows which can ADVERTISE)
|
|
798
798
|
|
|
799
|
+
# "What is the lead form collecting, and how many came in?"
|
|
800
|
+
baker ads meta lead-forms --page-id 100635183117758 # instant forms on a Page + lead counts
|
|
801
|
+
baker ads meta lead-forms --page-id 100635183117758 --full # also each form's questions
|
|
802
|
+
baker ads meta leads --form-id 987654321 --since 2026-08-01 --until 2026-08-31
|
|
803
|
+
baker ads meta leads --form-id 987654321 --after <nextCursor> # results are PAGED — follow the cursor
|
|
804
|
+
baker ads meta leads --form-id 987654321 --full # raw contact details (CRM hand-off only)
|
|
805
|
+
|
|
799
806
|
# "What are we running right now?"
|
|
800
807
|
baker ads meta campaigns --account-id act_123 # ACTIVE only by default
|
|
801
808
|
baker ads meta ads --account-id act_123 --all-statuses # widen to everything
|
|
@@ -818,6 +825,9 @@ baker ads meta pixels --account-id act_123
|
|
|
818
825
|
baker ads meta pixels --pixel-id 9988 --stats --days 7
|
|
819
826
|
```
|
|
820
827
|
|
|
828
|
+
**Instant-form leads** — `leads` returns **one page** plus a `nextCursor`; a response carrying one is not the whole set, so follow it before quoting any total. Email and phone answers come back masked unless `--full`. Both commands need Meta lead ads switched on for the company (`pages_manage_ads` + `leads_retrieval`, granted at connect time — a company switched on after connecting must reconnect Meta first); each says which of the two is missing.
|
|
829
|
+
|
|
830
|
+
|
|
821
831
|
#### Staged writes (`baker ads meta campaigns|adsets|ads|creatives|audiences|media|draft`)
|
|
822
832
|
|
|
823
833
|
Meta writes mirror the Google/LinkedIn model: they **never hit the Graph API when you run them**. Each op is validated at stage time (field shapes, budget rules, page/Instagram identity ownership, CBO/ABO exclusivity, status-transition legality), shows in the dashboard chat as a pending Meta change, and applies only when the chat is published. Meta has no atomic batch mutate, so ops apply **sequentially** on publish — one failure skips its dependents but the publish completes.
|