LeadSync

Returns the account (id, email, username, plan level, subscription), the key (name, scope, can_write_accounts, can_test_lead), acting_on_other_account and limits; no balance. Use it first to confirm which account you are working on.

Admin keys only. Matches email, username or page name, up to 20 accounts, so you can pick an account_id to act on.

Returns the sources (pages) -> lists graph (each list with `active`, `mapping_set` and its destinations) plus the account's connections with their autoresponders. A source's LeadSync page id is `page.id`; its Facebook id is `page.page_fb_id`. Use it to find a page_id, list_id or connection_id. It cannot show a list's current mapping, only whether one is set.

Returns the fields a destination connection accepts, for building a field mapping. For Google Sheets pass sheet_id, the exact TAB NAME inside the spreadsheet, not the spreadsheet id. Ask the human for it (new Google Sheets often use "Sheet1", but a sheet created another way may be "Untitled"); a destination_error with a sheet_id usually means the tab name is wrong, check that before suggesting a reconnect.

Lists the account's autoresponders and the connection each is attached to. Every lead through a connection gets every autoresponder on it.

Lists recent leads, newest activity first, with the delivery status for each destination. The first stop for "why didn't my lead arrive": check for failed, pending or held deliveries. `since` defaults to 7 days ago and the response echoes the value used as `since_used`; `limit` defaults to 50 (max 200). A lead counts as "never reached LeadSync" only when the window covered its time (pass `since` earlier than the lead's time) and fewer than `limit` rows came back; otherwise narrow with list_id, status or since, or escalate.

Lists emails LeadSync sent (lead notifications, autoresponders, system mail). The first stop for "why didn't my lead arrive" when the destination is an email address, or to check an autoresponder fired.

Re-reads the page's lead forms from Meta so newly created forms appear and attached ones are marked; each form's leads_count shows whether it is live, and forms[].questions[] lists its questions (key, label and type): use each key as the form field key when mapping. Takes the LeadSync page id (sources[].page.id from get_connections).

Attaches a lead form to a destination connection by creating a list. Send mapping AND settings in this same call: a NEW list immediately replays up to 7 days of that form's leads using the mapping given here, so mapping afterwards delivers the replay unmapped. Idempotent on page, form and connection (an existing list comes back with created false, mapping_applied false and a hint; its mapping is untouched). form_id "catch_all" catches every form on the page; Google Sheets needs settings.sheet_id, the TAB NAME. Gated: on another account, or a live form, wait for the human's yes first. override_limits is admin-only and audited.

Pauses or resumes delivery for one list. Resuming can use a source slot and is refused if another active list covers the same form and connection.

Sets an EXISTING list's field mapping and/or per-list settings. Replaces the whole mapping with what you send; settings keys are merged. Send `settings` alone to leave the mapping untouched. An empty mapping object clears it. No tool can read the current mapping, so on a list with mapping_set true never send `mapping` unless the human has given the complete mapping; otherwise the change is made in the LeadSync UI. Send at least one of mapping or settings. For a new list, put the mapping in attach_form instead.

Creates an email autoresponder on a connection. A gated write on another account: it starts emailing the customer's prospects, so wait for the human's yes (on another account there may be no 409 warning). Every lead through the connection receives every autoresponder on it; a 409 lists what is already attached, ask the human before acknowledging.

Requeues a Meta lead's failed or held deliveries. Meta leads only, only failed or held legs, refused while the lead is still in flight; duplicates are irreversible so check list_leads first. Delivery is asynchronous (about a minute); poll list_leads.

Asks Meta to create a test lead for a list's form. The test lead goes to the list's real destinations; on another account it may email the customer, so ask the human before setting acknowledge_customer_impact. Without it on another account the API answers 400 customer_impact_not_acknowledged.