Meta Leads-to-AFOS Automation

I need a robust Make.com scenario that takes every new lead generated through Meta Leads Center / Instant Forms and creates a matching contact in our AFOS CRM via its REST API. My AFOS provider will supply the full endpoint list, authentication keys and sample payloads, so you’ll have everything required for mapping.

Scope of the build
– Watch the chosen Instant Forms, capture each submission in real time and extract First Name, Last Name, Email, Phone, Postcode, Loan Amount, Campaign Name, Ad Set Name, Ad Name and Lead Submission Time.
– Push that data into AFOS, matching the field schema exactly.
– Add solid error-handling: automatic retry for transient errors, hard-fail logging when the API returns anything outside the 2xx range.
– On every hard failure send me an email notification (we do not need SMS).
– Keep an internal log in Make.com (Data Store or Google Sheet—whichever is simpler to maintain) so my team can audit successes and failures later.
– Thoroughly test with live leads until at least five records have landed in AFOS with all fields correct.

Context you should know
• CRM in use: AFOS only.
• Make.com account is already created but this will be our first production-ready scenario, so please structure it clearly and comment each module.
• Authentication to Meta is active; I can add you as a partner if you need access to the ad account.
- AFOS automatically screens / blocks any leads it perceives as a fake / test lead.

Deliverables
1. Active Make.com scenario with labelled modules, switched on and running.
2. A short hand-over document (Markdown or Google Doc is fine) that covers: module logic, field mappings, where to update tokens, how to modify retries, and how to change the notification address.
3. A quick call or screen-share walkthrough once everything tests green.

Acceptance criteria
– New test lead appears in AFOS within 2 minutes of form submission.
– All required fields populate exactly as in the form.
– Simulated API failure triggers an email to the address I provide and the run is marked ‘error’ in Make.com logs.
– Documentation is clear enough that a non-developer on my team can swap a field or adjust the retry window.

If any part of AFOS’ API spec looks ambiguous, flag it early so I can get clarification from the CRM provider.