Fix Facebook Conversion API Workflow Trigger Not Firing

By Sparkforge Support Team ·Last reviewed May 3, 2026

The test workflow button does not fire the Facebook Conversion API. Save and publish the workflow, then use a real input trigger like Form Submitted or Customer Booked Appointment to test.

If the Facebook Conversion API action in your workflow is not firing, the most common cause is testing through the workflow's test button rather than triggering the workflow live. The CAPI action requires a real, published trigger. Here is what works.

Do not use the test workflow button

The test runner does not generate a real Facebook Conversion API event. It validates the workflow logic but does not call out to Facebook.

Save, publish, and trigger live

To get a real CAPI event, save and publish the workflow, then trigger it using one of these input triggers:

  • Form Submission
  • Survey Submission
  • Appointment Submission (from a booking widget — see note below)
  • Two-Step Order Form

Appointment trigger: pick the right one

For appointments, the CAPI action only fires with Customer Booked Appointment. Do not use the generic Appointment trigger — it covers all appointment events (created, updated, canceled), and CAPI needs the booking widget specifically.

Lead value

Lead value is required only if you map the action to the Facebook Purchase event. For Lead, CompleteRegistration, Schedule, and other event types, lead value can be left blank.

Quick checklist

  1. Workflow is saved and published.
  2. Trigger is one of the supported input triggers.
  3. For appointments, the trigger is Customer Booked Appointment, not generic Appointment.
  4. Lead value is set if (and only if) the event type is Purchase.
  5. Test by actually submitting the form, booking the appointment, or completing the order — not via the test button.

Frequently Asked Questions

Why does the workflow test button not fire the Facebook CAPI?
The test runner validates workflow logic but does not generate real outbound calls to Facebook. The Conversion API action requires a live trigger from a published workflow.
Which appointment trigger works for CAPI?
Customer Booked Appointment, which is specific to the booking widget. The generic Appointment trigger covers all appointment events and will not fire CAPI reliably.
Do I need to set a lead value for every event?
Only for the Purchase event. For Lead, CompleteRegistration, Schedule, and other events, the lead value field can be left blank.
What triggers can I use besides forms?
Form Submission, Survey Submission, Two-Step Order Form, and Customer Booked Appointment all support the Facebook Conversion API action.

Was this article helpful?