Objective

Sam selected the recommended path to fix the suspended Power Automate webhook or replace it with a durable Teams relay for website intake alerts.

Diagnosis

The live website was calling the Teams alert webhook, but recent wp_sal_contact_attempts rows showed Teams failures with HTTP 400 while Litify and email succeeded on the same leads. The Power Automate response was WorkflowTriggerIsNotEnabled for workflow b7629569-f685-4356-8933-fc0f37f53d89.

Further inspection found two distinct issues:

• The configured flow was suspended.
• Once restarted, simple WordPress payloads shaped like {text: ...} triggered the flow but failed inside the Teams card action. A direct adaptive-card payload succeeded.

What Changed

• Restarted Power Automate flow b7629569-f685-4356-8933-fc0f37f53d89, display name Send webhook alerts to Intake Alerts.
• Backed up the live handler before editing: wp-content/mu-plugins/sal-private/backups/sal-custom-contact-intake-v2.php.pre-teams-card-20260603-132036.
• Patched only sal_contact_intake_send_teams() in wp-content/mu-plugins/sal-custom-contact-intake-v2.php.
• The alert text content is unchanged, but it is now sent inside a Teams adaptive-card envelope.
• Did not change Litify mapping, email delivery, form submission, recipients, field names, or the webhook URL.

Verification

• Local working copy lint: php -l admin/scratch/teams-alert-webhook-repair-2026-06-03/sal-custom-contact-intake-v2.php, no syntax errors.
• Live handler lint: php -l wp-content/mu-plugins/sal-custom-contact-intake-v2.php, no syntax errors.
• Live handler availability: sal_contact_intake_send_teams loaded.
• Handler-level WordPress test returned status=sent, responseCode=202, no error. This did not create a Litify Intake and did not send the normal intake email.
• Power Automate latest run for the configured flow succeeded at 2026-06-03T17:23:30.355466Z to 2026-06-03T17:23:35.691181Z.
• Teams channel Intake Alerts showed a new Workflows message at 2026-06-03T17:23:35.429Z.