Objective

Sam asked whether the alert webhook is working too after the contact form GCLID and Litify mapping work.

Live Evidence Checked

• Server path checked: /home/1615235.cloudwaysapps.com/fctbkwwahp/public_html.
• Live site home resolved as https://aguiarinjurylawyers.com.
• Custom intake config exists at wp-content/mu-plugins/sal-private/contact-intake-config-v2.php.
• Custom intake handler exists at wp-content/mu-plugins/sal-custom-contact-intake-v2.php.
• The Teams webhook value is configured, uses HTTPS, and is not blank. The secret URL was not printed or copied.
• The handler describes the relay destinations as Litify, email, and Teams. No separate call-center alert function was visible in this handler during the grep check.

Result

The alert webhook is not currently delivering. The handler is calling the Teams webhook, but Power Automate is rejecting it.

Latest failure detail from wp_sal_contact_attempts:

• Lead 104, destination teams, status failed, response code 400, created 2026-06-03 15:15:51.
• Response payload says WorkflowTriggerIsNotEnabled: the workflow b7629569-f685-4356-8933-fc0f37f53d89 manual trigger is suspended and not enabled.

Recent comparison rows show the issue is isolated to Teams alerts:

• Lead 104: Litify sent with HTTP 200, email sent with HTTP 202, Teams failed with HTTP 400.
• Leads 103, 102, 101, 100, 99, 98, and 97 show the same pattern: Litify sent, email sent, Teams failed.

Decision / Handoff

The remaining issue is not the GCLID fix and not the Litify mapping. It is the suspended Power Automate webhook flow behind the configured Teams alert URL.

A future agent can resolve this by either re-enabling the existing Power Automate flow/trigger or replacing it with a durable relay that can post to Teams. After that, submit or replay one controlled test lead and confirm wp_sal_contact_attempts.destination='teams' records a 2xx status.